How to Land Your First Pilot Customers and Write a One-Page Pilot Agreement
Your first pilot customers are the most important people in your business. They give you real usage, honest feedback and, if it goes well, your first revenue and case study. But many founders handle pilots casually: no success criteria, no end date and no agreement about what happens next. This guide shows how to choose pilot customers, structure a simple offer and write a one-page pilot agreement, so the pilot produces a decision rather than a pleasant story.
Key takeaways
- Who makes a good pilot customer and where to find them.
- A pilot offer template and a one-page agreement outline.
- Success criteria and a plan to convert pilots into paying customers.
What a pilot is, and what it is not
A pilot is a time-limited trial in which a real customer uses your product for a real purpose, under agreed terms, so both sides can judge whether it works. It is not a free-for-all demo, an open-ended favour or a substitute for a finished product. The more clearly you frame it, the more useful it will be.
Who makes a good pilot customer
- Feels the pain now. They already spend time or money on the problem.
- Has authority or a champion who can decide and make time to use the product.
- Is typical of your target market, not a unique case that teaches you little.
- Will give honest feedback, including criticism.
- Is willing to commit something: time, data, a small fee or a reference if it works.
Avoid pilots with friends who will be polite but never use the product, or with huge organisations whose approval process will take months. Aim for three to five pilots, so one bad fit does not decide everything.
Where to find them
- The people you interviewed during validation. See customer interviews before you build.
- Direct outreach to a narrow niche. See cold email for first customers and LinkedIn strategy.
- Partners and communities that already serve your audience. See MVP partnerships.
- Your waitlist and landing page responses.
Craft a clear pilot offer
Your offer should fit in a few lines:
Should the pilot be free?
There is no single answer, but free pilots often attract low commitment. Options:
| Approach | Pros | Cons |
|---|---|---|
| Free pilot | Easy to say yes to | Weak commitment; unclear willingness to pay |
| Discounted paid pilot | Shows seriousness; funds learning | Harder to close |
| Full-price pilot with a guarantee | Strongest signal of value | Needs a confident, defined outcome |
| Free with a commitment | Time, data or reference promised in return | Commitments can be soft |
Even a modest fee changes behaviour. For pricing ideas, see how to charge from day one and choosing a revenue model.
The one-page pilot agreement
A short written agreement prevents most misunderstandings. Cover these points in plain language:
| Section | What to write |
|---|---|
| Purpose and scope | What the pilot covers and what it does not |
| Duration | Start date, end date and review dates |
| Participants | Who is involved on both sides, and your single point of contact |
| Success criteria | Measurable results that define a successful pilot |
| Customer commitments | Time per week, data provided, feedback calls |
| Your commitments | Setup, support response times, bug fixes |
| Fees | Free, discounted or paid, and the price if they continue |
| Data and confidentiality | What data is used, how it is protected and what happens to it at the end |
| Feedback and reference | Permission to use feedback and, if agreed, their name as a reference |
| Ending | How either side can stop, and what happens after the pilot |
This is general information, not legal advice; have a lawyer review your template, especially where personal data is involved. For wider contract topics, see SaaS contracts and terms of service.
Define success before you start
Agree two or three measurable outcomes in writing, for example:
- “Reduce time to collect client documents from five days to two.”
- “At least eight of ten staff use it weekly.”
- “Zero missed deadlines during the pilot.”
Without these, the pilot ends with a feeling, and feelings do not convert into contracts.
Run the pilot well
- Onboard personally. Do the setup together. See getting users to their first win.
- Check in weekly, briefly, with the same questions each time.
- Track usage as well as opinions. Behaviour is more honest.
- Fix the top issue fast. Responsiveness builds trust.
- Keep a decision log of requests and why you accepted or declined them.
- Review at the midpoint against the success criteria.
Converting the pilot to a paying customer
- Schedule the end-of-pilot review at the start.
- Show results against the agreed criteria, with numbers.
- Present the continuing price clearly, with a start date.
- Ask for a testimonial and introduction if they are happy. See how to get customer testimonials.
- If they decline, ask why. That answer is valuable.
Common mistakes
- No end date, so the pilot drifts.
- Building custom features for one pilot that nobody else needs.
- Skipping the conversation about price until the end.
- Counting enthusiasm as success without usage.
- Collecting too little data to learn anything.
Frequently asked questions
How many pilot customers do I need?
Three to five is a good range for most B2B products, enough to spot patterns without overwhelming you.
How long should a pilot last?
Long enough to cover a full cycle of the process you are testing, commonly several weeks. Set the end date upfront.
Should I build features pilot customers ask for?
Only if they serve your core use case and other customers would want them. Otherwise, add them to the backlog.
Ready when you are
Turn your idea into a working MVP in weeks, not months
Book a free 30-minute Idea Audit with a certified Bubble.io developer. You will leave knowing what to build, how to build it and what it will cost.
SA Solutions is a product studio led by a certified Bubble.io developer, building MVPs, SaaS platforms, portals, dashboards and internal tools for founders.