A flat-fee discovery phase turns a vague project into a written plan and fixed quote, and pays for itself. What it includes and who it suits.
When clients come to us they almost always think they want the work. A website. A brand. A product. They want execution. They want to see something in three months that they can show to their team.
We sell discovery as its own product. Standalone. Flat fee. Days, not weeks. The deliverable is a document, not a design. Clients can buy it without any commitment to the build.
This essay is about why discovery is, in many cases, a better product than the work that follows it.
What standalone discovery actually is
Discovery is the phase where the studio and the client figure out what the project is. In most agency engagements, discovery is buried at the start of the project. The agency runs a few workshops, drafts a brief, then immediately starts on visuals or code. The discovery is in service of the build.
When we sell discovery standalone, the deliverable is the thinking, not the build. At the end, the client has:
- A written project definition. What the work is. Who it is for. What success looks like.
- A technical or design audit of the existing system, where one exists.
- A scoped recommendation for the actual build, with a fixed-fee quote and timeline.
- A list of things we would not do, and why.
The last bullet is usually the most valuable. Clients almost always come in wanting more than they need. Discovery is the conversation where they realize what is not worth doing.
Why clients pay for discovery
The clients who pay for discovery standalone fall into three buckets.
- The unsure client. They know something is broken but cannot articulate what. They have a budget but not a plan. Discovery turns the budget into a plan.
- The internally-conflicted client. Multiple stakeholders, different views, no agreement. Discovery is the forcing function that makes them agree before money gets committed to building the wrong thing.
- The shopping client. They want to compare studios. Discovery is a low-risk way for them to test whether we are the right team before committing to a hundred-thousand-euro build. We are happy to be tested.
In all three cases, the client is paying us to reduce the risk of the larger spend that may follow. The discovery fee is small relative to the build it precedes. It is the smartest insurance most clients have ever bought.
A flat-fee discovery is the cheapest way to find out you should not do the project.
Why we like selling discovery standalone
The other reason we sell discovery standalone is selfish. It is the best way to learn whether we want to work with the client.
A short discovery is enough to see how the client makes decisions, how they handle disagreement, whether they pay invoices on time, whether the founder is responsive, whether the team can produce information when asked. By the end of discovery, we know whether the build is going to be a pleasure or a slog.
Sometimes discovery ends with us declining the build. Then the discovery was the right product. The build would not have been. The client gets a written plan they can take to another studio. We get to avoid a project that would have hurt the work and the relationship. Both sides are better off.
What discovery deliverables look like
A discovery deliverable is a written document. Not a slide deck. Not a glossy PDF. A working document the client can edit, share, and refer back to.
The structure is consistent across projects:
- Context. Why the project exists. The trigger. The status quo.
- Audience. Who the work is for. What they currently do. What we want them to do.
- Audit. The current state of the systems we are replacing or extending. Honest, technical, specific.
- Recommendation. What we would build. What we would not. What we would defer.
- Scope and cost. The fixed-fee quote for the build, the timeline, the milestones.
- Open questions. What we still do not know, and what would have to happen to answer it.
The open questions section is the one that surprises clients most. They expect us to deliver certainty. We deliver clarity, which is different. There are always open questions at the end of discovery. Pretending there are not is the most expensive lie a studio can tell.
Pricing discovery
We price discovery as a flat fee, typically a small fraction of the expected build cost. Not a percentage, a flat number. The client knows the cost before signing. There are no overages.
The reason this works is that discovery is well-defined. We know how many workshops, how many interviews, how many hours of audit. We have done enough of them to estimate within a tight band. We absorb variance. The client absorbs none.
What clients do with the discovery doc
Some clients commission the build from us after discovery. Others take the document elsewhere, to a different studio or an internal team. We are fine with either.
The document is valuable on its own. We have had clients use it to brief in-house teams, to raise their next round, to align their board, to justify hiring decisions. The work survives our involvement. That is the test of whether the deliverable was real.
If you are thinking about a project and not sure what shape it should be, start with discovery. A few days. A document. A plan. The cheapest thing you will buy before the most expensive one.
Frequently asked questions
What is a discovery phase in a web or software project?
A short, separately priced phase where the studio and client define what the project is: goals, audience, an audit of what exists, a recommended scope with a fixed quote, and open questions.
Is paying for discovery worth it?
Usually. It costs a small fraction of the build and prevents months of building the wrong thing. The written plan is yours to use with any team.
