Discovery and planning

Decisions made early,
so the build holds.

We define what the website must do, for whom and on what architecture before design and build begin. Discovery turns opinions into requirements and requirements into a plan you can hold the delivery to.

Discuss your project Book a meeting

Scroll

In brief

We provide website discovery and planning services from Melbourne for established businesses across Australia. We define requirements, architecture and scope before build decisions are made. Our discovery-led projects are documented in case studies on this website.

The service

The cheapest place to change a website is on paper.

Every unresolved question in planning becomes a mid-build surprise with a cost attached. Discovery resolves the questions while they are still cheap, so the build proceeds on decisions rather than assumptions.

What we do

Discovery and planning, end to end.

Objectives, audiences, architecture and scope defined on one program by one accountable Melbourne team.

Objectives and success measures.

What the website must achieve commercially, agreed in writing with the people accountable for it.

Audience and journey definition.

Who the website serves, what they need to decide and the journeys that get them there.

Content and information architecture.

Sitemap, content models and page hierarchies designed around how audiences actually look for things.

Technical and platform requirements.

Integrations, hosting, security and platform needs to be documented before they can surprise the build.

Scope and delivery plan.

What is in, what is out and in what order, written down so delivery can be held to it.

Build-ready documentation.

Requirements handed over in a form a design and build team can execute without interpretation.

The discovery fit

Sized to the decision in front of you.

Not every project needs the same depth of definition. We run focused discovery where the questions are contained, and complex discovery where integrations, regions or stakeholders multiply. The output in both cases is the same: decisions you can build on.

Focused discovery.

A contained program for projects where the questions are known and the systems are few.

Complex discovery.

A deeper program where integrations, migrations, regions or many stakeholders need resolving.

Fit for what follows.

Either way, the output is build-ready: requirements, architecture and scope you can hold delivery to.

Why it matters

Why planning decides what the build costs.

Most website projects fail on unresolved questions, not on bad code. Discovery is where those questions get resolved.

Scope that holds.

A written scope means changes are decisions, not disputes.

Budgets that behave.

Requirements resolved early stop the mid-build surprises that stretch cost and time.

Stakeholders aligned.

Decisions made once, with the right people in the room, stop the relitigating later.

Architecture before aesthetics.

Structure and platform decided on evidence, so design and build stand on solid ground.

Content faced early.

Content needs sized at the start, so the launch is not delayed by missing pages.

A plan you can hold.

Delivery measured against a written plan rather than a moving memory of what was said.

Quality

Findings you can act on, not a report that shelves well.

Discovery outputs are working documents for the build that follows, and every recommendation carries its reasoning.

Evidence based.

Recommendations grounded in analytics, stakeholder input and audit findings, not preference.

Decisions recorded.

Every decision written down with its reasoning, so it survives team and time.

Requirements testable.

Requirements written so the finished website can be verified against them.

Scope explicit.

What is out of scope stated as clearly as what is in.

Owners named.

Every stream has a named owner on both sides, so nothing waits on nobody.

Build ready.

Documentation complete enough that a design and build team can execute without interpretation.

Talk to us

Not sure where to start? Talk it through with us.

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

Book a meeting

The discovery sequence

A deliberate sequence from questions to plan.

Discovery follows the same order every time, so decisions are made once, in the right place, with the right people.

LISTEN

Objectives and evidence first.

Stakeholder sessions, analytics and audits establish what the website must do and for whom.

DEFINE

Architecture and requirements.

Sitemap, content models, technical requirements and platform direction defined and reviewed.

PLAN

Scope and delivery plan.

Scope, order and owners agreed in writing, then handed over build-ready.

The approach

How we approach discovery.

Discovery can precede any engagement, ours or another team's. The documentation stands on its own either way.

Understand

Business objectives, audiences and the jobs the website must do, confirmed with the people who own them.

Interrogate

Current website, analytics, content and systems audited for what helps and what blocks.

Plan

Definition order agreed by dependency and impact, with owners and checkpoints written down.

Implement

Requirements, architecture and scope produced in agreed cycles, reviewed as they land.

Measure

Documentation verified as testable, explicit and build-ready against the agreed standards.

Improve

Findings from delivery fed back into the plan, so the documentation stays true in use.

Answers

Answers, before you ask.

No. Contained projects can proceed on a focused program, and we will tell you honestly which depth your project needs and why.

It depends on the systems, stakeholders and unknowns in scope. We agree the program and its checkpoints with you before it starts.

Yes. The documentation is written to stand on its own, so any competent team can execute from it.

Requirements, sitemap and content models, technical and platform recommendations, and a written scope and delivery plan with owners and order.

Sometimes, and that is the point. It is far cheaper to change direction on paper than mid-build.

Access to analytics and the current website, and time with the people who own the objectives, content and systems.

Planning routes

Where discovery leads.

Focused discovery Complex discovery Template-led website Custom website

PROOF ON THIS PAGE

Website development results, documented.

Health & wellbeing Sense of Self Wellbeing Website design and development giving a life coaching brand its own voice online. Read more

Trades & construction Dinya Designs WooCommerce website design and development serving retail browsers and trade buyers alike. Read more

HR consultants reviewing a presentation.

Professional services VeiraMal Consulting Website design and development giving a specialist consultancy a brand of its own. Read more

Start a conversation

Talk to a planning team in Melbourne.

Starting a significant build, weighing a replatform or trying to get stakeholders aligned? Tell us where the project stands, and we will help identify the appropriate next step.

Discuss your project

4.9 on Google· 74 reviews

Decisions made early, so the build holds.

The cheapest place to change a website is on paper.

Discovery and planning, end to end.

Objectives and success measures.

Audience and journey definition.

Content and information architecture.

Technical and platform requirements.

Scope and delivery plan.

Build-ready documentation.

Sized to the decision in front of you.

Focused discovery.

Complex discovery.

Fit for what follows.

Why planning decides what the build costs.

Scope that holds.

Budgets that behave.

Stakeholders aligned.

Architecture before aesthetics.

Content faced early.

A plan you can hold.

Findings you can act on, not a report that shelves well.

Evidence based.

Decisions recorded.

Requirements testable.

Scope explicit.

Owners named.

Build ready.

Not sure where to start? Talk it through with us.

A deliberate sequence from questions to plan.

Objectives and evidence first.

Architecture and requirements.

Scope and delivery plan.

How we approach discovery.

Understand

Interrogate

Plan

Implement

Measure

Improve

Answers, before you ask.

Do we need discovery before every build?

How long does discovery take?

Can you run discovery on a website someone else will build?

What do we get at the end?

Will discovery change what we thought we needed?

What do you need from us to start?

Where discovery leads.

Learn more about Discovery and planning.

Website brief template for complex website projects.

Website brief vs paid Discovery: what should each stage achieve?

How to compare website proposals when every agency scopes differently.

Website development results, documented.

Talk to a planning team in Melbourne.

Decisions made early,
so the build holds.