How to turn customer interest into a useful paid pilot
Scope a first engagement that tests value, protects delivery time and gives both sides a clear decision at the end.
Start with the job the customer wants done#
Interest becomes commercially useful when both sides can name a job, a responsible person and a next decision. A good pilot is a bounded engagement with a clear value question. It might test a workflow in one team, deliver a specific consulting output or service one location.
Do not propose a pilot simply because a prospect will not buy the full offer. First ask what uncertainty prevents a decision. Is it performance, fit with an existing process, implementation effort, trust in your team or approval from someone else? A small test should answer that uncertainty.
Zapier's first-paying-customer account is a useful historical reminder that delivering and supporting the requested work matters after a person agrees to pay. It does not set your price or establish a normal conversion rate.
A paid-pilot plan connects one customer question to bounded work and an agreed decision at the end.
Write the pilot on one page#
Use the customer's actual situation rather than a generic proposal template. Ask them to confirm it before treating the pilot as agreed.
| Field | What to specify |
|---|---|
| Value question | What will this engagement help the customer decide? |
| Scope | One workflow, location, team or deliverable |
| Owner | Who supplies inputs and who can accept the work? |
| Inputs | Access, data, time and dependencies actually needed |
| Success measure | Observable result plus how it will be measured |
| Delivery window | A realistic start, completion and review date |
| Commercial terms | Your agreed price, payment and included work |
| Boundaries | What is outside scope and how changes are handled |
| End decision | Continue, change scope, stop or buy the next engagement |
A software pilot might examine the time needed to complete a repeatable process and whether the intended users can operate it. An agency pilot might produce one defined asset with agreed acceptance criteria. A maintenance provider might assess and service a defined set of equipment. Avoid using the same metric for all three.
Establish the starting position#
A comparison needs a baseline. If the customer wants a faster process, document the current process and how long comparable work takes. If they want better quality, agree what a usable output looks like. If the starting position cannot be measured, say so and choose an observable test instead.
Make the customer's required effort visible. A “small” pilot that needs a month of their engineering time is not small for them. Identify the minimum input that lets you test the value question. Use authorised data and access; do not put private customer material into public examples.
Do not invent a percentage improvement to make the proposal persuasive. A target is something to test, and a reported result needs actual evidence.
Make delivery and payment workable#
Choose commercial terms that cover your work and that the customer understands. Include implementation, support, revision and review time in your internal estimate. State what happens if a prerequisite is late and how extra work will be approved.
There is no universal pilot price, duration or discount. A trial that costs little to deliver and a specialist engagement requiring several people need different decisions. Confirm the appropriate contract and payment arrangements for your business before beginning. Do not let an agent agree terms or collect money on your behalf without explicit authority.
Run the pilot as a decision process#
At the start, confirm the agreed scope and inputs. During delivery, keep an issue log: observed problem, effect on the value question, owner and next action. Escalate a scope change rather than absorbing it silently.
At the review, compare the agreed measure with what happened. Include limitations, incomplete work and the customer's own assessment. Separate your delivery quality from dependencies neither side controlled.
Choose the next step together. A useful pilot can end with “stop” if the fit is wrong. It can also reveal that another team, scope or timing is more appropriate. Record the decision instead of reporting every completed pilot as a successful sale.
Use Kite for the conversation that precedes the pilot#
Kite can help you meet qualified people with a reason to do business with you. Your mission's Introduction criteria should describe willingness to discuss the relevant problem and your actual required fit. A pilot purchase is a later commercial decision, not the definition of an Introduction.
Review the Introduction and its context, then use your own confirmed offer to propose a next step. Your pilot brief is ready when the customer, your delivery owner and your commercial owner can all describe the same engagement.
Your readiness check
0 of 4 checked
A clear task to copy
Reference: https://kitegtm.com/university/guides/turn-interest-into-paid-pilot. Read the current guide and cite its section URLs and version. If the reference is unavailable, state that limitation instead of inventing its instructions. Using the customer situation and offer details I provide, draft a one-page paid-pilot brief. Include the value question, scope, customer owner, inputs, baseline, measure, delivery window, commercial terms to confirm, exclusions, issue log and end decision. Mark missing facts. Do not invent prices or results, accept terms, take payment, request access or send the proposal. Keep an Introduction separate from a sale.
This prepares guidance. Use the controls in your Kite workspace for account changes and starting work.
Your experience should make the next step clearer.
About this guide and its sources
Sources used to write and check this guide.
- Kite V1 product explanationChecked 2026-10-10
- What counts as an IntroductionChecked 2026-10-16
- How Andrew Warner became Zapier's first paying customerChecked 2026-10-14
- Introduction counting owner decision, October 15Checked 2026-10-16