What's the right way to handle a deal where the buyer wants a 6-month free pilot?

Why a Free Six-Month Pilot Backfires

The instinct to say yes is understandable. Free feels like the friction-free path to a logo, a case study, or a foot in the door at a strategic account. In practice, the free six-month pilot damages the deal on both sides of the table, and it does so quietly enough that you often don't notice until month five.

It compresses your effective evaluation window. Onboarding, data integration, and user provisioning routinely consume the first four to eight weeks of any B2B software deployment. In a 60-day paid pilot, that ramp is a feature — it forces both teams to move. In a six-month free pilot, the ramp becomes an excuse to drift. The buyer's champion has no urgency, so integration slips, adoption stalls, and the "value" you were supposed to prove never gets a fair test. You then arrive at month five with weak usage data and a buyer who says, reasonably, "we didn't really get to try it."

It removes the commitment signal. A buyer who has paid even a small fee behaves differently than one who hasn't. Paying customers assign an internal owner, show up to check-ins, escalate integration blockers, and defend the tool internally. Free-pilot users deprioritize all of that the moment something more urgent lands on their plate — which, over six months, it always does. The fee isn't primarily about the money; it is a forcing function for internal accountability on the buyer's side.

It anchors the buyer to a discount mindset. Once someone has used your product free for six months, the psychological reference price is zero. When you finally quote list, they experience it as a price *increase* rather than a fair price. You will hear "we've been using it and it's fine, but we can't justify that number" — and now you are negotiating from a floor you set yourself. Free usage teaches the buyer that your software is a commodity to be extracted cheaply, not an investment with an ROI.

It exposes you to champion attrition. Six months is long enough for org charts to change. The average tenure of individual contributors and mid-level managers in many go-to-market functions is well under two years, which means the person who sponsored the pilot has a real chance of leaving, changing roles, or losing budget authority before it ends. When your champion evaporates, a free pilot has no contractual gravity to keep the deal alive — there is no signed commitment, no fee already spent, nothing for a successor to inherit except a tool nobody remembers approving.

It quietly burns real money. Free does not mean costless to *you*. Every pilot consumes onboarding engineering, customer success hours, support tickets, and infrastructure. Doubling the pilot length roughly doubles that fully loaded cost while generating exactly zero recognized revenue against it. Under revenue-recognition standards like ASC 606, a free arrangement produces no bookings to recognize, so the account sits on your P&L as pure cost for half a year with only a probability-weighted hope of conversion attached.

The Deal Economics: Run the Numbers

The fastest way to win the internal argument for a paid pilot — and the buyer-facing argument too — is to put the economics on paper. The exact figures depend on your price point and cost structure, but the *shape* of the comparison is remarkably stable across mid-market B2B software. Below is an illustrative model for a hypothetical deal targeting roughly $60K in year-one annual recurring revenue. Treat the numbers as a template to fill in with your own actuals, not as external benchmarks.

Two dynamics drive the gap. First, the free pilot *lengthens* the period over which you carry loaded customer-success cost with no offsetting revenue, which pushes your customer-acquisition-cost payback further out. A healthy SaaS CAC payback typically lands somewhere in the range of roughly 12 to 18 months; a six-month free pilot bolted onto the front of that can push a marginal deal into "never pays back" territory once you account for the deals your CS team *couldn't* work because they were babysitting a free trial.

Second, the paid pilot self-selects for higher-intent buyers. The willingness to pay even a small, fully-creditable fee is one of the cleanest qualification signals available. Buyers who say yes to a credited pilot fee are, in aggregate, far likelier to convert than buyers who insist on free — not because the fee changes their mind, but because the buyers who were only ever going to extract free usage filter themselves out at the ask.

The practical takeaway: build a one-page version of this worksheet for your own price point and bring it to deal reviews. When a rep proposes a free pilot, the worksheet reframes the conversation from "do we want this logo?" to "are we willing to spend $28K of loaded cost over six months for a sub-coin-flip chance at a deal we could structure better?"

Buyer Psychology: Why the Ask Feels Reasonable

The buyer asking for a free pilot usually isn't being adversarial. They are optimizing rationally under a set of predictable cognitive biases and real internal constraints. Understanding the *why* lets you counter the ask without turning it into a standoff.

Loss aversion. Paying for software the organization might not adopt feels, to the buyer, like a concrete loss — real budget spent on a maybe. Failing to extract value from a *free* pilot feels like a loss of zero. Even when the expected value of committing is clearly higher, the buyer instinctively prefers the option with no visible downside. The foundational work on loss aversion and prospect theory explains why the pain of a $12K spend looms larger than the equivalent upside. Your counter is the credit-back structure: it collapses the perceived loss, because the buyer pays nothing net if they proceed.

