Demand FirstTest an idea
Menu
Pre-salesDemand First Research

How to pre-sell SaaS before building it

A transparent pre-sale framework for SaaS: choose a commitment level, state what exists, test pricing, define delivery and refunds, and measure real purchase intent.

Short answer

Pre-sell SaaS by offering a clearly disclosed future product to a specific buyer, at a real price, with an explicit delivery scope and refund policy. Start with the least commitment that can answer your current question, then move from application to reservation, deposit, or pre-order only when you can fulfill the obligation. Never disguise an intent test as a working checkout.

Choose the smallest honest commitment that matters

A pre-sale is not one tactic. It is a ladder of increasingly costly actions. The right rung depends on what you need to learn and what you are operationally and legally ready to promise.

Pre-launch SaaS commitment options
MechanismVisitor commitsUseful forOperational requirement
WaitlistEmailMessage and audience screeningPrivacy notice and realistic follow-up
Detailed applicationTime and business contextBuyer fit and workflow qualificationManual review capacity
ReservationExplicit request for a priced slotPrice and urgency testingClear non-payment disclosure
Refundable depositMoney with stated conditionsStronger commitment evidencePayment, refunds, terms, support
Pre-orderPurchase of a future deliverableCommercial demandDefined scope, delivery date, tax and consumer compliance
Paid design partnerMoney, access, and collaborationHigh-value B2B workflow validationHands-on delivery and agreed success criteria

Make the pre-sale offer concrete enough to evaluate

A visitor cannot reveal willingness to pay for a vague future. The page should make the commercial proposition legible without pretending the product already exists.

  • Buyer: who the offer is for and who it is not for.
  • Painful job: the recurring event, current workaround, and consequence of doing nothing.
  • Outcome: what changes for the buyer in observable terms.
  • Mechanism: enough explanation to make the outcome believable, without inventing shipped features.
  • Price: amount, billing basis, setup cost, and what the first payment covers.
  • Beta state: what exists today, what will be manual, and what is still planned.
  • Commitment: one primary action with an accurate label such as “Apply for the pilot” or “Reserve a beta place.”
  • Delivery and risk: timing, eligibility, cancellation, refund, support, and contact information.

Keep pricing and important product facts in readable HTML, not only in an image, video, or client-only widget. That helps visitors, accessibility tools, search engines, and AI retrieval systems interpret the same offer.

Test a 30-day cash model, not just a monthly price

First-month unit economics

30-day contribution cash = cash collected in 30 days − direct acquisition, fulfillment, payment, and service costs

The purpose is not to maximize upfront cash at any cost. It is to learn whether each new customer creates enough near-term contribution to fund delivery and the next acquisition cycle.

A €49 monthly plan can look attractive while creating a cash deficit if the first customer costs more to acquire and onboard than the first month contributes. A founding pilot, paid setup, annual commitment, or done-for-you onboarding can improve early cash—but only when each element delivers real value and is presented clearly.

  • Separate refundable customer funds from operating cash where the applicable rules require it.
  • Model ad spend, domains, hosting, payment fees, manual service time, and refunds—not only software gross margin.
  • Do not offer an annual commitment before you have a credible delivery plan and cancellation terms.
  • Track cash collected, contribution after variable cost, refund exposure, and time to first customer result.
  • Use a conditional guarantee only when the condition is controllable, measurable, understandable, and legally reviewed.

Instrument the pre-sale funnel before launch

  1. Record qualified exposure

    Separate intended buyers from accidental traffic. Preserve channel, campaign, market, page variant, and displayed price without collecting unnecessary personal data.

  2. Track the price exposure

    Count a price as viewed only after the offer is actually visible. A page load alone does not show that the visitor encountered the commercial trade-off.

  3. Track the action before the reveal

    If an intent test opens a transparent beta disclosure, measure the initial unlock click separately from confirmation after the disclosure. Those actions answer different questions.

  4. Join behavior to the cohort

    Persist the assigned price or proposition variant so repeat visits do not silently switch the offer. Analyze conversion by cohort rather than averaging incompatible experiences.

  5. Connect the deepest event to a real record

    Only count a completed application or early-access request after production-safe persistence succeeds. A client-side click is not a submitted lead.

For the broader experiment structure, read how to validate a SaaS idea. If you are comparing waitlists, interviews, fake-door tests, and pilots, use the validation methods matrix.