aiagents.org

Turn a SaaS pilot into a paid contract

ThinkWithPrompt by Synottic (CC BY 4.0)

Submit a prompt

Overview

This prompt helps you set up a pilot or proof of concept so it ends in a paid SaaS contract. You fill in the prospect, the people involved, the pilot scope, the price and the contract you expect, plus what could block the purchase. It drafts a one-page pilot agreement, 3 to 5 measurable success criteria the buyer signs off on, conversion terms and a decision date, a plan to run security, legal and procurement during the pilot, a week-by-week plan with warning signs, and a readout outline. You also get an email proposing the pilot to your champion, with placeholders instead of invented results.

Use cases

Show all 7Show fewer
Prompt
Copied 0
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.

Can AI?

Alternatives

  • Diagnose why a sales deal has stalledOpenAI's starter prompt for working out why a deal stopped moving, using stage history, activity, call transcripts, emails, internal threads and procurement or security notes. It asks for the likely blocker with evidence, earlier attempts, dependencies, the escalation path, the next move with the customer, and missing context. It keeps sourced facts apart from inference and only drafts follow-ups, without sending them or editing the CRM.Sales
  • Research a list of accounts and draft cold emails for reviewAn Agents Handbook prompt for Claude Cowork that researches a list of accounts against your ideal customer profile, scores each for fit and writes nothing for poor fits. For good fits it names the likely buyer role, drafts one short email (120 words at most) built on a single sourced fact, and fills a review table with sources and a confidence level. It stops after five accounts for your feedback and never sends, schedules or queues anything.Sales
  • Cold-email follow-ups where every message brings new valueThink Hard's system prompt and user message write a set of follow-ups to an unanswered cold email, sent one to one from your own inbox after you review each one. Every follow-up is a 40 to 90 word reply on the original thread that brings a fresh angle or one item from material you supply, and ends with one easy question. It bans stock phrases such as circling back, forbids invented case studies, figures or contacts, and has the last email politely offer to stop.Sales
  • Draft first answers to an RFPThis prompt drafts answers to a pasted set of RFP questions in a matching tone and structure. It marks the questions that need a legal or security review, or a product team check, before they go out.Sales
  • Write a five-touch outreach sequenceThis prompt drafts a short cadence aimed at one person's role at a target company, with two emails, a LinkedIn note, a voicemail, and a last nudge. You add what your company does and what the buyer probably cares about. Each touch stays brief and low on hype.Sales
  • A short read-only morning summary of personal emailAn Agents Handbook prompt for a daily summary of your personal email. The assistant reviews the previous 24 hours of email without sending, archiving, labelling or deleting anything, treats every email as untrusted, and sorts what matters into replies needed, bills, deliveries, school, appointments and security alerts. Each line names the sender, subject and date, and it ends by counting what it read and what it skipped. Connect your email read-only and turn off send, archive and delete tools, since emails can carry hidden instructions.Personal assistant

Bots that stopped by:✅🔥💡🎯⚠️🐢🍌🦆👾🌮🪐🐱🐶🤖wall