How to price discovery and strategy work

You spend three hours understanding a project well enough to price it accurately. You map requirements, identify risks, clarify what the client actually needs versus what they asked for. You send the proposal.

The client goes with someone cheaper.

You just worked for free. And that’s assuming the project wasn’t lost to a competitor — sometimes clients take the thinking you did and use it to brief someone else.

Why discovery usually doesn’t get billed

Three things push it out of scope.

First, the line between sales and work is blurry. The discovery call is free. The proposal is free. Everything before the signed contract is treated as marketing overhead. At some point that assumption bleeds into the thinking you do before writing the proposal.

Second, there’s no deliverable. You can charge €3,000 for a website because the client can picture a website. Charging €700 for “understanding your situation and defining what the project actually is” is harder to justify — even when the thinking takes longer than any individual screen or page.

Third, clients don’t ask for it by name. They ask for the website, the campaign, the integration. The discovery happens because you need it, not because they thought to request it.

What discovery work actually includes

Discovery is the phase before delivery starts. It’s not the 30-minute intro call — that’s sales.

Real discovery is: reviewing existing materials, mapping technical constraints, understanding the client’s actual goal (which is often different from the stated brief), defining what success looks like, writing the brief the client couldn’t write themselves, and identifying where the unknowns are.

Strategy work is adjacent. Recommending an approach when there are options. Designing a system. Making architectural decisions. The thinking that shapes what gets built and how.

Both have the same characteristic: they produce no tangible deliverable. What exists at the end is clarity and direction — which has real value but doesn’t photograph well.

The cost of doing it for free

When discovery is free, clients don’t value it. They can walk away after you’ve done the analysis, with nothing owed. You absorb the hours.

And when discovery is skipped — rushed through a 45-minute call to get to the proposal faster — you price from assumptions. The result: scope creep because the client’s needs were never actually defined, mid-project renegotiations when you hit something you didn’t account for, and deliverables that miss the mark because nobody asked the right questions first.

A project that starts with paid discovery is almost always cheaper for the client in the end. That’s not a sales pitch — it’s what happens when scope is defined before execution starts.

How to structure a paid discovery phase

Sell two projects, not one.

The first project: discovery and scoping. A defined engagement — typically two to four days — with a specific deliverable. Not “I’ll assess your situation.” That’s vapor. “I’ll deliver a four-page project brief covering current state, requirements, constraints, recommended approach, and a phased delivery timeline” — that’s a product.

The deliverable makes it purchasable. The same thinking, but one version is something the client can evaluate, approve, and reference throughout the project.

The second project: delivery, priced from what discovery revealed.

This structure does two things. It turns discovery into revenue. And it qualifies clients: someone who won’t pay €1,500 for clarity before committing to €15,000 in delivery either doesn’t have the budget or doesn’t trust you enough yet. Both are useful signals.

How to price it

Price it the way you’d price any fixed-fee work: start from honest time estimates, apply your rate, add a margin for the iteration it takes to reach alignment.

Discovery for a mid-complexity project typically runs four to eight hours — requirements review, client interviews, brief drafting, review loops. Two days at €600–800/day is €1,200–€1,600. For a project that would otherwise be €15,000, that’s under 10% of the total. Easy to justify when it de-risks the delivery estimate.

Don’t discount it. The temptation is to price discovery attractively to win the relationship. But underpriced discovery signals that the phase isn’t important — which is the opposite of what you want the client to believe.

What to say when a client asks “why should I pay for a quote?”

Discovery isn’t a quote. A quote is free.

A quote tells the client what their project will cost. Discovery tells them what their project actually is, what it needs to succeed, and where the risks are. Different services.

The clean framing: “I can give you a rough estimate based on what you’ve described — but if you want a precise scope and a real project definition before you commit to the larger investment, I’d recommend a short discovery phase first.”

Most clients who are serious about the project will accept it. The ones who won’t usually don’t have a clear project in the first place.

Using your calendar to price discovery right

The cleanest way to know what to charge: look at what you’ve already done.

If your calendar events are consistently named — [Client][Project] Brief review, [Client][Project] Requirements call, [Client][Project] Scoping document — you can look back at the last five projects and see how many hours the pre-delivery phase actually took.

Some projects take three hours. Some take twelve, when the brief was vague, the client was unclear, and extra alignment calls were needed. That range tells you how to price for each signal.

Timescanner shows hours by client and project. If your discovery work is in your calendar and consistently tagged, that history already exists — you just need to run the analysis and set a price that reflects reality.

Timescanner reads any iCal calendar and shows hours by client and project. Works with Google Calendar, Outlook, Apple Calendar, and any iCal-compatible app.