September 28, 2026
The Paid Pilot Playbook: Get Paid Before You Build
How to get your first B2B customer to pay for a small, time-boxed pilot, with scripts, pricing principles and a one-page agreement outline.
The short answer
You get your first B2B customer to pay before you build by selling a paid pilot: one clear outcome, delivered mostly by hand, for a fixed fee, over a fixed number of weeks. Pick 20 real businesses you can reach this month, send them a one-page offer, ask for payment in the meeting, and deliver the result yourself. By week 4 you have either a paying customer ready to convert, or a clean no that saves you months of building.
Why is a paid pilot better than a free one?
A paid pilot is better because payment is the only signal that separates real demand from polite interest. B2B buyers are busy and kind. They will say “sounds great, keep me posted” to almost anything that costs them nothing, and then never open it.
One founder on Indie Hackers put it bluntly after a launch that got 500 signups in 30 days and only 3 paying customers:
“In B2B, a free signup isn’t a warm lead.”Jack Builds, Indie Hackers, May 2026
A commenter on the same post replied that “1 paid pilot teaches more than 50 free signups.” When money changes hands, the buyer shows up to meetings, gives you real data and tells you what is missing. When it doesn’t, you get silence and you guess.
If you have an app that is “80% done” and zero paying customers, the problem is usually not the last 20% of the build. As another Indie Hackers founder wrote on day 35 of chasing a first customer: “I do not have a conversion problem yet, I have a distribution problem.” A paid pilot forces you to fix distribution first: real names, real conversations, a real price.
| What you learn | Free pilot or free signup | Paid pilot |
|---|---|---|
| Is the problem worth money? | Unknown: “yes” costs them nothing | Proven: they paid |
| Who signs off on spend? | You never find out | You meet the budget holder |
| Will they show up? | Often not, it’s low priority | Usually, they have skin in the game |
| What should you build? | Your guesses | What a paying buyer asked for |
| What happens at the end? | “Let me know when it’s ready” | A decision: convert or a clean no |
Proof: pre-selling before code works
Yes, serious B2B companies have started this way. According to Forbes Australia, Tracksuit, the New Zealand brand-tracking startup, signed 11 corporate customers at $10,000 each before a single line of code was written, then bootstrapped for 20 months. (The article doesn’t state the currency.) You don’t need to be Tracksuit. You need one buyer who pays.
How do you get a paid pilot? The 7-step playbook
You get a paid pilot by working a short list of real buyers, offering one outcome at one price, and asking for payment directly. Here is the sequence I recommend.
- Build a buyer list of 20 real businesses you can reach this month. Named companies and named people, not “SMEs in logistics”. Start with your own network: former employers, clients, suppliers and peers from your 10+ years in the industry. Warm beats cold every time.
- Define one outcome. Not features. One measurable result the buyer cares about, for example “cut weekly reporting time in half” or “a clean list of 50 qualified leads”. If you can’t say it in one sentence, the pilot is too big.
- Write a one-page offer doc. The problem in their words, the outcome, how you’ll deliver it, the timeframe, the price, what’s not included and how to pay. This page does most of the selling for you.
- Set a price. A fixed fee for a fixed period, tied to the outcome. See the pricing section below.
- Make the ask. Book a 20-minute call, confirm the problem, walk through the one-pager, then ask for the payment. Out loud. In my experience, many founders skip this step.
- Run the pilot by hand. Spreadsheets, email, an AI assistant and your own time. Don’t build software yet. Write down every step you repeat, because those are the only things worth building later (this is the Manual MVP approach).
- Convert or get a clean no by week 4. Book the review meeting on day one. Show the result against the success metric, then offer the full contract. A clear no is also a win: it’s cheaper than a third rebuild.
Steps 3 and 5 are where most founders stall, so I’ve put the call script and the one-page offer into a free kit.
Free Pre-Sale Kit
Get the buyer interview and one-page offer
Two pages. The 20-minute buyer interview to run with 10 people who have the problem, and the one-page pre-sale offer to send within 24 hours of a yes.
How should you price a B2B pilot?
Price a pilot as a fixed fee for a specific outcome over a fixed timeframe, with the fee credited toward the full contract if they continue. That structure keeps it easy for the buyer to say yes and hard for either side to drift.
Charge for the outcome
Price against the value of the result to their business, not your hours.
Fixed fee
One number, paid upfront or 50/50. No hourly billing, no surprises.
Time-boxed
Two to six weeks. A clear end date forces a decision.
Credit it forward
If they sign the full contract, the pilot fee comes off the first invoice.
How much? It depends on your sector and the size of the problem, and I won’t quote made-up benchmarks.
One pilot-pricing guide suggests that if a full-price pilot feels like too big an ask, a discount of 50% to 75% off the normal price for a set period is a reasonable middle ground, and to go free only if the MVP isn’t ready. My view: discount the price if you must, but never go to zero. The act of paying is the signal.
Copy-paste scripts for the paid pilot
These scripts are short on purpose. Edit the brackets, keep the structure.
1. Outreach email (warm or cold)
Subject: [their problem] at [company]
Hi [name],
I spent [X] years in [industry] and kept seeing [specific problem] cost teams like yours [time or money]. I’m now running a small number of 4-week pilots that deliver [one outcome].
It’s a fixed fee, I do most of the work, and if it doesn’t hit the agreed result, you walk away with the findings. Worth a 20-minute call next week to see if it fits?
[Your name]
2. The payment ask (in the meeting)
Say this after they agree the problem is real
“Based on what you’ve told me, the pilot would deliver [outcome] in [4] weeks for [price], credited toward the full contract if you continue. If that works, I’ll send the one-page agreement and invoice today so we can start on [date]. Shall I send it through?”
Then stop talking. Silence is part of the script.
3. Follow-up email (no reply after the call)
Subject: Pilot for [company], next step?
Hi [name], thanks again for the time on [day]. As promised, here’s the one-page pilot outline: [link]. I’m starting pilots on [date] and have room for [number] more. Is it a yes, a not now, or a no? Any of the three is helpful.
4. When they say “let me know when it’s ready”
Reply
“Totally fair. The thing is, the software gets shaped by the first few customers, so pilot clients get the result now and a say in what gets built. If I did [outcome] for you by hand over four weeks, would that be worth [price] to you? If not, what would need to be true for it to be?”
What goes in a one-page pilot agreement?
A one-page pilot agreement covers eight things: scope, success metric, duration, fee, exclusions, data, IP and what happens at the end.
| Section | What to write |
|---|---|
| Scope | What you will deliver, in plain words, and how you’ll deliver it (by hand, with tools). |
| Outcome and success metric | The one result and how you’ll both measure it, with the starting number. |
| Duration | Start date, end date and the date of the review meeting. |
| Fee and payment terms | The fixed fee, currency, whether GST or tax applies, when it’s due, and that it’s credited toward a full contract. |
| Out of scope | What you won’t do: custom software, integrations, extra users, extra weeks. |
| Data and confidentiality | What data you’ll access, how you’ll store it, who sees it and when you delete it. |
| IP ownership | Who owns the deliverables, and that you keep your own methods, templates and any product you build. |
| What happens at the end | The conversion offer, the price of the full contract, and how either side can walk away. |
Not legal advice: this is a general outline, not a contract. Have a lawyer in your market check your agreement, especially the data, privacy and IP sections, and check the local laws and regulations in every market you sell into.
Common objections, and how to answer them
In my experience, most pilot objections are about risk, not price, so answer the risk.
“We don’t pay for pilots.”
“Understood. What usually makes a pilot free for you? If it’s the risk, I can split payment 50/50, with the second half due only if we hit the agreed metric.”
“It’s too expensive.”
“Compared to what? What is [problem] costing you each month right now?” If the answer is small, they may not be your buyer.
“I need to check with my boss.”
“Great, would it help if I joined that conversation for ten minutes, or sent a one-pager they can approve?”
“Is the software ready?”
“The pilot is about the result, not the software. You’ll get [outcome] in four weeks, and your feedback shapes what we build next.”
Want help running your first paid pilot?
Sell as you build is the 12-week program for doing this with me. It includes a bonus Paid Pilot Starter Kit: B2B outreach, a paid pilot script, an offer doc, a pricing guide and a one-page pilot agreement.
See Sell as you build See the workshopsFrequently asked questions
What is a paid pilot?
A paid pilot is a short, fixed-fee trial where a business pays you to deliver one specific outcome over a set number of weeks, usually before the full product exists. It tests whether the problem is worth money and gives you a paying customer to build around.
How much should I charge for a B2B pilot?
Charge a fixed fee tied to the outcome, not your hours, for a two to six week period, and credit it toward the full contract. The right number depends on your sector and the value of the result. If full price is a stretch, discount it, but don’t make it free.
How do I get my first B2B customer before building?
List 20 real businesses you can reach this month, define one outcome, write a one-page offer, set a fixed price and ask for payment in the meeting. Deliver the pilot by hand and aim to convert or get a clear no by week 4.
Do I need a contract for a paid pilot?
Yes, keep it to one page: scope, success metric, duration, fee and payment terms, out of scope, data and confidentiality, IP ownership and what happens at the end. It’s general information, not legal advice, so have a lawyer in your market check it.
What if nobody says yes?
That is useful data. Check whether you reached the person who controls the budget, whether the outcome was specific enough and whether the problem is costly enough. If 20 real conversations produce no payment, change the offer before you build anything.
Related guides
- The Manual MVP: get paid before you write code
- Stuck at 80%: what to do when your AI-built app stops working
- What an MVP should really cost in 2026
Sources: Forbes Australia (Tracksuit pre-sales and bootstrapping, November 2024), Indie Hackers, Jack Builds (500 signups, 3 paid, and the “one paid pilot” comment), Indie Hackers, Gissur Þór Rúnarsson (distribution problem), I Want Product-Market Fit (free, discounted and paid pilots).
About the author
Matt Ainsworth is the founder of The Lean CPTO. He has 20+ years across product, technology, sales, marketing and communications in Australia and Japan (nearly a decade in Tokyo), has mentored founders for 10+ years, and has worked on both sides of the developer relationship: selling development services and building products with developers.