Status-quo bias. The buyer's current toolset — even if it is a spreadsheet and three manual processes — works "well enough," and switching costs feel scary. A pilot's real job is to make the status quo feel expensive by demonstrating a concrete, near-term win. This is why *phased* value delivery matters more than showing every feature: if month one produces a measurable lift in something the buyer already cares about (forecast accuracy, response time, hours saved), the status quo stops looking free.

Hyperbolic discounting. People overweight certainty today relative to uncertain gains tomorrow. "Spend nothing now" is certain; "get ROI in six months" is not. The buyer discounts the future ROI steeply, which makes free-and-later look better than paid-and-sooner. You counter this by pulling the payoff forward — concrete wins in the first 30 days, not a vague promise for month six.

Reciprocity, used deliberately. When you *give* the buyer something of value — a credited pilot fee, a locked expansion price, pre-cleared security paperwork — you create a light obligation to reciprocate with commitment. A free pilot short-circuits this loop entirely, because you've given away everything up front and left the buyer nothing to reciprocate. A structured paid pilot with a genuine concession baked in ("we'll credit the entire fee, and we'll hold this price for you") activates reciprocity in your favor.

Real internal constraints. Sometimes the free ask is genuinely about budget timing — the money exists in next quarter's plan, not this one — or about needing internal proof to unlock funds. These are legitimate, and they are workable: a paid pilot with a deferred or credited fee, a start date aligned to the budget cycle, or a smaller initial scope can honor the constraint without giving away six months. The way to tell the difference between a real constraint and a stalling tactic is qualification, which is why you run a rigorous discovery pass — using a framework like MEDDPICC, with particular attention to the Decision Process, Economic Buyer, and Paper Process — *before* you quote any pilot at all.

Structuring the Paid Pilot for Conversion

Once you've reframed away from free, the structure of the pilot determines whether it converts. Five components do the heavy lifting.

1. A service fee, not a discount. Charge a real pilot fee — sized to be meaningful but not a procurement obstacle — and make it fully creditable against year one upon conversion. The framing to the buyer is: "This isn't a cost; it's a deposit against your subscription. If you move forward, it's net-zero. If we're wrong and you walk, we've each invested in finding out." A fee also keeps the pilot below heavyweight procurement thresholds at many organizations, which speeds contracting. Practitioner communities focused on go-to-market economics, such as SaaStr, have long argued that even a small paid commitment changes buyer behavior more than any messaging can.

2. A written mutual success plan. This is the single highest-leverage document in the whole motion. Co-author a plan with the buyer that names 3 to 5 quantified success criteria, each with a threshold and a measurement method, and each agreed in writing. Vague criteria ("see if it helps") are useless; sharp ones ("reduce manual data-entry time by 30%," "cut lead response time from 4 hours to under 1," "achieve 70% weekly active usage across the pilot team") are the objective standard that triggers conversion. Crucially, the buyer must sign off on *what happens when the criteria are met* — ideally an automatic transition to a paid subscription — so success isn't the start of a new negotiation.

3. Phased feature access tied to milestones. Don't hand over the entire platform on day one. Gate access so each phase corresponds to a value milestone and a success criterion. A representative sequence: month one delivers the core workflow and the fastest measurable win; month two adds analytics and reporting once the core is adopted; a later phase unlocks advanced or AI capabilities as an expansion carrot. Phasing does three things — it prevents overwhelm, it maps usage to proof points, and it preserves upsell surface for the expansion conversation.

4. Pre-locked expansion mechanics. Decide, in the original pilot agreement, exactly what the full deal looks like: the expansion price, the term, the scope, and the conversion trigger. This is the step most teams skip, and it is where good pilots die — the metrics hit, everyone is happy, and then procurement reopens pricing from scratch and the deal stalls for a quarter. Lock it up front. Below is an illustrative timeline for a 60-to-90-day pilot with a defined conversion path.

5. A pricing ladder with a clear upside. Structure the numbers so the pilot is the cheapest, most-committed entry point and expansion is pre-discounted relative to it. For example: a modest creditable pilot fee for the initial 60-to-90-day scope, a defined expansion price for the department rollout, and a full-organization tier beyond that. The buyer should be able to see the whole staircase on day one, which turns the pilot from a dead-end trial into the first rung of a known path.

The Negotiation Playbook: Concession Sequencing

The most common way sellers lose value in pilot deals is by conceding reactively — giving on price the moment the buyer pushes, without trading for anything. The discipline is simple: never give a concession without getting something of equal or greater value in return, and plan every trade before the call. Map your concession menu in advance so you are never improvising under pressure.

Here is the concession map in table form. The left column is what the buyer asks for; the middle is what you never simply give away; the right is the trade you offer instead.

A few negotiation counters worth having ready as verbatim language:

