Prototype‑First Pricing: A 6‑Step Workflow to Run Fake‑Door & Deposit Tests From Playable Demos

Prototype‑first pricing puts a low‑friction playable demo in front of users and asks for a real commitment (a click to a fake checkout, an email + deposit, or a microtransaction). This combination converts expressed interest into a monetary signal—stronger than clicks or signups alone—while remaining cheap to run compared to a full build.

Empirical and theoretical work in digital product monetization shows that small, immediate payments and microtransactions are predictive of later spend behavior if the demo captures core value and the payment friction is representative of the final checkout path. Use the web as your distribution channel for installless playables to reduce acquisition friction and to control the payment microflow you’ll show test customers.

Step 1 — Define the value: pick the single mechanic that delivers the product’s core value (the loop or payoff you intend people to pay for). Keep the demo to 1–3 minutes of engaged interaction.

Step 2 — Build an installless playable: export a minimal Web build (HTML5/WebGL or a lightweight JS playable). Host it on a landing page and instrument telemetry for time played, actions completed, and replays. The web platform lets you control the microcheckout UI and collect payment metadata without app‑store constraints.

Step 3 — Add a microcheckout: present one of three payment options after a short session: (A) fake‑door buy button that opens a checkout, (B) refundable $1 deposit to unlock the next level, (C) gated email+payment intent (payment details auth but no capture). Keep copy clear: this is a test of purchasing interest.

Step 4 — Telemetry & prediction: capture first‑session metrics (time played, completion, retries, core actions/min) and microcheckout events (checkout opened, payment method added, deposit authorized). These correlate with Day‑7 conversion in product experiments—build queries to compute the conversion prediction score (see templates).

Copy that converts for prototype pricing follows three principles: reduce cognitive load, set expectations, and minimize perceived risk. Use a clear CTA variant test: “Try playable demo” vs “Play demo — reserve for $1”. On the buy path, show what the deposit unlocks and that the charge is refundable or only an authorization if you’re testing intent rather than revenue capture.

Payment microflow (3 screens): 1) Offer screen (what paying gives you + price), 2) Payment entry (card, Apple/Google Pay, or Payment Request API), 3) Confirmation + thank‑you (or refund promise). For fake‑door tests you can substitute a short checkout stub that records intent without real capture—this is acceptable when you clearly disclose it’s an interest check.

Don’t just count clicks. Compute a composite conversion‑prediction score from short‑session telemetry. Key signals: session duration percentile, completion rate (reached core milestone), replay rate (user returned within 24 hours), and payment funnel engagement (checkout opened, payment entered). Weight these signals and flag users above a threshold as high probability converters.

A simple scoring formula you can run on analytics data: Score = 0.4*(session_duration_percentile) + 0.25*(completion_rate) + 0.2*(replay_within_24h) + 0.15*(checkout_engaged). Calibrate thresholds with any paid conversions you collect. Over time, regress Day‑7 actual conversions on this score to improve weights—this lets you predict revenue from a single prototype run.

Case A — Hypercasual mobile game: 90‑second WebGL demo, fake checkout for $0.99 to remove ads in full game. Distribution: ads + organic landing. Key metric: checkout opened rate and deposit auth. Decision rule: if >2% of engaged users authorize payment, proceed to build a playable first paid tier.

Case B — Productivity micro‑SaaS feature: interactive in‑browser mini workflow that demonstrates the automation. Offer a $1 refundable trial authorization to unlock extended export. Key metric: replay within 48 hours and payment details added. Decision rule: if conversion‑prediction score > 0.6 and at least 25 real deposits, run a pricing A/B for $3 vs $5.

Case C — Niche creative tool (founder market): gated demo that forces a small non‑refundable deposit ($5) for extended export templates. Because the audience is narrower, pair the test with an email sequence driving back to replays. Key metric: true purchases and churn at Day 7. Decision rule: if ROI per acquisition at test scale is positive, build minimal paid onboarding.