I often get asked what exact, low-cost experiments subscription SaaS founders should run to validate product‑market fit before they reach 1,000 users. Having coached founders and launched features at early-stage products, I believe you don’t need fancy analytics or huge ad budgets to feel confident that your product solves a real problem people will pay for. You need three focused, cheap experiments that test demand, onboarding retention, and pricing—each designed to surface real willingness to pay and real user behavior.
Why these three experiments?
To me, product‑market fit for a subscription SaaS boils down to three things happening in sequence: people want the outcome, they can get that outcome using your product (or flow), and they’re willing to pay for it repeatedly. The experiments below map to those three checkpoints:
Demand validation with pre‑sales or lead-to-paid conversionOnboarding & initial retention validation (does the product deliver the promised value?)Pricing & value-capture validation (can you extract recurring revenue and expand?)Each experiment is cheap, requires minimal development, and gives high signal if run correctly.
Experiment 1 — Pre‑sales landing + paid waitlist (smoke test)
This is my go-to first move. Before you build the product, build a landing page that describes a clear outcome and offers a paid “early access” or “founder” plan. The goal is to measure real willingness to pay—nothing beats a credit card in validating demand.
How I run it:
Create a single landing page using Carrd, Webflow, or a simple HTML page. Describe the outcome in plain words: what job you solve, who benefits, and a short social proof/faq section.Run two purchase actions: “Buy founder access — £29/month (limited)” and “Join free waitlist.” Use Stripe or Paddle for checkout. If someone pays, mark it as high-signal demand.Drive traffic with two inexpensive channels: targeted LinkedIn outreach to 50–100 decision makers, and a small targeted Facebook/Instagram ad campaign (£100–£300) to test volume. Organic communities (Reddit, Indie Hackers, relevant Slack/Discord groups) are excellent low-cost sources.Metrics I watch:
Conversion rate on paid checkout (sessions → purchases). Even a 1–2% paid conversion from targeted traffic is strong signal.Cost per paid sign-up. If your acquisition cost is higher than expected LTV, you have a unit economics problem.Qualitative: who paid and why? Send a short follow-up survey or 15-minute interview request.Why it’s cheap and powerful: building a convincing landing page and a checkout flow can be done in a weekend. Paying customers are the gold standard of validation—no guesswork.
Experiment 2 — Concierge MVP / Wizard‑of‑Oz onboarding for first cohort
Once you have people willing to pay, you need to prove the product actually delivers value and retains. I frequently recommend running a concierge or Wizard‑of‑Oz experience for your first 10–50 users. Instead of shipping a complete product, you deliver the outcome manually or with minimal tooling while observing the exact steps users take.
How I run it:
Invite early buyers to a “limited pilot” with a special price and explicit expectations. Promise a specific outcome in X days (e.g., reduction in churn, faster campaign launch, automated report delivered weekly).Deliver the service manually. Examples: if your SaaS automates competitor monitoring, you can manually compile reports and send them. If it optimizes ad spend, run the optimization manually and send results.Use a lightweight toolset: Zapier for automations, Google Sheets, Notion, Calendly for scheduling, Loom for walkthroughs, and Stripe for billing. Track tasks in Trello or Notion.Metrics I watch:
Week-1 activation rate (did users reach the core Aha moment?).Retention at day 7 and day 30 on the pilot plan.Net promoter sentiment and direct quotes about what worked or didn’t.Upgrade/renewal intent when the pilot ends.Why it’s cheap and powerful: operating manually teaches you the true product workflow, reveals hidden edge cases, and lets you tweak the onboarding before engineering spends cycles building features nobody needs. You also build a cohort of product champions and early testimonials.
Experiment 3 — Pricing & packaging micro‑tests
After you’ve validated demand and that your flow produces value, the remaining critical question is whether customers will pay a recurring price and whether you can grow revenue over time (expansion). I run micro pricing experiments to test price sensitivity, value metrics, and packaging.
How I run it:
Set up A/B tests on pricing pages: one page shows price A (lower) and package X, the other shows price B (higher) and package Y. You can use simple tools like Google Optimize, Convert.com, or even two separate landing pages and split traffic via UTM links.Test value metrics rather than arbitrary tiers. For example, charge by number of seats, data rows, API calls, or outcomes. See which metric aligns with customers’ willingness to pay and which predicts expansion potential.Introduce add-ons or usage overage to simulate expansion revenue (e.g., custom reports, priority support). Offer an upgrade prompt after the Wizard‑of‑Oz pilot to see who chooses to scale up.Metrics I watch:
Price elasticity: signup conversion by price variant.Average revenue per user (ARPU) for each cohort.Expansion rate within the first 3 months (do pilot users add seats or buy add-ons?).Churn rate tied to each price tier and value metric.Why it’s cheap and powerful: pricing tests can be conducted before major engineering investment. Small changes to display, framing, and the chosen unit of value reveal whether your revenue model is sustainable.
Quick playbook: sequence and cost estimate
Run these experiments in sequence: demand → delivery → pricing. Below is a compact table I often share with founders to help prioritize and estimate time & cost.
| Experiment | Primary signal | Estimated cost | Time to run |
| Pre‑sales landing + paid waitlist | Paid signups | £50–£500 (landing + small ads) | 1–2 weeks |
| Concierge / Wizard‑of‑Oz pilot | Activation & retention | £0–£300 (tools & time) | 2–6 weeks |
| Pricing & packaging micro‑tests | Price elasticity & ARPU | £0–£200 (testing tools) | 2–4 weeks |
Practical tips I always use
Be explicit about expectations with early users: label the experience as a pilot, promise hands-on support, and set a clear duration. Transparency builds trust and usability feedback.Interview every paying user within the first two weeks. I schedule 15–30 minute calls and use a short script: what outcome did you expect, what did you get, what would make you churn, what would make you expand?Instrument minimal analytics. You don’t need full event tracking to start—track activation steps in a spreadsheet, record calls, and use simple retention cohorts in Stripe.Iterate quickly. If demand is weak, iterate on the landing copy and target audience before building. If activation fails, optimize onboarding flows in the Wizard‑of‑Oz pilot.Keep founders in the loop. I recommend the founder(s) run the first outreach and onboarding—there’s no substitute for hearing customers’ language directly.These three experiments together give you a compact, actionable path to validate product‑market fit before hitting 1,000 users. They minimize wasted build time and maximize learning—helping you avoid building features nobody wants and ensuring you start with customers who both value and pay for what you do.
