Trial-period emails
A sequence that leads to first value instead of nagging about payment.
The prompt
You are an onboarding specialist. Write the trial email sequence. Product: {what it is} Trial length: {days} First-value moment: {what the person must do to see the point} Where people get stuck: {list it} What happens at the end: {charge / lockout / downgrade} For each email: 1. The day it goes out and the reason — an event, not "day three of the trial". 2. A subject under 45 characters. 3. Body under eight lines, one action at the end. 4. Who must not receive it: anyone who already did that action. Required: 5. An email for those who never came back after signing up. 6. An email two days before the end: exactly what the person loses, concretely. 7. An email after it ends for those who did not pay — with no pressure. The sequence leads to first value, not to payment: someone who never got there will not pay however often you remind them.
Anything in curly braces is yours to replace.
Example output
Day 0, right after sign-up: "Your first result in 4 minutes" — one link, one action. Day 5, only for those who never returned: "Looks like you did not get to it. What got in the way?" — a question, not a reminder… Two days out: "Your 13 saved prompts stay; access to the PRO collection closes."
Related prompts
Your idea broken down into risks plus a one-week test plan — before you spend months.
You are a product strategist who has seen plenty of projects die. Assess my SaaS idea honestly, without cheering me on. Idea: {what the service does} For whom: {who, as narrowly as possible} What the person does today without us: {how the job gets done now} How I plan to charge: {model and price} Time and money I can spend before first revenue: {resources} Break it down: 1. The problem: does it hurt regularly, or is it a one-off inconvenience? Answer plainly. 2. Who pays: the user themselves or their manager — and why that changes the product. 3. The three main risks: why this could fail. For each — the cheapest way to test it. 4. What already exists on the market, including a spreadsheet, a notebook and "do nothing" — count those as competitors too. 5. The most dangerous assumption: the one that makes everything else pointless if it's wrong. 6. A one-week test plan: what to do on which day to get a signal without writing code. 7. The kill criterion: what result means the idea should be dropped. If the idea is weak, say so in the first paragraph.
Show sample resultHide sample
Most dangerous assumption: that the bookkeeper is allowed to change tools. The finance director decides, not them — so you sell "fewer reporting errors", not "more convenient". Kill criterion: if fewer than 3 out of 20 conversations end in "let me try it", drop the idea.
The smallest set of features you can already sell, plus what's deferred and why.
Help me draw the boundary of an MVP that can actually be shipped and sold. Product: {what the service does} The main scenario: {what the user does from login to result} Who the user is: {description} Time available for development: {timeframe} Who is building it: {one developer / a team / no-code} Do this: 1. One user path from sign-up to first value — step by step, no branches. 2. The features without which that path doesn't work. Each with a reason why it can't be dropped. 3. Features that feel mandatory but aren't needed in an MVP — and what replaces them for now (manual work, an email, a spreadsheet). 4. What to cut entirely, and why it won't stop you selling. 5. The boundaries: what the product does NOT do. Wordings for the site so nobody expects otherwise. 6. An estimate in weeks, broken down, with a note on where the estimate is least reliable. 7. What can be done by hand for the first few months instead of being automated. Rule: if a feature can be replaced by a human at launch, it does not belong in the MVP.
Show sample resultHide sample
Do it by hand: PDF export is done by support on request for the first months. Three requests a week is one hour; automating it would have cost two weeks. Boundary for the site: "We don't replace your accountant — we prepare the data for them."
A feature turned into tasks with testable criteria — including errors and empty states.
This prompt is part of the PRO collection
Unlock accessTables, relations and indexes derived from your scenarios — plus where the schema will strain.
This prompt is part of the PRO collection
Unlock access