A startup pilot proposal should define one customer problem, a bounded test, the work each side will contribute and the evidence needed to decide what happens afterward. The goal is to make a pilot useful before either team commits to a larger rollout.
A proposal is a working commercial brief, not a substitute for approved contract terms. Keep legal, security, procurement and data-use decisions with the appropriate people. Use the original template below to make those decisions visible rather than silently assuming them.
Start with a decision, not a feature tour
“Try our platform for a month” leaves the customer to invent the purpose. “Test whether the dispatch team can identify an owner for unresolved requests during its morning review” gives the pilot a specific question.
Define a starting condition and a way to observe the result. If the customer cannot provide the necessary access or permitted data, narrow the experiment. A small test with useful evidence is better than a broad implementation that nobody can evaluate.
Copy this pilot proposal
| Section | What to write |
|---|---|
| Customer problem | The observed workflow problem and who experiences it |
| Pilot decision | What the customer will be able to decide after the test |
| Included scope | Team, use case, materials and activities covered |
| Out of scope | Work that the pilot does not include |
| Starting evidence | The current process and how it will be observed |
| Success measures | Defined measures, source, observation window and reviewer |
| Responsibilities | Named owner and contribution from each organization |
| Access and dependencies | Approvals, permitted data and preparation needed |
| Timing | Start, check-in, review and close-out dates |
| Commercial questions | Proposed fees, support and rollout questions requiring approval |
| Exit and next decision | How to stop, return materials and discuss continuation |
Attach the smallest useful supporting example. Do not include customer information that the recipient is not authorized to receive.
Worked fictional example: request ownership
Imagine a startup testing a request-coordination product with a service team. The pilot includes one team and one daily review. It excludes customer billing, production-system changes and automatic external messaging.
The teams agree to observe whether requests have a named owner and whether unresolved requests remain visible. Those are pilot measures, not a promise of a percentage efficiency gain. Before starting, they identify who will record the baseline and who will review the close-out.
| Review point | Evidence | Possible decision |
|---|---|---|
| Before launch | A permitted sample of the current process | Confirm scope or reduce it |
| Midpoint | Owner assignment and unresolved-request records | Adjust one workflow problem |
| Close-out | Comparable records and user feedback | Stop, repeat a narrower test or discuss rollout |
The result can be “not enough evidence.” Do not rewrite an incomplete pilot as a successful deployment.
Send a concise proposal note
Hi [Name],
Attached is a working pilot brief for [specific workflow]. It defines the proposed scope, responsibilities and evidence for a close-out decision.
Could you review the customer-owner, access and measurement sections before we choose a start date? The commercial and data-use questions still need the appropriate approvals.
Thanks, [Name]
Use this after a real discussion; the example is illustrative. A sent proposal is not an accepted pilot. Record feedback, approval and launch as separate states.
Keep the pilot context connected
Ask Aurora to prepare a draft from the agreed notes, flag missing responsibilities and link each proposed measure to the supporting discussion. You review scope, claims and outgoing messages. Finta CRM can keep the customer relationship and next step together, while Documents holds the approved brief.
When the pilot exposes a learning gap, return to the customer discovery worksheet. When you are preparing investor evidence, use the product-market-fit evidence lesson, distinguishing pilot participation from contracted revenue.