Skip to main content

​
Definition

The pilot-to-production gap is the failure point where a startup delivers a successful pilot for a buyer — usually a public sector or enterprise organisation — but cannot convert it into a paid production contract. The pilot proves the technology works. The buyer agrees it has value. But no budget exists, no procurement pathway is available, and no one has authority to buy. This is the most expensive failure mode in innovation procurement. It wastes the startup’s time, the buyer’s investment, and the ecosystem’s learning. It also teaches founders that public sector innovation programmes are a dead end — which reduces participation in the next round.

​
When it matters

​
Why do successful pilots fail to convert?

Pilots fail to convert for structural reasons, not technical ones. The gap exists because innovation teams and procurement teams operate as separate systems. Innovation teams are tasked with exploring new technology and testing solutions. They have budgets for exploration. They do not have budgets for production. When a pilot succeeds, the innovation team celebrates, but the procurement team has not been involved. There is no budget line, no supplier assessment, no contract vehicle. Vicky Brock gives a concrete example from a UK GovTech programme: a successful delivery for a specific Border Force use case, followed by no budget or route to buy the solution. The startup delivered value. The system could not absorb it.

​
How common is this problem?

This pattern is widespread across the UK public sector and enterprise procurement. CivTech in Scotland has addressed it partially by creating a defined pathway — a three-week exploration stage followed by a 15-week accelerator stage. But even with a defined pathway, the conversion from accelerator output to paid production depends on whether the sponsoring body has budget and procurement authority aligned. The Building Scotland conversations estimate that Scotland’s £16.6 billion annual public procurement spend could be a powerful demand lever — but only if the system is designed to convert successful pilots into production contracts rather than treating them as isolated experiments.

​
How it works

​
What causes the pilot-to-production gap?

Four structural failures create the gap:
  1. Budget misalignment — innovation budgets fund exploration. Production budgets sit in service delivery. These are different budget lines, often controlled by different people.
  2. Procurement process misfit — standard procurement frameworks are designed for known requirements and established suppliers. A startup emerging from a pilot does not fit the template.
  3. Risk ownership vacuum — nobody owns the risk of adopting a new solution. Innovation teams take the risk of testing. But deploying to production requires a service owner to accept operational risk.
  4. Criteria ambiguity — pilots are commissioned without clear criteria for what success looks like. When the pilot ends, there is no objective basis for deciding whether to proceed.

​
What does a working conversion pathway look like?

A working pathway connects the pilot to production before the pilot starts. It requires:
  • Named budget holder — a person with authority and budget to buy if the pilot succeeds.
  • Published success criteria — defined before the pilot starts, not negotiated after it ends.
  • Procurement vehicle — a contract mechanism that allows the buyer to proceed without a full re-tender.
  • Risk allocation — clear ownership of operational risk if the solution is deployed to production.
  • Timeline — a committed decision point. Not an open-ended evaluation.

​
Practical steps

​
How to close the pilot-to-production gap

  1. Involve procurement from day one — do not design a pilot without the procurement team in the room. They need to understand what is being tested and what happens if it works.
  2. Set success criteria before the pilot starts — define measurable outcomes that, if achieved, trigger a procurement process. Make these criteria public and specific.
  3. Identify the production budget in advance — ensure a named budget holder has committed funds for production if the pilot succeeds. If no budget exists, do not start the pilot.
  4. Use existing contract vehicles — frameworks, dynamic purchasing systems, and innovation partnerships provide routes to production without full re-tender. Identify the appropriate vehicle before the pilot begins.
  5. Build the evidence pack during the pilot — collect the data, outcomes, and risk evidence that procurement teams need to justify the buy. Do not wait until after the pilot to assemble this. See evidence packs.
  6. Set a decision deadline — commit to a go or no-go decision within a defined period after the pilot ends. Open-ended evaluation kills momentum and teaches startups that the system wastes their time.

​
What three things must every POC have from day one?

The Lessons from a Fintech series identifies three non-negotiable requirements for any proof of concept. Without all three in place before the pilot begins, the POC will produce learning but not revenue.
  1. A measurable success metric. Not “the client was happy” — a specific, quantified outcome that both sides agree constitutes success. Example: “Reduce income verification time from 48 hours to under 5 minutes with 95%+ accuracy.”
  2. A named decision owner. A specific person with the authority and budget to approve production if the metric is hit. Not a committee, not a department — a named individual who has committed to making a decision by a specific date.
  3. A production path defined from the start. The procurement vehicle, contract terms, and integration pathway must be agreed before the pilot starts. If the pilot succeeds, the path to production should be a process step, not a new negotiation.
Without these three elements, pilots become what the series calls “innovation theatre” — activity that creates the appearance of progress without a commercial outcome. The founder invests months of engineering and sales effort, the buyer gets free work, and neither side builds anything lasting.

​
Common mistakes

  • Running pilots without production intent — if there is no budget and no authority to buy, the pilot is an experiment, not a pathway. Be honest about which it is.
  • Separating innovation from procurement — when innovation teams run pilots and procurement teams run buying, the gap between them becomes the graveyard for successful solutions.
  • Using pilot success to justify more pilots — the next step after a successful pilot is production, not a bigger pilot. Avoid the loop of perpetual testing.
  • Applying standard procurement criteria to pilot outputs — headcount requirements, revenue thresholds, and years-trading filters designed for mature suppliers will block the startup that just proved its technology works.
  • Celebrating the pilot without tracking conversion — the measure of a pilot programme is how many companies progress to paid production, not how many pilots run.

​
Key takeaways

The pilot-to-production gap is not a technology problem. It is a procurement design problem. Closing it requires connecting innovation teams and procurement teams before the pilot starts, not after it succeeds. Every pilot should start with four answers: what does success look like, who has authority to buy, what budget is committed, and what procurement route will be used. If those answers do not exist, the pilot is likely to produce learning for the buyer and frustration for the startup.