Clarity

Clarity is the phase where an idea becomes strategically legible. The goal is not to prove the business yet. The goal is to understand what you think is true, why it might matter, and whether the opportunity is sharp enough to validate seriously.

Overview Dashboard

The Overview tab is the synthesis layer for the whole phase. It pulls the strongest signal from each Clarity tab so you can judge whether the project hangs together.

Why it matters:

• If your strongest problem does not match your best ICP, the market story is still fuzzy.
• If your differentiation claim has weak proof, your positioning is probably still aspirational.
• If the risk watch is full of big unknowns, you are not ready to move fast.

Tips:

• Use Overview to spot thin areas quickly.
• Click through weak or suspiciously confident cards.
• Revisit this tab before moving into Proof.

Competitors

The Competitors tab is where you track direct, indirect, and inspirational alternatives in the market. This is not just a list of rivals. It is your category map.

Key fields:

• Tier: Use Direct for same buyer and same job, Indirect for alternate solutions, and Inspirational for adjacent products worth learning from.
• Advantages / Disadvantages: Write these from the buyer perspective, not your own product preference.
• Review history: Track what changed over time, especially positioning, pricing, packaging, and notable product moves.
• Pricing history: Useful for seeing whether the category is moving upmarket, downmarket, or toward new billing models.
• Win / loss notes: Capture why you expect to win or lose against that competitor in practice.

Theory:

Good competitor research is not about copying. It is about understanding where the market is already crowded, where buyers are frustrated, and where a credible opening exists.

Competitive Analysis

The Analysis tab turns competitor data into structured comparison. This is where your theory of advantage becomes explicit.

Key fields:

• Comparison features: These should be features or capabilities buyers actually use to compare options.
• Feature importance weights: These show how important each item is in the buying decision. Higher weight means it matters more strategically.
• Feature coverage: This is the raw yes or no view of who has what.
• Weighted leaderboard: A directional summary of who looks strongest based on the selected criteria and weights.
• Gap analysis: Highlights meaningful missing capabilities in your current position.
• Where we win: Highlights areas where your story can honestly claim advantage.

Tips:

• Keep the feature list tight.
• Weight buyer importance, not engineering pain.
• Do not overreact to small gaps that buyers do not care about.

Problem Library

The Problems tab is where you capture the pains worth solving. A good problem entry is specific, repeated, and costly enough to matter.

Key fields:

• Problem: Describe the pain in customer language.
• Audience: Who specifically has this problem.
• Current solution: How they try to solve it today.
• Current alternatives: Include spreadsheets, internal hacks, agencies, manual work, or doing nothing.
• Impact: What the problem costs in time, money, quality, speed, or stress.
• Evidence: The direct proof behind the entry.
• Evidence count: Number of supporting signals or observations.
• Frequency: How often the problem happens.
• Severity: How painful the problem is when it occurs.
• Linked ICPs: Which customer profiles this problem most strongly belongs to.

Why it matters:

Products become vague when they are built around broad dissatisfaction instead of sharp recurring pain.

Ideal Customer Profile

The ICP tab helps you define who should care most about the product and who is most likely to buy, adopt, and benefit.

Key fields:

• Segment: The market slice or category the customer belongs to.
• Company size: Useful in B2B when budget, process, and urgency change by company scale.
• Goals: What the ICP is trying to achieve.
• Pain points: Their most important frustrations.
• Pain severity: How strong those frustrations are.
• Buying triggers: Events or moments that make them more likely to search for a solution.
• Objections: Reasons they might resist buying.
• Channels: Where you can reach them.
• Channel effectiveness: Which channels appear most workable.
• Best fit rank: Relative ordering of the ICPs you have defined.

Tips:

• Specificity beats coverage.
• Rank ICPs honestly. Not every plausible user is equally valuable.
• Objections are often just as useful as goals.

Market Sizing

The Market tab is where you turn market ambition into concrete numbers.

Key fields:

• TAM: Total addressable market if everyone who could buy did buy.
• SAM: The narrower serviceable segment you could actually serve.
• SOM: The realistic share you could capture in the near term.
• Sources: Where the numbers come from.
• Notes: Assumptions, caveats, or segmentation details.

Why it matters:

Market sizing is not just about impressing investors. It helps you decide whether you are building a niche business, a large software company, or something in between.

