How to Run a Paid Pilot for B2B SaaS (Bootstrapped Guide)

Short answer: To run a paid pilot for B2B SaaS, sell a short (30 to 90 day), fixed-price trial of your product to one business customer, with one measurable success metric, a named owner on each side and a conversion date written down before you start. Credit the fee toward an annual contract so the end of the pilot is a buying decision, not a new negotiation.

Every external fact and quote below comes from the linked sources, checked on 13 Nov 2026. The advice in between is ours and is marked as such.

TL;DR#

• Charge for it. Heavybit's library puts it plainly: "Asking your customers to pay a token fee is an important qualifier for long-term successful deals" (Heavybit).
• Keep it short. The same article says "aim for a 30 day paid pilot", framed "in the context of a full year contract". Pear VC's Pepe Agell gives an upper bound: "ideally 1 month, never more than 3" (Pear VC).
• One page, signed. Success metric, duration, owners, data access, price, credit toward the contract, conversion date, exit clause. Template below.
• Find the economic buyer early. A champion who cannot sign a contract cannot convert a pilot.
• Invoice it properly. Stripe Invoicing costs 0.4% per paid invoice on Starter, plus Stripe's normal payment processing fees (Stripe Invoicing pricing).

Disclosure: ZeroRaised is a launch site for bootstrapped products and publishes this guide. We have no commercial relationship with Stripe, Heavybit or any tool mentioned here. This is general guidance, not legal or tax advice.

Why a paid pilot beats a free one#

For a bootstrapped founder, a paid pilot is both a sales tool and funding: customer money that pays for onboarding and integration work you would otherwise do for free (see our guide to ways to fund a product without venture capital).

The bigger reason is commitment. When a company pays, someone approved a budget line, so the pilot has an owner and a deadline. A free proof of concept (POC) is easy to agree to and just as easy to ignore. Our read: if a prospect will not pay a small amount to evaluate you, they are unlikely to pay a large amount to keep you. Agell, writing for Pear VC, puts the same idea more bluntly: "Humans simply don't value what they don't pay for" (Pear VC).

Pilot vs free trial vs straight annual contract#

Our read: if your product shows value without you in the loop, use a self-serve trial (see freemium vs free trial for solo founders).

How to run a paid pilot, step by step#

1. Qualify before you offer a pilot#

Offer a pilot only after a discovery call has confirmed three things: a specific, painful problem; a person who owns that problem; and a person who can sign for the budget. Nick Beecroft, writing for Heavybit on troubleshooting enterprise proofs of concept, defines the role you need: "An economic buyer, put simply, is someone who has the power to align company budget $ to pay for your solution."

If you cannot name the economic buyer, you are not ready to propose a pilot. Our read: ask "who else needs to approve a purchase like this?" on the first call, not the last.

2. Agree one success metric#

Heavybit's advice is to "Pick a single KPI that will have a measurable business impact", and it adds: "You don't necessarily have to meet your goal, you just have to show that you can move the needle in 30 days." Beecroft makes a related point: "write down the technical success criteria that align back to the business value." SaaStr's Jason Lemkin suggests asking the customer directly: "What does success look like for you at the end of this pilot?" (SaaStr).

Our read: write the metric as a number with a baseline, a target and a way to measure it. "Cut invoice matching time from about 6 hours a week to under 2, measured by the finance lead's time log" is a success criterion. "See if the team likes it" is not.

3. Set the duration and the conversion date#

Put an end date and a decision date in writing. Our read: 30 days suits products that show value quickly; if yours depends on a monthly cycle (month-end close, payroll), 60 days shows two cycles. Decide the price, credit and post-pilot annual price at the same time. Pear VC agrees on the timing: "Ideally, the annual contract value should already be discussed before the pilot begins" (Pear VC).

4. Write the one-pager and get it signed#

Use the template below as the order form, attached to your terms. If you do not have terms yet, write them before your first pilot, not during it.

