The Pilot Project Trap: How Agencies Lose Money Winning New Logos
Discounted pilots feel like smart business development. Most of them aren't. Here's how to structure a first engagement that actually leads to a profitable second one — or kill the deal early.
A sales lead asks for a "small pilot to see how we work together." You discount 30%, cap the scope, and promise fast delivery. Six months later you've done three of those and converted zero. This is the pilot project trap, and most agencies walk into it with a smile.
Why discounted pilots feel smart and usually aren't
The logic is seductive. A pilot lowers the client's perceived risk, gets your engineers in the door, and lets both sides sniff each other out before a bigger commitment. In theory, the discount is a customer acquisition cost — cheaper than a conference booth or an outbound SDR.
In practice, three things go wrong.
First, the discount anchors the relationship. When pilot pricing becomes the client's reference point, every follow-up quote feels expensive. You've trained them to expect a number that doesn't cover your actual cost of delivery.
Second, pilots attract the wrong buyer. A client who insists on a discounted trial before committing is often a client without budget authority, without urgency, or without conviction that the problem is worth solving. These are the three signals most correlated with projects that die in procurement.
Third, pilots distort your delivery incentives. To hit the discounted number, you assign your most junior people or compress the timeline. The client sees your worst work and concludes you're not worth the full rate. Self-fulfilling.
A pilot that doesn't convert isn't a lost deal. It's a project you paid to deliver.
The two kinds of pilots, and only one works
Pilots split cleanly into two categories once you look at them honestly.
Trial pilots exist to prove you can do the work. The client doesn't know you, hasn't seen your output, and wants evidence. The implicit question is "are you competent?"
Qualification pilots exist to prove the engagement is worth doing. Both sides know the agency is competent — maybe through referral, past work, or a strong portfolio. The question is "is this specific problem well-scoped, well-funded, and well-sponsored?"
Trial pilots almost never convert at healthy margins. If a client needs a discounted trial to believe you're competent, you have a positioning problem, not a pricing problem. Fix the positioning. Case studies, reference calls, a technical writeup of a similar system — these do the job without burning six weeks of a senior engineer's capacity.
Qualification pilots work, but only when structured as a paid, time-boxed discovery with a specific deliverable and a decision gate. We've written about one version of this in our discovery sprint approach, and the principle holds: the pilot is not a mini-build. It's a diagnostic.
What a qualification pilot actually produces
At the end of a qualification pilot, the client should walk away with artifacts they can use whether or not they hire you for the next phase:
- A written technical approach, not a slide deck
- A scoped backlog with effort ranges, not point estimates
- An architecture diagram and the key trade-offs flagged
- A go/no-go recommendation that includes "don't build this" as a legitimate outcome
The deliverable is the thinking. If the client takes it to a cheaper vendor, you've still been paid for the work and you've learned that this client was never going to be a long-term partner.
Pricing the pilot without lighting money on fire
Here's where most agencies get it wrong. They price the pilot as a discounted project when they should price it as a fixed-fee consulting engagement.
A reasonable structure in our experience:
- Duration: 1 to 3 weeks, never longer
- Team: one senior engineer or architect, part-time, plus a product lead
- Price: fixed fee, roughly the cost of the loaded time plus a modest margin — not discounted, not loss-leading
- Scope: written as questions to answer, not features to ship
The fixed fee matters. T&M on a pilot invites scope expansion and makes the client nervous about every hour. A fixed fee for a defined deliverable mirrors how management consultancies price, and it signals that you're selling expertise, not seat-time.
Here's a scoping template we've used:
## Pilot Engagement: [Client] / [Problem]
Duration: 2 weeks
Fee: [fixed amount], invoiced 50% on start, 50% on delivery
### Questions this engagement will answer
1. Is the proposed architecture viable given [constraint]?
2. What is the realistic effort range for the MVP scope?
3. What are the top three technical risks and their mitigations?
4. What team shape would deliver this in [timeframe]?
### Deliverables
- Written technical assessment (10-20 pages)
- Scoped backlog with effort ranges
- 90-minute walkthrough with client stakeholders
### Not included
- Working code or prototypes
- Design mockups
- Vendor selection beyond architecture-level recommendations
### Decision gate
At delivery, client decides within 10 business days whether to
proceed to a full engagement. No obligation either way.
Notice what's missing: no promise of working software, no design deliverables, no commitment to the next phase. The pilot stands alone.
The conversion rate math nobody runs
Agencies tell themselves pilots are worth it because "even one conversion pays for the rest." Run the math honestly.
Assume a pilot costs you four weeks of a senior engineer at a fully loaded internal cost of, say, X per week. You deliver the pilot for 60% of your normal rate, so you're losing roughly 1.6X per pilot in opportunity cost compared to billable work.
If your pilot-to-full-engagement conversion rate is 25% — which is optimistic for discounted trials in our experience — then every converted engagement carries the cost of three failed pilots. That's roughly 5X in sunk delivery cost before the paying engagement starts. For a six-month follow-on at normal rates, you might still come out ahead, but the margin is thinner than the alternative: investing that same senior engineer time in content, case studies, or outbound to clients who don't need a trial.
Qualification pilots at full fixed-fee pricing flip this. Even at a 40% conversion rate, each failed pilot is cash-flow neutral or slightly positive. The economics stop depending on conversion.
When to walk away mid-pilot
Some signals that the pilot has already failed and the full engagement will too:
- Stakeholders you were promised access to never show up
- The problem keeps mutating week to week
- Procurement gets involved before you've delivered the assessment
- The client asks you to "start the build in parallel" to save time
- Budget for the full engagement has not been confirmed by week two
Any two of these and you should be having a direct conversation with the economic buyer about whether the next phase is real. Better to surface the misalignment during a paid pilot than to inherit it in a signed SOW.
What to tell the client who demands a discount
The pushback is predictable: "We can't commit to a full engagement without seeing how you work. Can you do the first phase at a reduced rate?"
A script that works:
"We don't discount first engagements, because the clients who get the most value from us are the ones who are confident in the fit before we start. What we can do is a two-week paid assessment at a fixed fee. You get a written technical plan and a scoped backlog you own, whether or not we do the build. If after that you want to work with someone else, no hard feelings. Does that sound like a better fit than a discounted pilot?"
Most serious buyers say yes. The ones who don't were not going to be good clients anyway, and you've saved yourself the discovery of that fact the expensive way.
Where we'd start
If you're running discounted pilots today, audit the last twelve months. Count how many converted to full engagements at your target margin. Our bet is the number is lower than you tell yourself, and the converted ones were clients who would have signed without the discount.
Then rewrite your pilot offering as a fixed-fee assessment with a written deliverable and a decision gate. Price it to be slightly profitable on its own. Push back — gently, with a script — on any prospect who insists on a discounted build-based trial.
You'll close fewer pilots. You'll convert more of the ones you do close. And the senior engineers you'd otherwise be burning on unpaid prototype work will be free to do the thing that actually grows an agency: deliver excellent work for clients who pay full price. If you want to see how we structure engagements end-to-end, our services page lays out the model.
Want a team like ours?
72Technologies builds production software for the kind of teams who actually read this blog.
Start a projectKeep reading
Killing the Discovery Phase: Why We Replaced It With a Paid Architecture Sprint
Discovery phases rot. They produce PDFs nobody reads and estimates nobody trusts. Here's the paid architecture sprint we run instead, and why clients actually pay for it twice as often.
The Statement of Work Is a Product: How We Rewrote Ours After Losing Three Fixed Bids in a Row
An SOW isn't paperwork. It's the first thing your client reads in anger when a project goes sideways. Here's how we rebuilt ours to actually protect both sides.
The Equity Deal That Almost Sank Us: A Framework for Agencies Taking Stock Instead of Cash
Taking equity from a client sounds like free lottery tickets. It isn't. Here's the framework we use to decide when stock beats a wire transfer — and when it's just a discount with extra paperwork.
