Idea to Validation
The complete workflow from concept to go/no-go decision.
[Live]
Overview
You have an idea. It might be brilliant. It might be solving a problem nobody has. This workflow takes you from raw concept to a data-backed decision on whether to proceed, pivot, or stop — without building anything first.
The goal is not to validate that your idea is good. The goal is to find out the truth about whether people want it, how badly they want it, and what would make them pay for it.
The Workflow
1. Articulate Your Idea Clearly
Before you validate, you need to know what you are validating. Write down:
- The problem — What specific pain point does your product address? Be concrete. "Helps people be more productive" is not a problem. "Freelance designers spend 3 hours per week manually categorizing business expenses" is a problem.
- The solution — What does your product do about that problem? Describe the core functionality, not the feature list.
- The customer — Who has this problem badly enough to pay for a solution? Be specific about role, industry, and company size.
- The difference — Why would someone choose your solution over what they already use (including doing nothing)?
2. Set Up Validation
Create a project in HolyShift and enter your idea description and target market. See Your First Validation for the step-by-step setup.
3. Analyze Results
When your Pretotyping Signal Report arrives, read it thoroughly. See Reading Your Report for a section-by-section guide.
Focus on three things:
- Demand strength — Is there evidence that people actively want this?
- Willingness to pay — Do conversations suggest people would exchange money for this, or just express mild interest?
- Objection patterns — What are the most common reasons people would not buy?
4. Make a Go/No-Go Decision
Use this framework:
Proceed when: - Strong demand signals from multiple independent conversations - Evidence of willingness to pay (not just "that sounds cool") - The competitive landscape has gaps you can credibly fill - Identified risks are addressable, not structural
Pivot when: - Demand exists but for a different version of your idea - Your target audience is wrong but a different segment shows strong interest - The problem is real but your proposed solution does not resonate - Objections consistently point to a different approach
Stop when: - Weak or no demand across a large sample - The problem you are solving is not painful enough for people to pay - The competitive landscape is saturated and your differentiation is not meaningful - Structural risks (regulatory, technical, market size) make success unlikely regardless of execution
5. Act on the Decision
- If proceeding: Move to Validation to Landing Page to build your page using validation data.
- If pivoting: Create a new project with the refined idea and run validation again. Do not skip this step — a pivot is a new hypothesis that needs its own evidence.
- If stopping: Archive the project. You saved yourself months of building something nobody wants. That is a win.
FAQ
How do I know if I should pivot vs stop? Pivot if the report shows demand for something adjacent to your idea — a different customer segment, a different feature emphasis, or a different positioning. Stop if the report shows fundamental lack of demand for the category, not just your specific angle.
Can I validate multiple ideas in parallel? Yes. Create separate projects and run validations simultaneously. Comparing reports side-by-side is a powerful way to choose between competing ideas.
What if the results are ambiguous? Ambiguous results usually mean moderate demand — people are somewhat interested but not urgently seeking a solution. Consider refining your idea to sharpen the value proposition and validating again, or proceed with the understanding that you will need to work harder on positioning and marketing.
What's Next
- Validation to Landing Page — Build your page from validation data.
- Core Concepts — Understand the pretotyping methodology.
- Prompt Starters for Founders — Quick prompts to get more from validation.