Data processing. If the pilot touches personal data, expect a data processing agreement (DPA). The UK ICO states that "every time a controller uses a processor to process personal data, there must be a written contract" (ICO), a rule rooted in GDPR Article 28(3). Our read: in a typical pilot the customer is the controller and you are the processor, so have a short DPA ready, and start any security questionnaire in week one. This is not legal advice.

Signatures. A one-page order form does not need an expensive e-sign tool. Prices from each vendor's own page:

5. Invoice up front#

Send the invoice when the one-pager is signed, payable before or at kickoff. Stripe Invoicing lists "0.4%" per paid invoice on its Starter plan and "0.5%" on Plus, which adds quotes. Stripe also says "Stripe Invoicing has no fixed fees or setup costs, but Stripe Payments pricing will apply", so payment fees for your country come on top (Stripe Invoicing pricing). Our read: offer bank transfer, and never give 60-day payment terms on a 30-day pilot.

To roll the pilot into a subscription, Stripe's docs say an accepted quote can become "a recurring subscription or a one-time invoice", and that for quotes with recurring prices, "A subscription schedule is created if the effective date on the quote is in the future" (Stripe Quotes docs). Our read: send the annual contract as a quote dated to start the day after the pilot ends.

6. Kick off and run weekly check-ins#

In a 30-minute kickoff, confirm the metric, the baseline, who grants data access by when, and book every check-in plus the final review. Each week, cover progress against the metric as a number, blockers and their owners, and what the customer's team actually used. Send a three-line written summary after each call: that becomes your evidence at the end.

7. Run the conversion review#

A week before the end date, send a one-page results summary: baseline, result, what changed, and the proposed annual contract with the pilot credit applied. Then hold the review with the economic buyer present. Ask for the decision on the call. Heavybit frames the upside of this: "You'll be able to keep up your momentum and build on the results you've shown during the pilot."

How to price a paid pilot#

There is no published standard for pilot pricing, so this section is our read plus labelled example arithmetic.

Our pricing rules of thumb:

1. Anchor on the annual contract. Decide the annual price first. The pilot is a slice of it, not a separate product.
2. Make it hurt a little. The fee should need approval from someone with budget, which is the point of charging.
3. Stay under a sign-off limit. Ask your champion what they can approve without procurement. A fee under that limit can move in days instead of months.
4. Credit it. If they convert, the full pilot fee comes off the first year. Saying yes then costs less than starting over with a competitor. Pear VC recommends a clause "that credits the pilot cost toward the annual contract if the customer moves forward within a defined period" (Pear VC).
5. Do not discount the annual price to win the pilot. Agree the post-pilot price in the one-pager so the conversion is not a fresh negotiation.

Example arithmetic (illustrative, not a benchmark):

In this example, a converting customer pays the annual price for 14 months of use; a no still pays for some of your setup work.

Copy-paste pilot one-pager template#

Fill in the brackets, attach your terms, and get it signed before kickoff.

PAID PILOT: [Your product] x [Customer company]

Problem
  [One sentence: the specific problem this pilot tests.]

Success criteria
  Metric:       [e.g. hours per week spent on X]
  Baseline:     [current number, and how it was measured]
  Target:       [number that means success]
  Measured by:  [who, using what data]

Duration
  Start date:   [date]
  End date:     [date, 30-90 days later]
  Final review: [date and time, economic buyer attends]

Owners
  Customer champion:  [name, role]
  Economic buyer:     [name, role, can sign the annual contract]
  Vendor lead:        [your name]

Scope
  Included:     [users, teams, integrations, data sources]
  Not included: [custom features, extra integrations]
  Data access:  [what data, who grants it, by which date]

Commercials
  Pilot fee:          [amount], invoiced on signature, due [date]
  Credit:             100% of the pilot fee is credited to the first annual contract if signed by [conversion date]
  Post-pilot price:   [annual price and plan]
  Conversion date:    [date]

Exit
  Either party may end the pilot with [X] days' written notice.
  If the success criteria are not met, there is no obligation to buy.
  Customer data is [returned / deleted] within [X] days of the end date.