• *"We need the full six months."* → "The good news is you don't. A focused 60-day pilot gets you decision-ready data in eight weeks — and it keeps your team's urgency high, which is what actually produces a fair test. Six months tends to let the evaluation drift."
• *"Discount the pilot fee."* → "The fee is fully credited to year one, so if you proceed it costs you nothing net. What I *can* do is lock your expansion price today so there are no surprises later."
• *"We want every feature from day one."* → "Month one gets you about 70% of the impact from the core workflow. We'll open analytics and the advanced modules as you hit each milestone, so nothing gets in your way before you've adopted the basics."
• *"Our legal won't sign success metrics."* → "That's fine — but success-based structures are how we justify the credit-back and the held pricing. Without agreed criteria, we'd move to standard list terms with no value-based discount."

When the buyer's executive pushes back, escalate seller-executive to buyer-executive rather than letting a rep absorb pressure alone. A VP-to-VP framing on the credit-back — "we're trading the entire pilot fee against year one; if your team validates the metrics you're net-zero, and if we're wrong you walk and we eat the onboarding cost — that symmetry is what lets us commit our success team" — reframes the paid pilot as a *shared* risk rather than a seller demand.

Legal, Procurement, and Contract Clauses

Most pilots don't die in the demo; they die in contracting. Pre-empt the paper problems before they surface.

Keep the paper light where you can. For a small pilot fee, push for a simple order form that references your standard online terms rather than a full master services agreement — order-form-only deals close materially faster because they skip the redline cycle. When a buyer's procurement requires an MSA, work from a recognized, balanced framework rather than starting from scratch; standards bodies like World Commerce & Contracting publish contracting benchmarks and template language that both sides tend to accept as fair.

Clear security early. For any buyer with a security review — and increasingly that's everyone — submit your SOC 2 report, a completed security questionnaire (the Cloud Security Alliance's CAIQ / Cloud Controls Matrix is a widely accepted standard), and a data-processing addendum on the *first day of discovery*, not after the buyer decides to proceed. Security review is frequently the longest pole in the tent; starting it in parallel with the technical evaluation can save weeks.

Pre-write the pilot agreement clauses. Have standard, reusable language ready so contracting is a fill-in-the-blanks exercise:

1. Pilot term and auto-conversion. Define the pilot term (e.g., "60 days from the Effective Date") and specify that the order form converts to an annual subscription at the pre-agreed expansion price on the day after expiration *unless* the customer gives written notice of non-conversion a set number of days prior.
2. Success criteria by reference. Point to the mutual success plan as an attached exhibit that governs pilot outcomes, so the criteria live in one maintained document.
3. Pilot-fee credit. State plainly that the pilot fee is credited dollar-for-dollar against year-one subscription fees upon conversion.
4. Feature scope. Enumerate the modules included in the pilot in an exhibit, so phased access is contractually clear.
5. Data handling on non-conversion. Specify how customer data is exported and the timeframe for deletion if the buyer walks — this reassures security teams and removes a common late-stage objection.
6. Guard your pricing. Block any most-favored-nation or price-ratchet clause that would tie your expansion or renewal pricing back to the discounted pilot fee.

The unifying principle: do the legal and security work *once*, up front, covering both the pilot and the expansion in the same paper. That way, when the success criteria hit, there is no second contracting cycle — the deal simply converts.

Red Flags, Bear Cases, and When to Walk Away

Structure only works if you're honest about when the deal isn't real. Watch for these signals.

Disqualifying red flags:

• "We need six months" paired with "we'll decide by month four" — the extra runway is the point, not the evaluation.
• No named executive sponsor and no identified economic buyer for the expansion.
• Refusal to agree to *any* success criteria — if the buyer won't define what winning looks like, they're not evaluating, they're extracting.
• Refusal to accept a credit-back structure, which should be a near-costless yes for a serious buyer.
• The buyer is already paying a direct competitor and wants your product free "to compare" with no intent to switch budgets.

Bear cases and how to mitigate them:

• *Champion churns mid-pilot.* Mitigate by naming a co-sponsor and getting the success plan signed at the executive level, so the deal survives one person leaving.
• *Criteria prove out but procurement stalls.* Mitigate by locking expansion pricing and clearing security in the *original* agreement — the whole reason to pre-write the paper.
• *The pilot fee itself triggers heavyweight procurement.* Mitigate by keeping the fee under the buyer's PO threshold, or structuring it as a credit so it reads as a deposit rather than a new spend.

When free actually can be worth it. There are narrow, legitimate exceptions. A genuinely strategic logo that will produce a strong reference or case study, or a beachhead account in a new market you're deliberately entering, can justify giving up revenue. Even then, protect yourself: cap the scope to a single department or use case rather than the whole organization, keep the term short, and *still* attach written success criteria and a defined conversion path. "Free" should never mean "unstructured." The moment a free pilot has no criteria, no sponsor, and no end state, it stops being a strategic investment and becomes a subsidy.

