A website route

Focused
Discovery.

A formal scoped engagement for work that is not yet defined well enough to plan. Best when the objective is clear but the requirements are not: a straightforward project carrying real unknowns.

Scroll

In brief

We use Focused Discovery from Melbourne as a formal scoped engagement for businesses in Melbourne and across Australia. We turn a clear objective with unclear requirements into a decision-ready scope pack across four steps, so the build that follows is quoted from evidence rather than assumption.

The route

Certainty before commitment.

Some projects are clear enough to plan on day one. Focused Discovery exists for the ones that are not: the objective is agreed, but audiences, content, structure or technical direction still carry real unknowns. A short scoped engagement resolves them before anyone commits to a build.

The sequence

Four steps from unknowns to a plan.

A deliberate order, so each decision rests on the one before it.

01

Prepare

Existing material gathered and reviewed: analytics, content, brand, previous scoping and the systems the website touches.

02

Align

A working session to agree objectives, audiences and what success looks like, with the people who will own the result.

03

Define

Structure, content model and high level technical direction drafted and tested against the objective.

04

Validate

The draft scope challenged, gaps closed and the recommendation confirmed as buildable before it is handed over.

Is this your route

Best when the goal is clear and the path is not.

If several systems, teams or governance requirements have to agree before anything can be built, Complex Discovery is the better fit. If requirements are already well defined, go straight to a Template-led or Custom build.

01

A clear objective.

You know what the website needs to achieve, even if you cannot yet describe what to build.

02

Real unknowns.

Audiences, content, structure or platform direction are still open questions rather than decisions.

03

A straightforward project.

One website and one team to align. Multi system environments belong in Complex Discovery.

Why scope first

Why projects start with Discovery.

A short engagement that answers the risky questions before the larger decision is made.

01

Quoted from evidence.

The build is quoted from a defined scope rather than assumption, so the number means something.

02

Fewer surprises mid build.

Unknowns are resolved before they can surface as variations, delays or rework.

03

Decisions in the open.

Objectives and trade offs are agreed and written down, not discovered in review rounds.

04

A pack you own.

The scope pack is yours. Build with us or take it elsewhere; it stands on its own.

05

A faster build once started.

Build weeks are spent building, not re-answering what the website is for.

06

A smaller first commitment.

Discovery is a fraction of a build, sized to the questions it has to answer.

What you end up holding

A decision-ready scope pack.

Objectives, audiences, structure and high level technical direction, concise enough to act on. Not a hundred page document; a pack a decision maker can read and approve.

Objectives and success measures.

What the website must achieve and how everyone will know it has.

Audiences and journeys.

Who the website serves and the paths that matter most to each of them.

Sitemap and content model.

Structure and hierarchy, what content exists and what must be produced.

Technical direction.

Platform recommendation and integration considerations at decision depth.

Risks and dependencies.

What could move the scope, named early with an owner against each item.

A buildable recommendation.

The recommended route and sequence for the build ahead, with reasons.

Talk to us

Scoping a small project? Talk it through with us.

A short, no obligation conversation about where the website is now and what it should do next.

What happens next

From scope pack to build.

Discovery hands over momentum, not just a document.

STEP 01

Walk the pack through together.

The pack is presented and discussed, so decisions are understood rather than just documented.

STEP 02

Choose the build route.

Template-led or Custom, recommended in the pack with the reasoning shown.

STEP 03

Move into the build.

The same team carries the thinking forward. No re-briefing, no drift between disciplines.

Answers

Answers, before you ask.

Long enough to resolve the unknowns and no longer. Duration is confirmed when the engagement is scoped, and the four step sequence is designed to hold momentum.

No. Workshops are one input. The engagement produces a written, decision-ready scope pack you can act on.

No. The pack stands on its own and is yours either way. Most clients continue with us because the same team carries the thinking into the build.

Then it has done its job. You find out at scoping depth rather than mid build, and the pack recommends the right route forward.

Scale. Focused Discovery suits a straightforward project with real unknowns. Complex Discovery adds the streams needed when several systems, teams or governance requirements must agree first.

The people who own the objective in the room, access to existing material and analytics, and honest answers about constraints.

Start a conversation

Scope it properly before you commit to it.

Tell us what the website needs to achieve and where the unknowns sit. We will tell you honestly whether Focused Discovery, Complex Discovery or a straight build route fits best.

4.9 on Google· 74 reviews

Proud partners

  • Google logo
  • Meta logo
  • Microsoft logo
  • Klaviyo logo
  • Mailchimp logo
  • WooCommerce logo
  • BigCommerce logo
  • WP Engine logo
  • Amazon Ads logo
  • Salesforce logo