The Pilot That Never Ends: Converting a Corporate Maybe Into a Signed Contract

A no with a calendar invite attached is still a no. It just costs more.

If you sell into mid-market or enterprise, you already know the shape of this. A warm intro turns into a discovery call, which turns into a pilot, which turns into a quarterly business review where someone from procurement says the words legal is still reviewing. Nine months later you've shipped custom features, answered a two-hundred-question security questionnaire, and invoiced exactly zero dollars.

Pilots are supposed to be validation. Too often they're a polite way for a big company to get free strategic work from a small one.

Here's how to stop being that vendor.

The Moment a Pilot Becomes Unpaid Consulting

The transition is quiet and it always looks the same. Deliverables drift from we'll test your product to can you build this specific integration for our team. Success criteria go from does this solve our problem to we'll know it when we see it. The champion stops giving you dates and starts giving you reassurances.

When those three things happen together, you are no longer running a pilot. You're running a services engagement with no statement of work.

Price the Pilot

This is the single highest-leverage change you can make, and it's the one founders resist hardest. Charge for the pilot.

Not full price. Not free either. A paid pilot — even at $5,000 to $15,000 depending on scope — does three things no free pilot can. It forces a real budget line to exist. It filters out companies that were never going to buy. And it converts your team's engineering hours from a gamble into revenue.

Counter the inevitable objection with the honest version: we charge for pilots because they involve real engineering time, and because companies that pay for a pilot show up to the meetings. Buyers respect that more than they'll admit. The ones who balk at a five-figure pilot were rarely going to sign a six-figure contract.

Write the Finish Line Before You Start

A pilot without a written decision criterion is a pilot that ends in ambiguity, and ambiguity always resolves in the buyer's favor. Before anything begins, put one page in front of your champion and get it acknowledged in email:

• What success looks like, in numbers. Not improved efficiency. Something like: support handle time drops 20% across a 20-agent test group within six weeks.
• Who decides. A name, a title, and confirmation that this person controls or strongly influences the budget.
• What happens on success. The specific contract shape and price range you'll move to. Get the range agreed in writing before the pilot, not after.
• The decision date. A hard date when both sides meet and choose: convert, extend once, or stop.

That last one matters most and gets skipped most often. Put it in the calendar at kickoff.

The Security Review Is Part of the Sales Cycle, Not a Compliment

SOC 2 paperwork and vendor risk questionnaires can eat six to ten weeks. Founders treat surviving them as momentum. It isn't. It's a cost.

Ask at kickoff which review gates the deal and who owns each one. If the answer is we'll find out when we get there, that's your real timeline and you should price and plan accordingly. Start the security review in parallel with the pilot, not after it. And if their review requires a control you genuinely don't have, say so early — silence here is how deals die at month seven.

Three Scripts You'll Actually Use

When the pilot has run past its decision date:

We set November 15 as our decision date and we're two weeks past it. I want to be direct: we can't keep this team allocated without a contract in place. Can we get thirty minutes this week to either convert or formally close it out?

When they ask for more scope instead of a decision:

Happy to look at that, but it's outside what we agreed to test. Let's either expand the contract to cover it, or note it as a phase-two item and make a call on the current pilot first.

When you need to shrink the pilot to save it:

It feels like the full scope is stalling on your side. What if we cut this down to the one workflow your team is actually using and get that into production? Smaller commitment, faster proof.

Each of these is uncomfortable for about forty seconds. Then it's just a normal business conversation.

The Walk-Away Math

Here's the part nobody puts in the board deck. A stalled pilot isn't neutral — it's actively expensive. Count the engineering hours, the solutions engineer's calendar, the founder time in status calls, and the sales cycles you didn't run because the team was busy.

If that number exceeds what the deal would be worth in year one, walking away isn't giving up. It's reallocating capital. And there's a real reputational upside: ending a pilot cleanly and professionally often gets you referred elsewhere in that company's network. Founders who ghost a dead deal get nothing. Founders who close it out with a gracious email sometimes get a warm intro six months later.

The Hardest Sentence in Enterprise Sales

We're not going to be able to continue without a decision.

Every founder avoids it. The ones who build durable enterprise businesses say it early, say it politely, and say it often. A pilot that can't survive that sentence was never going to survive procurement either.