Validate the idea before the first line of code
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.
У фігурних дужках — те, що треба замінити на своє.
Приклад результату
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.
Показати приклад результатуСховати приклад
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.
Промт входить до PRO-добірки
Відкрити доступTables, relations and indexes derived from your scenarios — plus where the schema will strain.
Промт входить до PRO-добірки
Відкрити доступWhat to pick for your timeline and skills — and what each choice will cost you later.
Help me choose the technologies for a project and explain the price of each decision. What the product is: {description} What I can do: {languages and tools, honestly} Time to launch: {timeframe} Who will maintain it: {just me / a team / a contractor} Special requirements: {payments, files, real time, offline, integrations} Monthly infrastructure budget: {amount} Break it down: 1. The recommended set: frontend, backend, database, hosting, auth, payments, email. 2. For each — why this one in my situation, and a sensible alternative. 3. The price of the choice: what becomes awkward within a year. 4. What I shouldn't build myself but buy as a service, and what it costs. 5. What to avoid specifically in my case, and why. 6. An estimate of the infrastructure bill at 100, 1,000 and 10,000 users. 7. Which choice will be hardest to reverse later — and how to reduce that lock-in. Account for my skills: an unfamiliar technology on a short deadline is a risk, not an advantage.
Показати приклад результатуСховати приклад
Auth: a ready service, not your own. Your own means emails, password resets, sessions and leaks — two weeks of work and permanent responsibility. Hardest to replace: the database. Keep queries in one layer so a migration doesn't spread through the whole codebase.