Tips:

• Bottom-up estimates are usually more honest than vague top-down market reports.
• SOM is usually the most actionable number.

Differentiation

The Differentiation tab is where you shape the positioning claim you want to own.

Key fields:

• Statement: The actual positioning claim.
• Target: The audience that should care about the claim.
• Proof: Evidence that supports the statement.
• Claim strength: How sharp and specific the claim is.
• Proof completeness: How well the claim is supported today.
• Competitor contrast: The specific difference versus existing solutions.
• Competitor focus: The competitor or category norm being challenged.

Theory:

Strong positioning is not just being different. It is making a relevant claim that is both memorable and defensible.

Demand Signals

The Demand tab helps you collect evidence that the market is reacting, not just nodding politely.

Key fields:

• Signal: What happened.
• Source: Where the signal came from.
• Source tag: The source type, such as interview, inbound, outbound, community, survey, or demo.
• Strength: A quick descriptive read on the signal.
• Confidence score: How trustworthy the signal is.
• Evidence score: How much weight the signal deserves.
• Observed at: When the signal happened.
• Notes: Context that matters for interpretation.

Why it matters:

Demand tracking keeps you from confusing scattered interest with real buying motion.

Tips:

• Separate trustworthy signals from emotionally satisfying ones.
• Track chronology carefully so trend views mean something.

Pricing

The Pricing tab is where monetization thinking starts before it gets locked into product and GTM choices.

Key fields:

• Hypothesis: Your belief about how pricing should work.
• Price point: The amount you want to test.
• Model: Subscription, usage, one-time, services, or hybrid.
• Rationale: Why the hypothesis might work.
• Experiment: The test you plan to run.
• Success metric: The metric that decides whether the test worked.
• Package fields: The starter, growth, and premium structure you want to compare.
• Willingness evidence: Signals from real conversations or buying behavior.
• Competitor references: Useful pricing anchors in the category.
• Too cheap / target / too expensive: A directional sensitivity range.

Tips:

• Treat pricing as positioning, not just monetization.
• Package around value steps when possible.
• Record real willingness-to-pay evidence whenever you get it.

Risks

The Risks tab is where you make uncertainty explicit and actionable.

Key fields:

• Risk: The specific failure mode.
• Likelihood / impact: Qualitative read on the risk.
• Likelihood score / impact score: Structured scoring used in the matrix.
• Status: Whether the risk is open, in progress, mitigated, or otherwise changed.
• Owner: Who is responsible for moving the risk forward.
• Validation task: The action that could reduce uncertainty.
• Validation task link: Where that action already exists in your workflow.
• Mitigation: The plan if the risk is real.

Why it matters:

Great Clarity work is not just optimistic. It is honest about what could break the thesis.

Tips:

• Phrase risks as concrete statements.
• Keep the risk list connected to actual mitigation and validation work.

Phase Gate Checklist

The Phase Gate Checklist appears on the Clarity overview and evaluates whether the project is ready to advance to Proof. Gates check whether key Clarity activities have been completed - competitors analyzed, problems documented, ICP defined, differentiation articulated, and risks assessed.

Phase gates are advisory, not blocking. They highlight what is strong and what is still weak so you can make an informed decision about advancing. If a gate is not met but you have good reason to proceed, you can override it and the decision is recorded.

Tips:

• Review the checklist before requesting a phase change. It tells you exactly what the system considers ready vs. incomplete.
• Unmet gates are a prioritization guide - they highlight the highest-value Clarity work remaining.
• A project with a few unmet gates and strong rationale for proceeding is better off advancing than waiting for artificial completeness.

Health Scorecard

The Health Scorecard shows a composite health score for the project across five dimensions: Clarity, Proof, Construction, Stability, and Expansion. Since the project is in the Clarity phase, the Clarity dimension is weighted at 50% of the composite score.

The score is calculated from 26 weighted boolean items across all dimensions. Each dimension shows its own score with an expandable checklist of individual items so you can see exactly what is contributing to or dragging down the score.

Tips:

• Focus on Clarity items first - they carry the most weight while the project is in this phase.
• A low score in future phases is expected and not a problem at this stage.
• Use the expandable item checklists to find specific gaps rather than reacting to the composite number alone.