Segmented Fake‑Door Playbooks: 4 Prebuild Tests per ICP and Exact KPI Thresholds

A fake‑door test measures outward demand without a finished product; segmented testing measures demand from specific ICPs so you can see where value is real versus noise. Running the same four variants (freemium, paid pilot, deposit, gated demo) for each ICP gives you multiple commitment levels — click interest, low‑cost try, monetary commitment, and sales‑engaged commitment — which together map how valuable the segment likely is.

Expect raw click‑through rates to vary widely by channel and ICP. Benchmarks for in‑product CTA CTRs often sit between 2–5%, while landing‑page CTAs aimed at cold audiences vary more. The important part is having consistent thresholds across ICPs and variants so you can compare signal quality rather than absolute volume.

Design each variant so the CTA reflects the real buyer action you care about. For freemium use a clear “Start free” CTA that creates an account or waitlist. For paid pilots present a short, time‑boxed pilot with price and deliverables and a CTA like “Apply for paid pilot — $X/month”. For deposits use a pre‑order flow that takes a refundable deposit or first‑month charge. For gated demos require a form request and a calendar booking flow with a firm next step.

Copy prompts should surface the core outcome, commitment, and time horizon. Put the outcome in the headline, the commitment in the CTA, and social proof or anchor pricing where possible. Keep all other elements consistent across ICPs so differences in performance track segment interest rather than page design.

Set thresholds before you run tests. Use these starting thresholds as decision rules and adjust them to your ACV and CAC expectations. These are conservative, practical cutoffs for early signal quality: for landing pages to cold audiences, treat freemium CTR ≥ 3% as promising; freemium activation (post‑click account creation) ≥ 25% as strong. For paid pilots expect paid‑pilot conversion (from visitor to pilot applicant who accepts pricing) ≥ 1% on cold landing pages and pilot‑to‑pay conversion ≥ 25% during the pilot.

For deposits, a refundable deposit conversion ≥ 0.5% on cold traffic is a meaningful revenue signal (higher for low‑traffic founders). For gated demos, a demo‑booked rate ≥ 2% from targeted outreach/ads indicates a healthy sales motion; conversion from demo to paid pilot or paid contract should be tracked separately and is the stronger signal. If multiple ICPs clear thresholds at higher commitment tiers, you have a build signal; if only freemium clears, focus on narrower discovery or pricing experiments.

Don’t make a binary decision based on a single metric. Read the shape of signals across the four variants for each ICP. A useful pattern: high freemium CTR but near‑zero deposit or pilot conversions suggests curiosity but not commercial urgency — skip full development or reframe pricing/outcome. Strong deposit + gated demo booking in the same ICP signals both demand and a salesable buying motion — that’s a build‑now cohort.

Weight high‑commitment signals more. Deposits and paid pilots are closer to real revenue and therefore carry more predictive power. Treat gated demo → paid conversions as behavioral proxies for standard enterprise sales cycles. If only one ICP shows high signals at the deposit or pilot level, consider building a narrow MVP for that ICP rather than a broad product.

Operationally, run all four variants in parallel for each ICP with consistent traffic sources and UTM tagging. Use a lightweight landing page tool (Unbounce/Webflow), an email automation for follow‑up, and a payment processor that can refund deposits. Capture qualification data on paid pilot applicants and demo requests so you can prioritize follow‑ups.

Address ethics and expectations publicly. If you take deposits, disclose refund policy clearly; if you run a fake‑door without an actual product, use waitlists and honest follow‑ups when you can. After the run: (1) prioritize ICPs that cleared high‑commitment thresholds, (2) run short pre‑sell or founder‑led onboarding sprints for those ICPs, and (3) iterate messaging and pricing for segments that showed only low‑commitment interest. AppWispr customers often use this staged approach to reduce wasted build time and focus on revenue‑backed cohorts.