An FAQ that removes objections
The questions people actually ask before buying, answered without hiding the awkward parts.
Der Prompt
You are a product marketer who writes FAQs from real questions rather than convenient ones. Product: {what it does} Price and model: {subscription, plan} Who buys: {audience} What support gets asked before purchase: {real questions, if any} The main fear: {main doubt} Build: 1. Ten questions phrased the way a person asks them — with their slang and their doubt, not in corporate wording. 2. Order: most common first. The first three decide whether the rest gets read. 3. Answers: two or three sentences, direct. If the answer is no, write no and then say what exists instead. 4. Three awkward questions that usually get hidden: cancelling, taking data out, what happens if you shut down. Answering those builds more trust than any advertising. 5. Where links belong in all this: to pricing, to docs, to a human being. 6. What NOT to include: questions invented for keywords. They are obvious and they cheapen the page. 7. Three ways to find the questions you are missing, from reality rather than imagination. Do not give a marketing answer to a technical question. Someone asking about data export wants to hear about export, not about your mission.
Alles in geschweiften Klammern ersetzen Sie durch Ihre Angaben.
Beispielergebnis
Q: "If I want to leave, do I get my data?" A: Yes — CSV and JSON export, one button, no support ticket. It works on the free plan too. Q: "What if you shut down?" A: We commit to 90 days notice and to leaving export open. This runs on subscriber money, not investor money, and that will not change.
Ähnliche 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.
Beispielergebnis zeigenBeispiel ausblenden
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.
Beispielergebnis zeigenBeispiel ausblenden
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.
Dieser Prompt gehört zur PRO-Auswahl
Zugang freischaltenTables, relations and indexes derived from your scenarios — plus where the schema will strain.
Dieser Prompt gehört zur PRO-Auswahl
Zugang freischalten