“Let's try it and see” sounds like an easy route to a first customer. Without a concrete agreement, it can become a delivery that never ends: extra requests, unlimited support and no useful way to decide whether to continue.
A useful pilot needs a boundary. You may not need a platform to discover the value of a small delivery, but you do need to explain its scope and review process. This guide offers a working sheet, not a contract or a promise of sales.
Choose a delivery you can observe
Paul Graham argues for manually recruiting and supporting early users. That work can bring founders closer to a customer's actual experience. Our pilot worksheet adds an operational boundary; it does not assume a manual service will eventually become scalable software.
Consider a service that turns meeting notes into a draft sales proposal. This is a hypothetical example. A pilot could cover one proposal for one person. “Improve the entire sales team's productivity” would leave you with too broad a task to evaluate.
Describe what the customer will receive and what they can do with it. A reviewable draft based on agreed inputs is an observable delivery. Extra sales or time savings are outcomes you should not promise before you can substantiate them.
Put six agreements on one page
- Participant and situation: who is involved and which specific problem the trial addresses.
- Delivery: the file, service or piece of work they will receive.
- Scope: how many items or revisions are included and what is outside the offer.
- Required cooperation: the information the customer supplies and when it is needed.
- Trial conditions: duration, agreed charge if applicable and the included support time.
- Final review: what you will observe and who decides the next step.
Do not assume another business's price is right for your first offer. Consider the work you will undertake, required tools and a scope you can sustain. Discussing a price and a concrete commitment gives you different information from receiving a compliment.
If you charge, explain exactly what is being purchased and how changes will be handled. Adapt commercial and legal terms to the actual arrangement before contracting. The worksheet structures that conversation; it does not replace an agreement.
Observe use and effort, as well as satisfaction
“They liked it” may be a valid observation, but it leaves key questions unanswered. Did they use the delivery? Which parts needed corrections? Did they need more help? What work did you perform that was missing from the offer?
For the proposal example, you could record whether the customer used the draft, what needed changing and the effort on both sides. Agree on observations before seeing the outcome. Without a comparable baseline, do not present a percentage saving as demonstrated impact.
Log exceptions too. An input that never arrives can teach you more about the service than the time required to generate a document. Repeated revisions may reflect missing context, misaligned expectations or poor quality. Understand the cause before automating it.
Decide what would justify continuing
The final review should allow three answers: continue, change the offer or stop the trial. Each can be useful if it prevents a larger investment in the wrong direction.
Continuing may mean repeating the same delivery with another customer. Changing may mean narrowing the segment, improving inputs or reducing scope. Stopping can be reasonable when the problem lacks urgency or the support burden is unsustainable.
One sale does not establish repeatable demand. Distinguish willingness to pay for exceptional personal attention from demand for a comparable delivery across customers. Both can support businesses, but they lead to different operating decisions.
Your exercise: an offer that fits on one page
Complete this sentence: “For ___, I will help ___ with ___; I will deliver ___, need ___ and review ___.” Add three exclusions and the support time you can commit.
Read the page as a customer. Do you know what you receive, what you must contribute and when the trial ends? If an answer depends on working it out later, tighten the scope.
Ramen Founders is a community for describing useful experiments honestly. Share one uncertainty about your first pilot and the boundary you have chosen. Explore our founder tools to prepare your next decision.