"Can You Do a Free Pilot?" — When a Pilot Is Progress and When It's a Parking Lot

Two things that sound identical on a call

"Can you do a free pilot?"

The rep hears momentum. Somebody wants to touch the product. Somebody is willing to put internal effort behind it. The forecast note that night says evaluating, pilot scoping in progress, and the deal moves from Stage 2 to Stage 3 in the CRM because the CRM rewards activity.

Twelve weeks later there is a pretty deck summarizing the pilot results. The sponsor is polite about it. The results were good, actually. And nothing happens. The renewal on the incumbent tool goes through in the background, the budget cycle closes, your champion moves to a different team, and the deal quietly rots in Stage 3 until someone runs a pipeline hygiene review and closes it out as no decision.

Here is the thing that took me too long to learn selling inside Dell and AWS, and then again running my own companies: the words "free pilot" describe two completely different objects. One is a purchase that hasn't been signed yet. The other is a place to put a decision so nobody has to make it. They sound the same coming out of a buyer's mouth. They feel the same in the meeting. They are not the same, and you can tell them apart in about four questions if you are willing to ask them.

Why buyers reach for the word

Most buyers who ask for a free pilot are not trying to trick you. That is worth saying up front, because reps who get burned once start treating every pilot request as a brush-off, and that is its own kind of expensive.

A buyer asks for a pilot for one of a few reasons. They genuinely have technical risk they cannot resolve on a demo — will this actually parse our file format, will the latency hold at our volume, will our reps use it. That is a real pilot request, and refusing it makes you look like you are hiding something.

Or they believe you and want you, but they cannot get money this quarter, and a pilot is a way to keep the relationship warm until they can. Also real, also workable, but the deal you are in is a timing deal, not an evaluation deal, and you should be selling to it differently.

Or — and this is the one that eats pipeline — they don't want to say no. Saying no to a vendor who has been helpful for six weeks is socially expensive. Saying "let's start with a pilot" costs nothing, buys months of quiet, and lets everyone stay friendly. Nobody is lying. They are just deferring, and the deferral is dressed up as progress.

Your job is not to figure out which type of person you're talking to. People are bad at self-reporting their own intent, and you'll never get a straight answer by asking "are you serious about this?" Your job is to look at the structure around the pilot. Structure doesn't lie.

The four questions

A real pilot has four things attached to it. A parking lot has none of them, and usually the buyer cannot produce them on the spot, which tells you everything.

1. Is there a named executive sponsor?

Not "leadership is aware." Not "my VP is supportive." A name, and a person who has been in a room where this was discussed.

A pilot with no exec attached is a hobby. Your champion runs it in the margins of their real job, the results land in an inbox nobody prioritizes, and when it comes time to convert, you discover you have to start the entire sales cycle over with someone who has never heard of you. I have watched deals die at exactly that moment — a great pilot, a delighted user, and a VP who says "remind me who these people are?"

The reason the exec matters is not signature authority. It's that an exec is the only person who can make the pilot matter to somebody's quarter. If no leader has a goal that this pilot serves, the pilot serves nothing.

How to ask it without sounding like you're auditing them:

"Happy to do this. One thing I've learned the hard way — pilots that don't have a leader watching them tend to get out-prioritized by whatever fire hits in week three, and then we both waste a quarter. Who's the exec whose number moves if this works? I'd like to get them a one-pager before we start so they're not surprised by the result."

Notice what that does. You said yes. You framed the question as protecting their time, not qualifying them. And you gave a concrete reason you need the name — you have something to send that person. If they can't produce a name, or the name is vague, you have learned something enormous and it cost you nothing.

2. Is there a written success threshold?

This is the one reps skip most often, and it is the one that kills the most deals.

"We'll see how it goes" is not a success criterion. "If the team likes it, we'll move forward" is not a success criterion. Those are vibes, and vibes lose to inertia every single time, because at the end of a pilot the buyer is comparing your product not against nothing but against the discomfort of a change project. Ambiguous results always resolve in favor of doing nothing.

