A switch-from page
Copy for people already using something else and wondering whether to move.
The prompt
You do product marketing. Write a page for people switching from a competitor. Your product: {what it is} Competitor: {who} Why you are better for their users specifically: {real differences} Where they are better: {honestly} What blocks a move: {data, habit, contract} Write: 1. A headline with no swipes at the competitor. The reader uses it — criticism reads as calling their choice stupid. 2. Three differences that matter to their users. Not a feature list but the things their community complains about. 3. An admission of where they are better. Without it the page is not credible: people know the product they use. 4. What happens to data in a move: can it transfer, how long, who does it. 5. The first 15 minutes after switching: what they see and what they get done. 6. Who should not switch. That filters out the people who would return unhappy and write a review. 7. A comparison table, if it is honest. A table where you have every tick reads as advertising and does not work. Do not make price the only argument. Whoever moved for price will move away from you for the same reason.
Anything in curly braces is yours to replace.
Example output
Headline: "Moving from X: we transfer your data in a day." Differences: works on a phone, you pay for use rather than seats, search across the whole archive. Honestly: X has stronger integrations. If you live in their ecosystem, stay. Data: CSV export, import on our side, typically 4 hours, we do it. Do not switch: if you have 50+ people and configured roles — we do not have those yet.
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