What Will This Buyer Do if the Pilot Works?

A buyer who asks for acquisition optionality before a pilot should still commit to a paid, bounded test with a clear decision point. The request reflects strategic seriousness when they can name the sponsor, the post-pilot decision, and the conditions that would lead them to expand.

The immediate problem came before the larger journey

In 1970, Apollo 13’s crew faced rising carbon dioxide inside the lunar module. The command module had square lithium hydroxide canisters. The lunar module used round ones. The crew needed a way to make equipment designed for one spacecraft work inside another, while the larger problem of getting home remained unresolved.

NASA engineers on the ground developed an adapter from materials already available aboard the spacecraft, including plastic bags, cardboard, tape and a flight-plan cover. NASA’s Apollo 13 Flight Journal documents the effort and the crew’s use of the improvised device.

The point was not to redesign both spacecraft in the middle of a crisis. The point was to solve the immediate constraint well enough to preserve the chance of finishing the larger mission.

A pilot can arrive with the same kind of confusion. The buyer has a real problem. They may see value in the product. Then they ask what happens if they want to acquire the company, buy the underlying technology, or secure exclusive rights after the pilot.

That question can pull a founder away from the work in front of them. Instead of agreeing what the pilot will prove, both sides begin discussing a transaction that may never happen.

Acquisition language can hide two very different intentions

The European buyer was not asking for a standard procurement answer. They wanted to know whether a successful pilot could give them a path to own the capability rather than depend on an external company.

That can mean they are thinking seriously about the product’s place in their business. It can also mean they want the comfort of control before they have taken the smaller risk of becoming a customer.

Those are different situations, even when they use the same language.

A serious buyer can usually explain the operational problem they need the pilot to test. They can identify who will use the product, who owns the budget, and what result would justify a wider rollout. Their acquisition question sits beside a real decision process.

A buyer avoiding commitment often keeps the request broad. They want reassurance about future ownership without agreeing the data access, user group, implementation work or commercial terms that would make the pilot useful. The exit plan becomes a substitute for a purchase decision.

Founders can be tempted to read every acquisition question as validation. It feels like evidence that the product matters. Sometimes it is. But a future transaction is not evidence of present demand.

The useful question is simpler: what will this buyer do if the pilot works?

If the answer is unclear, the pilot has not reached the stage where acquisition terms deserve much attention.

Keep the pilot useful if the future conversation never happens

I would separate the two conversations without dismissing either one.

The pilot needs a written purpose: the user workflow, the product boundary, the data involved, the success measure, the person who will review the result, and the date when both sides decide what happens next. The buyer should know what they are paying for and what they will receive. The founder should know which result counts as evidence rather than polite enthusiasm.

Then the acquisition request can be acknowledged as a later strategic discussion. It does not need to become a promise, an exclusive option, or a clause that gives the buyer influence over the roadmap before they have proved they can deploy the product.

This matters even more for a small team. A vague pilot can consume the same engineering attention as a committed customer, while leaving the company unable to reuse the work elsewhere. The risk grows when the buyer wants features tailored to an internal process they have not yet committed to funding. What Happens When a Buyer Changes Your Product Beyond Recognition? explores that pressure from the product side.

The cleanest response is practical: “We can discuss strategic options after the pilot. First, let’s agree what this pilot must show and what decision you will make from the result.”

That sentence tests intent without creating unnecessary conflict. A buyer with a real internal case usually welcomes the structure. They need it for their own stakeholders. A buyer seeking optionality without commitment may resist because the ambiguity was doing work for them.

Protect the decision that is actually available

Apollo 13 did not require everyone involved to solve the entire return journey before addressing the carbon dioxide problem. The adapter bought time and kept the mission viable.

A pilot should do the same. It should produce evidence about use, value, delivery effort and willingness to continue. It can create the conditions for a later partnership, investment or acquisition discussion. It cannot responsibly stand in for any of them.

If a buyer asks for an exit plan, write down the request and return to the current decision. Ask for the sponsor. Ask what a successful pilot changes. Ask what they will commit when the evidence is there.

If those answers remain vague, protect the roadmap and decline to price your company’s future into a pilot that has not earned its present.