What you want is a threshold somebody would recognize as met or not met without arguing. Not "improve response time" but "first-touch inside ten minutes on inbound leads for the pilot group." Not "reps like it" but "eight of the ten pilot reps say they'd rather keep it than go back." Written down. In an email you sent and they replied to. The reply is the artifact — it converts a conversation into something you can quote in week eleven.

"Let's write down now what a good result looks like, before either of us knows the answer. If we hit it, what happens? And just as important — if we miss it, I'd rather you tell me no in April than have this sit around. What's the number that makes this a yes?"

That last construction — offering them the no — does more for your credibility than anything else you can say in a pilot conversation. It signals you are not afraid of the result, which is the behavior of someone whose product works.

3. Is there a date it ends?

Pilots without end dates don't end. They become the arrangement. You are now a free vendor with a support obligation and no contract, and every month that passes makes it harder to ask for money because the status quo is you being free.

An end date is not just a deadline for you. It is the forcing function that makes the buyer's internal process start. Procurement will not begin reviewing your MSA in week two of an open-ended trial. They will begin when a champion emails them saying "this ends on the fifteenth and we need paper."

Set the date in the same conversation where you agree to the pilot, and set it short. Thirty days is enough to prove almost anything. Sixty if there's real technical integration. Anything longer than a quarter and you are not piloting, you are dating.

"I want to put an end date on this — not for pressure, but because open-ended evaluations tend to drift and then nobody's happy. Let's say we start Monday the sixth and we make a call by the ninth of next month. That's four full weeks of live use. Does that give your team enough runway?"

Asking whether it's enough runway hands them control of the length while keeping the principle of an ending. Almost nobody refuses.

4. Where does the money come from when it works?

The fourth question is the one reps are most scared of, and it is the only one that actually predicts revenue. There is no point running a flawless pilot into a budget that doesn't exist.

You are not asking "do you have budget." That question invites a defensive answer and you'll get "we'd have to find it," which means nothing. You are asking about the mechanism. Is there a line item. Whose cost center. Does it need to go into next year's plan, and when does that plan get locked. Is there an incumbent contract whose spend gets redirected, and when does that contract renew.

"Assume the pilot goes great and we hit the number we just wrote down. Walk me through what happens next on your side — whose budget does this come out of, and is that money sitting there now or does it get requested? I ask because if it's a next-fiscal-year thing, I'd rather we time the pilot to land right before your planning cycle instead of six weeks after it."

The last sentence is the unlock. You've turned a budget interrogation into a scheduling favor. And if the honest answer is "there's no money until January," you have not lost anything — you've learned that the pilot should run in November, not now, and you've saved yourself a quarter of unpaid implementation work.

Four for four and you have a real evaluation. Two or fewer and you are being parked, politely, and the correct response is not to walk away but to change what you're selling — sell the decision, not the trial.

Price the pilot

The fastest way to find out whether a pilot is real is to attach a price to it. Not because you need the money. Because money is the only reliable proxy for internal seriousness. A buyer who will not spend anything at all will also not spend attention, and attention is what makes a pilot succeed.

A few principles I hold to.

Make the pilot fee credit fully against the first-year contract. This removes the entire objection. The buyer is not paying extra for the privilege of evaluating you — they are prepaying a portion of a purchase they may or may not complete. Say that out loud: "every dollar of it comes off year one."

Size it to land under your sponsor's own signing authority. The whole point is that your champion can approve it without a committee. If the pilot fee triggers procurement, you have built a second sales cycle in front of your sales cycle and you'd have been better off going free.

And scope the paid pilot narrower than the free one you were about to give away. Paid means supported, configured, with your team in the room. Free means self-serve and best-effort. Buyers understand that trade instantly because it's how they buy everything else.

"I can do this two ways. There's a self-serve trial — you get a sandbox, docs, and I'll answer email. Most teams your size don't get much out of that because nobody has time to drive it. Or we do a scoped four-week pilot where my team does the setup, sits in on your Monday standup, and builds the report your VP actually wants to see. That one's a fee, and it comes off year one in full. Which fits how your team works?"

