Some projects cannot be priced honestly from a sales call. The client knows the problem but not the solution, three departments have different ideas of the requirements, and the existing system has integrations nobody has documented. Quoting a fixed fee for the build in that situation means either padding the price until it scares the client or underpricing it and absorbing the overrun. A paid discovery phase splits the risk: a small fixed fee now buys a clear scope, and the build quote that follows is based on evidence.
This template is for developers, web designers, studios and consultants who want to sell discovery as its own deliverable instead of giving it away inside a proposal.
TL;DR
The discovery phase SOW template sells a fixed-fee first phase with a defined set of activities, a capped number of stakeholder sessions, named deliverables such as a requirements document, scope map and priced build estimate, a decision gate, ownership of outputs and an optional fee credit. Send it when the build cannot be priced reliably yet. The key practice is fixing both the fee and the end date, so discovery cannot drift into unpaid design.
What's inside
- Purpose and fixed fee — why discovery comes first, the fee and the duration.
- Questions discovery will answer — the unknowns that make the build hard to price today.
- Activities — stakeholder interviews, workshops, audits and research, each with a cap.
- Deliverables — requirements, user flows or sitemap, technical notes, risks and a priced estimate.
- Client inputs and access — people, documents and systems the phase depends on.
- Decision gate — the readout meeting and the client's options after it.
- Ownership and fee credit — who owns the outputs and whether the fee counts toward the build.
- Schedule and payment — dates, and payment in full or in two parts.
When to use it
Use a discovery phase SOW when the client asks for a build quote but cannot answer basic scope questions, when stakeholders disagree, when there is a legacy system or data migration, or when the project is large enough that a 20% estimate error would hurt you. The thinking behind it is set out in how to scope a fixed-fee project.
It is not the consulting Statement of Work, which runs a full advisory engagement with several phases and recommendations for the client to implement. Discovery is a short, fixed-fee step whose main output is a scope and price for work you would deliver. Once discovery ends, its output becomes the basis for a software development SOW or web development SOW. If the client only needs a single scoping conversation, a discovery call checklist is enough.
How to sell and run paid discovery
Frame it as risk reduction. Clients pay for discovery when they see what it protects them from: a build quote with hidden contingency, or a project that runs over halfway through. Tell them the discovery estimate will be tighter than any number you could give today.
Cap the activities. Discovery expands like any other scope. Set the number of interviews (often 4 to 8), workshops (one or two half-days) and systems you will audit. Extra sessions are a change.
Make the deliverables useful on their own. If the requirements document, flows and estimate would let another competent provider quote the build, the client is getting fair value, and they are more likely to stay with you.
Hold a decision gate. End with a readout meeting and three explicit options: proceed with the build as estimated, proceed with a reduced first release, or stop. Give the build quote a validity period, often 30 days.
Decide on the credit before you send. A credit of the discovery fee against the build, valid if the build is signed within 30 to 60 days, is a common closer. If you offer it, put it in the SOW, not in a later email.
Customize it in your COLO workspace
Send the discovery fee as a COLO proposal with line items for interviews, workshops and deliverables, plus an expiry date. When the client accepts in the client portal, convert the proposal into an invoice, and they can pay by card or PayPal online.
Run the phase as a project with a task per interview and deliverable, and track your hours with the timer. A project budget set to the discovery hours warns you at 80%, which is your cue to wrap up rather than add one more workshop. Your tracked hours also make the build estimate more honest, because you can see how long this client's decisions take.
Common mistakes
- Giving discovery away. Free discovery attracts clients who want a free plan.
- No end date. Discovery without a deadline becomes the project.
- A vague estimate. "Roughly 40-80k" is not a decision-ready number; give ranges per feature.
- Skipping the readout. Emailing a document instead of presenting it lets the decision drift.
- Keeping ownership ambiguous. Clients worry that they paid for something they cannot use. Say they can.
FAQ
Q: What is a paid discovery phase?
A short, fixed-fee engagement before the main project where you research, interview stakeholders and define scope. The output is a requirements document and a priced estimate for the build, which the client owns once they pay.
Q: How much should a discovery phase cost?
Many freelancers and studios price discovery at roughly 5 to 15% of the expected project value, or as a fixed number of days. It should cover your real time, not be a discounted sales step. The freelance pricing guide has more on day-rate pricing.
Q: Should the discovery fee be credited against the build?
Some providers credit part or all of it if the client signs the build within a set period, which helps the sale. Others keep it separate because discovery is real work. Either way, state the rule and the deadline in the SOW.
Q: What if the client takes the discovery output to another provider?
That is the deal. A well-written discovery SOW says the client owns the deliverables on payment and can use them with anyone. You are paid for the thinking either way, which is the point of charging for it.
Q: How long should discovery take?
For small and mid-sized web or software projects, one to four weeks is typical. Longer than that usually means the discovery has turned into the project itself.