Turn a SaaS pilot or proof of concept into a paid contract
A pilot plan with agreed success criteria, a conversion path to a paid contract, and the check-ins that keep it on track.
The prompt
Help me structure a pilot or proof of concept (POC) so it converts into a paid SaaS contract.
Prospect and use case: [company, team, problem they want solved]
Who's involved: [champion, economic buyer, IT or security, end users]
Pilot scope we're considering: [users, workflows, integrations, length]
Paid or free pilot: [and the price if paid]
Expected contract after the pilot: [plan, seats or usage, annual value]
What could block a purchase: [security review, budget cycle, data access, competing tool]
Create:
1. A one-page pilot agreement summary: goals, scope, in and out of scope, timeline (keep it short, usually 30-60 days), responsibilities on both sides, and data access needs.
2. Success criteria the buyer signs off on before starting: 3-5 measurable outcomes with baseline, target, and how each is measured. Reject vague criteria like "users like it".
3. Pre-agreed conversion terms: what happens if criteria are met (contract start date, price, pilot fee credited or not), and the decision date.
4. A parallel-path plan: start security review, legal redlines, and procurement during the pilot, not after.
5. A week-by-week plan with check-ins, usage reviews, and an early-warning list (low logins, missing integration, champion silent).
6. A results readout outline for the decision meeting, tying outcomes to the buyer's business case.
7. Pilot traps to avoid: open-ended free pilots, too many users, no executive sponsor, success measured only by the champion.
Draft the email that proposes this pilot structure to my champion. Do not invent results; leave [ADD] placeholders.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Sales prompts
What to fill in
- company, team, problem they want solved
- champion, economic buyer, IT or security, end users
- users, workflows, integrations, length
- and the price if paid
- plan, seats or usage, annual value
- security review, budget cycle, data access, competing tool
- ADD
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Build a mutual action plan with a buyer to close on timeA shared, dated close plan with the buyer covering every step to go-live, written so the buyer will actually use it.
- Build a sales territory or account planAllocates accounts, sets priorities, and plans coverage and targets for a territory.
- Prepare a price reduction conversation for a stale listingA data-backed diagnosis of why a listing isn't selling and a respectful script to recommend a price or strategy change.
- Pitch my product to a retail buyer to win shelf spaceA buyer-focused pitch, sell sheet, margin table, and test proposal for getting a consumer product stocked by a retailer.