The Prelaunch Pricing Playbook for Apps That Aren’t SaaS: 5 Low‑Effort Tests to Find Willingness‑to‑Pay

What it is: Ask early users to put down a refundable deposit (e.g., $5–$25) to reserve access or a limited slot. This is not a full payment — it’s a low-friction commitment that separates curious clickers from real potential buyers. It works for marketplaces (reserve early-access seller slots), mobile utilities (beta access), and consumer apps (limited-launch invites).

How to run it: Build a simple landing page with a short product pitch, a guarantee (refund policy and date), and a payment widget (Stripe Checkout or Gumroad). Promote via waitlist, targeted ads, or partnerships. The goal is to measure conversion from visitor → deposit.

Why it works: Small deposits reduce friction and test real economic intent. Platforms such as Prelaunch have used reservation models to validate pricing and demand; academic and field experiments also show deposits and small payments are stronger signals than surveys alone. Use the deposit as a basis to test different price anchors in parallel (A: $5, B: $15, C: $25).

Expected numbers & timeline: For a baseline conversion (interest to deposit) of 3–10%, plan for 100–400 visitors per variant to detect meaningful differences in conversion (80% power, 5% significance) if you target a minimum detectable effect (MDE) of ~30–50% relative lift. Run for 1–3 weeks or until you hit the sample target. If traffic is tight, accept a larger MDE or extend the window.

What it is: Create a waitlist that unlocks earlier access. Offer users the option to pay small amounts to 'skip' ahead (e.g., $3, $10, $30 tiers). This reveals both willingness to pay and urgency — the people who pay for earlier access are your highest-value early adopters.

How to run it: Use a single landing page with a prominent waitlist status and a clear, limited inventory message (e.g., “Only 1,000 early spots — skip the line”). Test two or three skip prices and monitor paid skips vs. free signups. For marketplaces, sell priority onboarding; for consumer apps, sell early access or premium onboarding.

Why it works: Tiered skip pricing converts scarcity and convenience into measurable revenue signals. It also gives you segmentation: paying early-adopter customers are prime candidates for higher-ticket features or lifetime offers. Common practice among prelaunch tools and startups is to monetize waitlists because it both funds development and validates price bands.

Expected numbers & timeline: Expect lower absolute conversion than deposit presales because prices are higher; plan for 50–300 visitors per tier to detect practical differences. Run 2–4 weeks or until you have at least 30–50 paid conversions across tiers (that gives directional estimates of median paid price and segmentation).

What it is: Offer two purchase framings to early users — a one-time ‘payoff’ fee for lifetime access (or extended access) versus a low recurring subscription. For non‑SaaS apps (marketplaces, utilities with consumable value), users sometimes prefer one-time fees. Run a split test to see which framing generates higher conversion and better revenue per user.

How to run it: On your landing page or in a prelaunch purchase flow, randomly present variant A (lifetime access: $X) and variant B (monthly subscription: $Y/month with annual option). Track signups, choice proportions, and expected short-term revenue. Keep messaging consistent; only change payment framing and price points.

Why it works: Behavioral research shows payment timing and perceived fairness shape willingness to pay. Some customers avoid subscriptions even when they cost more over time, while others prefer subscriptions for lower up-front cost. Comparing both prelaunch gives you an early read on preferred monetization.

Expected numbers & timeline: Because you measure choice share, you need fewer visitors than revenue tests. Aim for 200–500 visitors total to get a stable split; if conversion is low, focus on the decision stage by splitting visitors who clicked 'Buy' (i.e., use a funneled test). Run 2–3 weeks or until you collect 100+ purchase decisions.

What it is: Give users a set of priced options (anchor + suggested price) and a free or pay-what-you-want path. Compare revenue and conversion across layouts: (A) fixed tiers with recommended/default price, (B) pick-your-price with suggested anchor, (C) free with optional tip/donation.

How to run it: Experiment with anchor values and default selections. For example, show Basic ($0), Supporter ($7), and Founding ($25) versus a slider that suggests $10. Track distribution of chosen amounts and conversion. This is useful for apps that plan voluntary payments, donations, or graded access.

Why it works: Research into pay-what-you-want and anchor effects shows suggested prices and the order of options change amounts paid. For prelaunch testing, anchors give you an idea of an expected modal price and whether most customers cluster at low, middle, or high tiers.

Expected numbers & timeline: PWYW and anchor experiments have noisy per-user payments. Aim for 200–600 participants to estimate a sensible central tendency (median/mean) and the share of zero-payers versus paying users. Run 3–6 weeks if you need more precision on the distribution of amounts paid.

What it is: Lock a tiny, high-value feature behind a paid micro-commitment (e.g., $1–$5). For marketplaces this could be a ‘highlighted listing’ credit; for utilities, a single premium export or premium filter. The goal is to discover which features your early adopters will pay for and whether you can later bundle them into a subscription.

How to run it: Offer the micro-feature on the prelaunch page with a clear CTA and limited quantity. Run several micro-price points in parallel or sequence (e.g., $0.99 vs $2.99). Track add-on purchases and whether buyers later convert to larger commitments in follow-ups.

Why it works: Micro-payments reduce friction and provide direct feature-level WTP signals. They also help you prioritize which product capabilities to build first and which to reserve for premium tiers.

Expected numbers & timeline: Micro-feature purchases tend to have higher conversion but lower revenue per purchase; 100–300 exposures per variant can give directional insight. A 2–4 week run is usually sufficient to identify promising paid features; follow with qualitative interviews of buyers to understand motivations.