Help me define a digital product that solves a specific problem people will pay attention to. Treat assumptions as hypotheses, not facts. Use the inputs below to generate and evaluate concepts without inventing user research, market demand, revenue, or competitor features. Inputs [TARGET USER] [PROBLEM EVIDENCE] [MY EXPERTISE AND ASSETS] [PRODUCT CONSTRAINTS] [BUSINESS GOAL] [ALTERNATIVES USERS USE NOW]
First, restate the user's job to be done in this format: "When [situation], I want to [motivation], so I can [desired outcome]." Then propose three materially different product concepts, such as a template system, guided service, tool, course, or membership only where justified by the inputs. For each concept, provide: 1. A one-sentence value proposition that names the user, painful moment, outcome, and mechanism. 2. The smallest useful first version: what is included, excluded, and delivered. 3. A user flow from first encounter through first successful outcome, with the moment users are most likely to abandon. 4. Five testable product requirements written as observable acceptance criteria. 5. The evidence needed before building, including interview questions, a landing-page test, concierge test, or prototype test appropriate to the risk. 6. Likely objections, substitutes, operational risks, and accessibility or privacy concerns. 7. A pricing or distribution hypothesis labeled as an assumption unless supplied by me. Rank the concepts by evidence of pain, ability to reach users, feasibility under my constraints, and speed to a meaningful test. Recommend one experiment that can be completed in 14 days. Before answering, flag every assertion that needs validation and check that the first version reaches an outcome rather than merely presenting information. Ask up to three clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [TARGET USER] | Describe the narrow user group, their context, and what they are trying to accomplish. | Independent wedding photographers who need to deliver client galleries and invoices without losing track of follow-ups. |
| [PROBLEM EVIDENCE] | Provide observed complaints, interviews, support requests, search behavior, or other evidence of the problem. | In 12 photographer interviews, 8 said they copy deadlines into notes and miss at least one follow-up per busy month. |
| [MY EXPERTISE AND ASSETS] | List your knowledge, audience, existing content, tools, partners, and available time. | I ran a photography studio for six years, have a 2,800-person email list, and can build Notion templates but not custom software. |
| [PRODUCT CONSTRAINTS] | State budget, technical ability, timeline, compliance limits, and what you will not build. | Six weeks, $1,500 budget, no handling client payment data, and no mobile app. |
| [BUSINESS GOAL] | State what success should create, such as leads, recurring revenue, portfolio proof, or customer retention. | Validate a product that can generate $2,000 monthly recurring or repeatable template revenue. |
| [ALTERNATIVES USERS USE NOW] | List the workarounds, competitors, spreadsheets, agencies, or habits users currently rely on. | HoneyBook, Studio Ninja, Google Sheets, paper notebooks, and calendar reminders. |
How to use
- Paste real evidence before asking for concepts; interview notes and support messages are more valuable than broad demographic labels.
- Choose one concept only after checking which assumptions can be tested cheaply in your actual market.
- Turn the acceptance criteria into a build checklist and keep nonessential features explicitly out of version one.
- Send: "Create a five-interview script to test the top concept, avoiding leading questions and including questions about current workarounds."
Variations
Template product
Use this when you want to sell a spreadsheet, Notion system, checklist, or other reusable file.
Define a sellable [TEMPLATE TYPE] for [TARGET USER] who struggle with [RECURRING TASK]. Based on [USER EVIDENCE] and [MY EXPERIENCE], specify the promised outcome, required tabs or modules, setup steps, example data, instructions, and boundaries of what the template cannot do. Write acceptance criteria for a first-time buyer completing their first useful task in under [TIME LIMIT]. Include a usability test with five representative tasks and a checklist for protecting private customer data. Do not claim it replaces professional advice or software unless the evidence supports that claim.
Course outline
Use this when the product teaches a skill over multiple lessons.
Design a practical digital course for [LEARNER] who need to achieve [OUTCOME] but currently face [BARRIERS]. Use [SOURCE MATERIAL OR EXPERTISE] to produce a course promise, learner prerequisites, six modules, a concrete practice assignment per module, and a capstone that demonstrates the outcome. For each module state the misconception to correct and evidence the learner has progressed. Include what the course excludes and where learners should seek a qualified professional for [HIGH-STAKES AREA]. Check that lessons build toward real work rather than passive watching. Do not invent credentials or outcome statistics.
MVP specification
Use this when you have a software idea and need a focused first version.
Write an MVP specification for a digital tool serving [USER] during [WORKFLOW MOMENT]. The core problem is [PROBLEM], and current alternatives are [ALTERNATIVES]. Produce one primary user story, a 6-10 step happy path, acceptance criteria for each essential feature, explicit non-goals, data inputs and outputs, privacy considerations, error states, and success metrics for [BUSINESS GOAL]. Identify the riskiest assumption and a manual or clickable-prototype test before development. Do not add features simply because competitors have them.
Tips
- A useful product starts with a repeated high-friction moment, not a format such as an app or course.
- Write version-one exclusions early; they prevent a template, tool, or curriculum from becoming a bundle of unrelated features.
- Interview users about the last time they encountered the problem and what they did next, since hypothetical preferences overstate demand.
- Test the promised outcome with a manual service or prototype before automating complex workflow steps.
FAQ
Can AI tell me which digital product will sell?
It can structure hypotheses and identify questions to test, but it cannot establish demand without evidence from your intended users and market.
Should I build an app or start with a template?
Start with the least complex format that can produce the desired outcome. A template or concierge service can reveal workflow needs before software locks in assumptions.
What makes a product requirement testable?
It describes an observable result, user, condition, and pass criterion. "Users can create an invoice with a due date in three clicks" is testable; "make invoicing easy" is not.