Terms
  This pilot is governed by [link to your terms of service / pilot agreement] and [DPA, if applicable].

Signed: ____________ (Customer)   ____________ (Vendor)   Date: ______

Conversion checklist#

Run this in the last two weeks of the pilot:

• Results summary sent (baseline, result, metric), champion saw it first
• Economic buyer confirmed for the final review
• Order form drafted at the one-pager price, pilot credit applied
• Security, DPA and legal review already started
• Two or three user quotes collected, with permission
• Decision asked for on the call, with a signature date

If it is a yes, ask for a reference while results are fresh.

What to do when a pilot fails#

Our read:

1. End on the agreed date and share a short written review against the metric.
2. Ask: "What would have to be true for this to be a yes?" The answer is a product gap, a timing problem or a polite no.
3. Extend only with new terms: a new end date, decision date and, ideally, a further fee.
4. Feed it back. If several pilots fail on the same gap, that is your roadmap.

Red flags#

• "Can you do a free POC first?" with no budget behind it. Offer a short paid pilot instead.
• No economic buyer. Your champion cannot name who signs.
• Procurement stalls on a small fee. The annual contract will take longer still.
• Data access that never arrives. Without data in week one, the pilot cannot prove anything.

Selling alone? See how to sell B2B SaaS as a solo founder.

Frequently asked questions#

How much should I charge for a paid pilot?#

There is no standard price. Our read: price the pilot as a slice of the annual contract you want to sign, often one to three months of the annual value, and credit it toward that contract. The fee must be high enough to need a real budget holder's approval and low enough to fit under their sign-off limit.

How long should a B2B SaaS pilot last?#

Heavybit's library suggests aiming for a 30-day paid pilot. Our read: 30 days suits products that show value quickly, while products that need data integration or a monthly business cycle may need 60 to 90 days. Longer than that and it stops being a pilot.

Should I offer a free pilot instead?#

Usually not, if you sell to businesses. A free pilot has no budget behind it, so nobody is accountable for evaluating it, and you fund the customer's experiment. Use a self-serve free trial for low-touch products and a paid pilot for sales-led deals that need setup or integration.

What paperwork do I need for a paid pilot?#

At minimum, a pilot one-pager or order form that states scope, price, dates, success criteria and the conversion terms, plus your standard terms of service or a short pilot agreement. If you will process the customer's personal data, expect a data processing agreement and possibly a security questionnaire. This is not legal advice.

What if the pilot fails?#

End it on the agreed date, run a short written review against the success criteria, and ask what would have to be true for a yes. A clear no is worth more than an endless extension. Keep the relationship, write down what you learned, and do not offer a free extension unless the scope and decision date change.

Launch the product your pilots prove#

ZeroRaised is a launch directory for products built without institutional VC. Once your first pilot customers have converted, work through how to launch a bootstrapped app, then submit your product for free. For more customer-funded growth guides, join the ZeroRaised newsletter.

Sources#

• Heavybit: How to Execute SaaS POCs that Convert, last checked 13 Nov 2026
• Heavybit: Troubleshooting Enterprise Proof of Concepts (Nick Beecroft), last checked 13 Nov 2026
• Stripe Invoicing pricing, last checked 13 Nov 2026
• Stripe Docs: How quotes work, last checked 13 Nov 2026
• Pear VC: Why pilots matter more than you think, and how to run them right (Pepe Agell), last checked 13 Nov 2026
• SaaStr: Dear SaaStr, We're Starting a Big Paid Pilot (Jason Lemkin), last checked 13 Nov 2026
• GDPR Article 28: Processor, last checked 13 Nov 2026
• ICO: When is a contract needed and why is it important?, last checked 13 Nov 2026
• Documenso pricing, last checked 13 Nov 2026
• PandaDoc pricing, last checked 13 Nov 2026
• Dropbox Sign pricing, last checked 13 Nov 2026