Giving them a real free option makes the paid option a choice rather than a squeeze. In my experience the buyers who are serious pick the paid one without much hesitation, and the buyers who pick free tell you exactly where you stand — which is worth knowing in week one instead of week twelve.

One warning. Do not let the pilot fee become the negotiation. The pilot price is not your price. If you discount the pilot heavily to get it started, you've anchored low on a number the buyer will remember when the real contract comes up, and you'll spend the back half of the deal clawing back margin. That is the same discipline as holding your number after a technical win, and if you sell software the mechanics in the SaaS pricing negotiation script apply almost word for word to pilot pricing — the concession you make to start is the concession you defend forever.

Converting a free pilot you already agreed to

Most reps reading this are not at the start. They already said yes, three weeks ago, with no exec, no threshold, and no end date. That's recoverable, but you have to be willing to reopen a conversation you'd rather leave alone.

Start by manufacturing the artifacts you skipped. Send a short recap email that asserts the structure and invites correction: here's what we're testing, here's what good looks like, here's the date we'll decide, here's who I understand is watching. People will correct a wrong statement far faster than they'll answer an open question. If your champion writes back "actually Dana is the one who cares about this," you just got your exec sponsor for free.

Then use the midpoint. Halfway through any pilot, schedule a checkpoint that is explicitly about the decision, not the product. Not "how's it going" — you already know how it's going. It's about what happens on the other side.

"We're two weeks in and the usage looks like what we hoped. I want to spend this call on what happens after the fifteenth rather than on features. If the results hold, what's the path to getting this signed, who else has to see it, and how long does that path take? I'd rather start that clock now in parallel than wait until we're done and add another month."

Running the commercial track in parallel with the technical track is the single biggest change I'd make to how most reps run pilots. Security review, legal redlines, vendor onboarding, procurement — none of that needs the pilot to be finished. All of it takes weeks. If you wait until the results are in, you have handed the deal to somebody's queue.

If the buyer is in a regulated or heavily procured environment, that parallel track is not optional. In life sciences the clinical ops technical win and the commercial close are two different fights with two different people, which is the whole premise behind the pharma pricing negotiation script, and utilities buyers run on procurement calendars that will happily swallow a good pilot result whole — the energy and utilities version walks the same ground.

The sentence that trades scope for commitment

This is the one to memorize. It comes up when a buyer asks you to extend a pilot, widen it to another team, add an integration, or roll it into a second phase — which is the most common way free pilots become permanent.

The instinct is to say yes, because saying yes feels like momentum and saying no feels like risking the deal. But every unpaid expansion resets the clock and teaches the buyer that more of your product costs nothing.

Here is the trade:

"I can absolutely do that. Here's my constraint — everything past the original scope needs a commercial commitment behind it, because I can't keep pulling my engineers onto an evaluation with no end. So: I'll extend to the second team and add the integration, and in exchange I need a signed order form with a start date the week the pilot ends. If it doesn't work, the order form has an out. But I need the paper now, not later."

Read what that actually does. You never said no. You gave them more than they asked for. You attached a price that isn't money — it's a signature — and you gave them an escape hatch so the signature isn't scary. And you named your constraint honestly rather than inventing a policy, which buyers can smell.

If they take the trade, you have a real deal with a real date. If they won't sign anything at all, in exchange for anything at all, you have your answer, and the kindest thing you can do for your own quarter is stop building reports for a decision nobody is planning to make.

The pilot itself was never the point. The point is whether there is a decision on the other side of it. Ask the four questions early enough and you'll spend your pilots on deals that close, and spend your Tuesdays prospecting instead of writing summary decks nobody opens.

What I'd do next

If I were working on this, I wouldn't reread it. I'd say it out loud until it stops sounding like a script — especially the exec sponsor question and the scope-for-commitment trade, because both of them feel confrontational the first ten times you say them and completely normal after that. That's the gap I built DrillCall to close: you run the objection live against an AI buyer who pushes back, you hear yourself flinch, and you fix it before it costs you a real pilot. Pick one of the four questions, drill it this week, and use it on the next call where somebody says the word.