Reading Your Report
How to interpret every section of your Pretotyping Signal Report.
[Live]
Overview
Your Pretotyping Signal Report is the output of 500 to 1,000 real market conversations analyzed for demand signals, risk factors, competitive dynamics, and actionable language. This tutorial walks you through each section so you know what to look for, what to act on, and what to set aside.
Reading the report takes about 15 minutes. Making decisions from it should take less. The report is designed to give you a clear verdict backed by evidence — but the evidence itself is where the real value lives.
Section-by-Section Walkthrough
Executive Summary
What it is: A one-paragraph overview of the validation results — the headline finding and overall confidence level.
What to look for: The demand verdict (strong demand, moderate demand, weak demand, no demand) and the overall confidence score. This tells you at a glance whether your idea has legs.
What to act on: If demand is strong, move to Build. If demand is weak or absent, read the rest of the report carefully to understand why before deciding to pivot or stop.
Demand Signals
What it is: Specific evidence from conversations that indicates interest in your product. Each signal is scored by confidence — how reliable the evidence is based on frequency, consistency, and strength of expression.
What to look for: High-confidence signals where multiple people independently expressed the same interest or need. Pay special attention to signals related to willingness to pay — someone saying "I would use that" is weaker than someone saying "I would pay for that."
What to act on: Use the strongest demand signals to shape your positioning. If 40% of conversations mentioned time savings and only 10% mentioned cost savings, your messaging should lead with time.
What to ignore: Low-confidence signals with a single data point. One person expressing mild interest is noise, not signal.
Risk Assessment
What it is: Potential blockers, market risks, and red flags identified from conversation patterns. These are the reasons your product might fail despite demand existing.
What to look for: Recurring objections, trust concerns, switching costs, and regulatory or compliance barriers. If the same objection appears in more than 15% of conversations, it is a real obstacle you need to address.
What to act on: Rank risks by frequency and severity. Some risks are addressable (pricing concerns — adjust your pricing). Some are structural (regulatory barriers — verify before committing). Some are fatal (the problem you solve does not actually bother your market enough for them to pay).
Competitive Landscape
What it is: What your target market currently uses, pays for, and complains about. This section maps the competitive terrain from your customers' perspective, not from your perspective.
What to look for: Which competitors get mentioned most frequently. What your market likes about existing solutions (these are table stakes you need to match). What your market dislikes about existing solutions (these are opportunities to differentiate).
What to act on: Position your product against the specific complaints people raised about competitors. If everyone says their current tool is "too complicated," your landing page should lead with simplicity.
Real User Language
What it is: The exact words, phrases, and descriptions your target market used when discussing the problem you solve. This is not summarized or paraphrased — it is verbatim language.
What to look for: The way people naturally describe the problem, the vocabulary they use, the emotional tone (frustrated, resigned, hopeful, indifferent), and any phrases that appear repeatedly across conversations.
What to act on: Use this language directly in your landing page copy, ad copy, and outreach messaging. Marketing that mirrors how your audience thinks and speaks converts dramatically better than marketing written in your company's internal vocabulary.
What to ignore: Outlier phrases used by one person. Look for patterns, not novelty.
Recommended Next Steps
What it is: Prioritized actions based on the validation results. These are specific, practical recommendations — not generic advice.
What to look for: The top three recommendations and their rationale. HolyShift explains why each action is recommended based on specific findings from the report.
What to act on: Start with the first recommendation. These are ordered by impact — the first action is the one most likely to move your business forward based on the data.
Build vs Don't Build Verdict
What it is: A clear, data-backed recommendation on whether to proceed with building your product.
What to look for: The verdict itself (build, consider with changes, do not build) and the confidence level behind it. A "build" verdict with high confidence is a green light. A "build" verdict with moderate confidence means proceed but address the identified risks.
What to act on: Trust the verdict as one input into your decision, not as an absolute answer. If the data says build, look at the risks before committing. If the data says don't build, look at the demand signals to see if a pivot could change the outcome.
FAQ
What if I disagree with the verdict? The verdict is based on data from hundreds of conversations. If you disagree, re-read the demand signals and risk assessment to understand the basis. You may have context the model does not — but be honest about whether your disagreement is evidence-based or emotional.
Can I run validation again on the same idea? Yes. Create a new project with the same description and a different or refined target audience. Comparing results across audiences can reveal which market segment has the strongest demand.
Should I share the report with my team? Absolutely. The report is designed to be readable without HolyShift expertise. Share it with co-founders, advisors, and investors — it is a more credible basis for decisions than "I talked to some people and they seemed interested."
What's Next
- Building a Landing Page — Turn your validation data into a live page.
- Idea to Validation Workflow — The full decision framework.
- Core Concepts — Understand the methodology behind your report.