The Two-Week Paid Pilot: How Agencies Win Enterprise Deals Without Losing Six Months to Procurement

Enterprise deals used to be the prize every agency chased. In 2026 they're often the thing that quietly bankrupts you — six months of unpaid discovery, three rounds of security review, and a legal team that treats your MSA like a hostage negotiation. The fix we keep coming back to is boring and specific: a paid two-week pilot with a fixed deliverable, sold before anyone mentions the word "statement of work".

Why the traditional enterprise pitch is broken

The standard agency motion — deck, discovery call, proposal, revisions, procurement, MSA, SOW — assumes the buyer already trusts you enough to spend the political capital required to push a six-figure contract through their finance and legal teams. Most of the time they don't. They like you. They're not willing to bet their Q3 review on you.

So the deal stalls. You keep sending "just checking in" emails. Your BD team burns hours on a prospect who is technically still in the pipeline but functionally dead. Meanwhile your senior engineers are being asked to jump on "one more scoping call" for free.

The two-week paid pilot flips the sequence. Instead of asking the client to commit to a big engagement based on a proposal, you ask them to commit to a small, ring-fenced piece of paid work that produces something concrete. The pilot is the proposal.

What the pilot is not

A pilot is not a discovery sprint dressed up in different marketing. It's also not a free trial. Two things make it different:

• The client pays. Usually somewhere in the £15k–£40k range, depending on team size and scope. This is deliberately small enough to fit under most managers' signing authority.
• The output is production-adjacent. Not a Figma file. Not a slide deck. A working prototype, a technical audit with reproducible findings, or a migration plan with a runnable proof of concept.

The commercial structure that actually gets signed

The reason two-week pilots close is that they slip under the procurement radar. Most enterprises have a threshold — often around £25k, sometimes £50k — below which a director or VP can sign without triggering full vendor onboarding. Your job is to price and scope so the pilot fits comfortably under that number for the specific buyer you're talking to.

A few things we've learned the hard way:

• Quote a fixed fee, not a day rate. Day rates invite comparison shopping. Fixed fees invite a yes/no decision.
• Include a written pilot agreement, not an MSA. Two pages. Scope, deliverable, payment terms, IP, confidentiality. Save the MSA fight for the follow-on engagement.
• Invoice 50% up front, 50% on delivery. Non-negotiable. If they can't get a 50% deposit through, they can't get the full engagement through either, and you've just learned that for £8k instead of £80k.
• Put an explicit expiry on the follow-on quote. The pilot report includes a proposal for the full engagement, valid for 30 days. This creates the urgency procurement usually eats.

Sample pilot agreement clause

Deliverables:
  1. Technical audit report (PDF, ~20 pages)
  2. Runnable proof-of-concept repository covering [specific feature]
  3. Written recommendation for full engagement scope, pricing,
     and timeline, valid 30 days from delivery date.

Out of scope:
  - Production deployment
  - Third-party integrations beyond those listed in Appendix A
  - Any work not explicitly listed above

IP: All deliverables assigned to Client on receipt of final payment.
Pilot code provided as-is; production hardening quoted separately.

That "out of scope" list is the single most important paragraph in the document. Non-technical buyers will assume everything is included unless you name what isn't.

Picking the right pilot shape

Not every prospect deserves a pilot, and not every pilot looks the same. We generally use one of three shapes depending on what the client is worried about.

Shape 1: The technical audit

Best when the client already has a system and is unhappy with it. You spend two weeks reviewing the codebase, infrastructure, and delivery process, and produce a report with prioritised findings. This is low-risk for you because the deliverable is well-understood, and it positions your senior engineers as the smart people in the room before the full engagement even starts.

Charge more than you think. A proper audit from two senior engineers for two weeks is not a £10k exercise.

Shape 2: The proof of concept

Best when the client is unsure whether a specific technical approach will work — a new AI feature, a migration to a different stack, a performance optimisation. You build the smallest possible version that answers the question. The deliverable is a repo, a short demo, and a written recommendation.

Be brutal about scope. "Can we make this search 10x faster" is a pilot. "Can we rebuild the search experience" is not.

Shape 3: The delivery dry run

Best when the client's real concern is whether your team can actually ship inside their environment — their VPN, their compliance rules, their code review process. You take one small, real ticket from their backlog and deliver it end to end, using their tools. The deliverable is a merged PR and a written report on friction points.

This one is deceptively powerful. It surfaces the political and procedural blockers that would have wrecked the main engagement six weeks in, when it's cheap to walk away.

Staffing the pilot without burning your bench

The biggest operational risk is that pilots eat your best people. If every prospect gets your principal engineer for two weeks, you've built a sales team disguised as a delivery team.

What's worked for us:

• One senior, one mid, part-time PM. The senior sets direction and writes the report. The mid does most of the hands-on work. The PM protects everyone's calendar.
• Cap pilots at two concurrent. More than that and quality slips, which defeats the entire point.
• Reuse ruthlessly. Audit templates, PoC scaffolds, standard report structures. The tenth pilot should take half the internal effort of the first.
• Track pilot-to-engagement conversion. In our experience, a well-run pilot programme converts somewhere between 55% and 70% into a follow-on engagement. If yours is below 40%, you're either qualifying badly or your pilots aren't producing useful deliverables.

Handling the awkward conversations

Two objections come up almost every time.

"Can you do the pilot for free? We'll pay for the full engagement." No. The whole point of the pilot is that paying for it filters serious buyers from tourists. If they push, offer to credit 50% of the pilot fee against the full engagement if signed within 30 days. This preserves the qualification signal while giving procurement a story.

"Two weeks isn't enough to understand our business." Correct. The pilot isn't there to understand the business. It's there to prove one specific technical or delivery hypothesis. Say that out loud. Buyers respect the clarity.

Where the model breaks

Paid pilots don't work for everyone. If your average deal size is below £50k, the overhead isn't worth it — just quote the whole thing. If you're selling to very early startups, they don't have budget for a pilot and shouldn't. And if your differentiation is genuinely creative rather than technical, a two-week engineering pilot may not showcase what you actually sell.

The model also breaks if you use the pilot as a way to lowball into a bigger contract. Buyers can smell that. The pilot has to be genuinely useful on its own — something the client would be glad they paid for even if they never hire you again.

Where we'd start

If you're running an agency in 2026 and your enterprise pipeline is clogged with prospects who love you but won't sign, pick the next serious conversation you have and offer a pilot instead of a proposal. Write the two-page agreement this week. Decide which of the three shapes fits. Set the fee at something that stings a little on both sides — enough that the client has to mean it, small enough that a director can sign it. Then measure conversion honestly over the next two quarters. If you want a sanity check on scoping or pricing structure before you send the first one out, our team runs these engagements regularly — have a look at how we work.