Why We Charge for Discovery

I'll start with a confession, because it's the honest way into this.

Early on, I gave the work away. A prospect would describe a problem, and I'd get interested, and before there was any contract I'd be a week deep — sketching the architecture, poking at their data, building a little prototype to prove the idea. It felt generous. I thought I was showing my value. I thought free discovery was how you earned trust.

It was actually corrosive, and it took me a few burned months to see why.

Free discovery is a pitch wearing a scoping costume

When discovery is free, both sides quietly lie to themselves about what's happening.

The vendor tells himself he's doing diligence — really understanding the problem before he commits. But he's not, not fully, because unpaid work has a natural ceiling. You do enough to win the deal, not enough to be sure. Free discovery is optimized to produce a "yes," not to produce the truth. It's a sales motion wearing a lab coat.

And the buyer can't tell the difference. From the customer's chair, paid diligence and free sales look identical — someone smart is asking good questions and nodding a lot. There's no way to know whether the enthusiasm in the room is a genuine read of the problem or the enthusiasm of someone who hasn't been paid yet and needs the contract to close. The incentive is invisible, but it's there, and it bends everything.

Then there's what it does to the seller over time. When you give away a month of real work and the deal stalls, or the prospect ghosts, or they take your architecture to a cheaper shop, you start to resent it. And resentment is a terrible foundation for a working relationship. I noticed I was pricing the eventual engagements higher to make up for the free work up front — which meant the customers who did say yes were subsidizing the ones who wasted my time. That's not generous. That's just a hidden tax with extra steps.

What paid discovery changes

So we made discovery a paid phase. In our methodology it's called Ignition, and it's the first thing every engagement runs through.

The moment money changes hands, the whole dynamic gets honest. I'm no longer trying to win you — you already picked me for this piece. So I can spend the time actually being right instead of being persuasive. If the real answer is "this workflow isn't worth automating yet," I can just say that, because I'm not depending on the follow-on sale to get paid for the thinking. Paid diligence can afford to tell you no. Free diligence almost never does.

There's a clarity test buried in this, too. A prospect who won't put a couple thousand dollars behind figuring out whether a project is real was probably never going to sign the contract either. That's not a knock on them — budgets are budgets — but it means we both find out in week one instead of week six. The paid gate does the qualifying that free discovery only pretends to do.

What you actually walk out with

Here's the part that makes charging for discovery fair rather than cheeky: you don't leave with a proposal. You leave with something you can touch.

Ignition ends with a working prototype running on one of your real workflows, using your real data — not a mockup, not a slide, an actual thing that does an actual piece of the job. Alongside it you get a short workflow audit of the process we looked at and a fixed-price quote for everything that would come after. And then you make a go/no-go decision that you control completely.

If you say go, the Ignition fee credits forward — it comes off the price of the rest of the engagement, so you're not paying twice for the same phase. If you say no, you keep the prototype and the audit and you've spent a small, bounded amount to learn something true about your own operation. I've had customers stop after Ignition, and I consider those good outcomes, not lost deals. They paid a fair price to avoid a bad five-figure commitment. That's exactly what the phase is for.

Compare that to the free version, where the "deliverable" is a proposal document engineered to get you to sign, and the only way to find out if the thing actually works is to buy the whole engagement first. Paid discovery inverts the risk. You get proof before you get a big invoice.

"But won't charging scare good people off?"

This is the objection I hear most, and I understand it, because I used to hold it. The fear is that a fee at the front door turns away a great customer who's just being careful with money. In practice, the opposite happens.

Other industries figured this out a long time ago. Architects charge for schematic design. Good agencies stopped doing free "spec" pitch work because it trained clients to expect the expensive part for nothing and rewarded whoever was most willing to gamble unpaid hours. Software diligence is no different. The thinking — figuring out whether a workflow is even worth automating, and how — is not the free sample that gets you to the real product. It is the product's most valuable part. Giving it away teaches everyone, including me, that it's worthless.

When a hesitant prospect asks why they should pay for discovery, my honest answer is that the fee is the cheapest insurance they'll buy all year. For a couple thousand dollars they find out — with a real prototype on their real data — whether a five-figure engagement is worth signing. The people who balk at that math were usually never going to commit to the larger number anyway. The people who get it lean in, because they can see I'm now paid to tell them the truth instead of paid to close them. Charging didn't cost me good customers. It helped me recognize them faster.

The number is small on purpose

Ignition is priced to be an easy yes for anyone who's serious — a couple thousand dollars, scaled a little by the size of the engagement it's scoping, and creditable against the rest. It's deliberately not a profit center. Its job is to align incentives and produce a real artifact, not to make money on its own.

I know charging for discovery cuts against the instinct that says you have to prove yourself for free before someone will trust you. I believed that instinct for a long time. What I learned is that free work doesn't build trust — it builds ambiguity, and ambiguity is the thing that kills these engagements. The trust comes from the prototype on your own data and the go/no-go you hold in your own hand. You can't fake that with a deck, and you shouldn't have to buy the whole project to see it.

If you've got a workflow you're not sure is worth automating, that uncertainty is exactly what a paid discovery sprint is built to resolve. You can see how it fits into the rest of the engagement on the services page.