How to Prove 'It Will Sell' Without a Product — Diagnosing WTP, Channel Fit, and Business Model Viability

#Why the Pre-Launch Stage Is the Most Vulnerable Section of a Business Plan

The statement reviewers scrutinize most is any claim that demand exists despite the absence of a product. Without post-launch data, founders tend to substitute market-size statistics or survey results to demonstrate demand. While those figures can show that demand exists in the market, they do not support the specific claim that 'customers will pay a specific price for our product through a specific channel.'

For the pre-validation section of a pre-launch business plan to persuade reviewers, three logical threads must interlock into a single argument: Is there genuine willingness to pay for this solution at this price point (WTP)? Is the channel for reaching those customers realistic in terms of cost and scale (channel feasibility)? And does the revenue model built on top of that channel structure actually generate margin (business model viability)? Weaken any one of the three and the other two collapse with it.

#WTP, Channel, and BM — How the Three Axes Connect

The three axes are not independent checkboxes — they form an ordered logical chain. Designing a channel without WTP produces a distribution plan with no defined buyer. Drawing a business model without channel feasibility produces a revenue formula built on customers who are unreachable. The pre-launch sales readiness diagnosis is fundamentally about finding in advance exactly where this chain breaks.

#What the Pre-Launch Diagnostic Agent Reviews

The pre-launch-stage agent reads the entire business plan and first checks whether evidence to answer all three axes exists within the document. Its role is not to render a final verdict on sales viability — it is to identify which evidence is missing and whether the evidence already written genuinely supports the WTP, channel, and BM logic.

• Presence of WTP signals — Does the plan cite concrete evidence such as interview quotes, pre-orders, letters of intent (LOIs), or beta waitlist counts, or does it stop at vague claims like 'demand is expected to exist'?
• Consistency of channel assumptions — Does the intended channel actually overlap with the target customer segment? Are the channel cost and conversion rate assumptions logically consistent with the revenue structure?
• Weak points in BM viability — Can the pricing policy, repeat purchase assumptions, and margin structure absorb channel costs, or is the model an idealized design that ignores channel costs entirely?
• Logic gaps between the three axes — Detection of points where sections were written in isolation and the overall argument fails to connect as a single coherent claim

#How to Apply Diagnostic Results to the Pre-Validation Section of Your Business Plan

The agent's diagnostic results show what evidence exists for each of the three axes and where the weaknesses lie. When incorporating this into your business plan, writing the three axes as a structure where each one supports a single unified claim is more persuasive to reviewers than listing them as separate paragraphs.

1. WTP paragraph: Lead with concrete signals from interviews, beta sign-ups, LOIs, etc., and describe which customer segments responded at which price points. Quantifying it — for example, '14 out of 20 interview participants expressed willingness to pay at that price point' — makes the argument significantly stronger.
2. Channel paragraph: Explain how the customer segment that showed WTP discovers the product, and cite the source of your channel cost and conversion rate assumptions. Reference comparable customer acquisition cost data from similar services or competitor ad cost benchmarks where available.
3. BM paragraph: Show that unit economics hold even after accounting for channel costs. The ideal format is a concrete formula: 'Channel cost $X, conversion rate Y%, average order value $Z → recoverable on first transaction.'
4. Connecting conclusion sentence: After the three paragraphs, add a sentence that ties all three axes together — for example, 'Under a structure where all three conditions are met, achieving N or more sales per month in the early stage is realistically achievable.'

#The Iteration Cycle for Getting the Most Out of the Diagnosis

The pre-launch diagnostic agent delivers the greatest value not as a one-time check but in a repeated write → diagnose → strengthen → re-diagnose cycle. The recommended approach is to use the first diagnosis to pinpoint the weakest of the three axes, then collect additional empirical data or explicitly state the basis for assumptions on that axis before resubmitting.

More important than the number of iterations is being clear about which axis was strengthened in each round. Modifying all three axes simultaneously makes it difficult to identify which change addressed which weakness. Focusing on one axis at a time and re-running the diagnosis keeps the direction of revision clearly defined.