The bottom line holds across all of it: a six-month free pilot is a budget deferral wearing an evaluation's clothes. Charge for the pilot, shorten it, lock the metrics and the expansion paper on day one, phase the access, and sequence your concessions deliberately. You'll filter out the tire-kickers, accelerate the buyers who are real, and anchor your pricing on the upside instead of on zero.

FAQ

Why would a serious buyer ask for a six-month free pilot?

Usually to de-risk a purchase they're genuinely interested in but haven't fully funded or internally sold. In enterprise deals, budgets are often locked a cycle ahead, trust hasn't been established, and the champion needs internal proof before they can unlock money. The free ask is frequently a proxy for "we want this but can't commit budget yet." The right response isn't to refuse the underlying need — it's to meet it with a paid-but-credited pilot, a start date aligned to their budget cycle, or a smaller initial scope, so you honor the real constraint without giving away six months of free usage.

Should I ever agree to a completely free pilot?

Rarely, and only with structure. A free pilot can make sense for a strategic reference logo or a beachhead in a new market — but even then you should cap the scope to one department or use case, keep the term short, attach written success criteria, and define the conversion path up front. "Free" should never mean "no criteria, no sponsor, no end state." If a buyer wants free *and* refuses all of those guardrails, that's not an evaluation; it's a subsidy, and you should decline.

What's a fair alternative to offer instead?

A paid proof-of-value: a 30-to-90-day pilot with a modest fee that is fully credited against year one upon conversion, plus a mutual success plan and pre-locked expansion pricing. This framing shows good faith and shares the risk — the buyer pays nothing net if they proceed, and you're protected if they don't. Most serious buyers accept a paid pilot readily once you frame the fee as a creditable deposit rather than a cost. If a buyer won't accept even a fully-credited fee, treat that as a qualification signal.

How do I set success criteria that actually work?

Define 3 to 5 measurable outcomes the buyer agrees to in writing, each with a numeric threshold and a clear measurement method — for example, "reduce manual data-entry time by 30%," "cut lead response time from 4 hours to under 1," or "reach 70% weekly active usage across the pilot team." Tie each to a timeframe, and — critically — get the buyer to agree in advance on what happens when the criteria are met, ideally an automatic conversion to a paid subscription. Vague goals like "see if it helps" give you nothing to convert on; sharp, quantified thresholds keep both sides accountable and remove the "we're not sure" exit at the end.

What if the buyer insists on free with no strings attached?

Hold your position and propose the shorter, paid, fully-credited alternative instead. Explain that a long free period with no criteria produces a weak evaluation for *them* as much as a bad outcome for you — no urgency, drifting integration, and no objective basis to make a decision. If they still won't engage with any structure, that refusal is diagnostic: a buyer who won't commit a creditable fee, name a signer, or agree on what success looks like is usually not a real near-term deal. It's better to know that in week one than in month five.

How long should a software pilot actually be?

For most B2B software, 30 to 90 days is the right window, with 60 days being a common sweet spot. That's long enough to get through onboarding and integration and to generate real usage data, but short enough to keep both teams urgent and focused. Six months rarely produces a *better* decision — it mostly produces drift, champion turnover risk, and anchoring damage. If your product genuinely requires a longer ramp (deep integrations, seasonal data cycles), extend the term deliberately and keep it paid and criteria-bound rather than defaulting to a long free trial.

Sources

• Gartner — The B2B Buying Journey — research on how B2B buyers evaluate vendors, including how little of the buying cycle is spent with any single supplier.
• Harvard Business Review — Negotiations — practitioner guidance on concession strategy, framing, and buyer-seller negotiation dynamics.
• FASB — Financial Accounting Standards Board (ASC 606) — the revenue-recognition standard governing how (and whether) pilot and free arrangements are recognized as revenue.
• MEDDICC / MEDDPICC — the qualification framework for validating decision process, economic buyer, and paper process before committing to a pilot.
• World Commerce & Contracting — contracting benchmarks and template frameworks for order forms, MSAs, and pilot agreements.
• Cloud Security Alliance — the Cloud Controls Matrix and CAIQ security questionnaire standards used to pre-clear vendor security reviews.
• SaaStr — go-to-market and SaaS-economics commentary on pilot structuring, conversion, and the value of paid commitment signals.

Related on PULSE

• [How do I structure an enterprise pilot that converts to a paid contract?](/knowledge/q133)
• [How do you calculate the true cost of a free trial motion vs a pilot program?](/knowledge/q9776)
• [What product-usage signals most reliably predict 6-month churn in B2B SaaS?](/knowledge/q520)
• [What's the right way to handle a deal where the buyer wants to talk to your CEO every week?](/knowledge/q217)
• [What is the realistic 6-month operating cost of running both HubSpot and Salesforce in parallel during a CRM migration cutover?](/knowledge/q9513)