God of StartupsGod of Startups

From first idea to product-market fit — your founder workspace, run by 100+ AI agents.

Go-to-MarketBy Tom (Artem) Dalevich· 7 min read· Updated June 9, 2026

SaaS Pricing Strategy for Founders: How to Price Before You Have Data

You don't have usage data yet, but you still have to pick a number. Here's how founders set SaaS pricing on day one without guessing — and the moves that compound over time.

Pricing is the highest-leverage decision in a SaaS business. A 10% lift in price flows directly to gross margin; a 10% lift in conversion does not. Yet most first-time founders pick a number that "feels right" and never revisit it. This guide is the opposite — a deliberate way to set SaaS pricing when you have zero usage data.

Start with the value, not the cost

Cost-plus pricing kills SaaS businesses. Software margins are 80%+ — what matters is what the buyer gains. Frame every pricing conversation around the dollar value the product creates for the customer. If a tool saves a 5-person team 4 hours/week, that's roughly $40K/year in recovered time. Charging $200/month for it is leaving money on the table; $2,000/month is reasonable.

Pick a pricing model first, a number second

The four models that cover 95% of SaaS:

  • Per seat. Predictable, easy to sell, ceiling on revenue per account. Default for collaboration tools.
  • Per usage (API calls, events, GB). Aligns price with value. Works when usage scales with customer success. Risk: hard to forecast.
  • Per outcome (per booking, per ticket resolved). Strongest alignment with value. Hardest to instrument.
  • Flat tier. Simple. Lowest friction to buy. Caps your expansion revenue.

Hybrid models (per seat + usage cap, flat tier + overage) are common — but pick the primary axis first. Most early-stage SaaS should default to per-seat or flat tier; switch to usage-based only when usage genuinely tracks value.

Choose your value metric — this is the real decision

The model is the shape; the value metric is the thing you charge on (seats, API calls, contacts stored, invoices processed, GB, bookings). Picking it badly is the pricing mistake that's hardest to undo, because it's wired into your billing, your contracts, and your customers' budgets. A good value metric does three things at once:

  1. It grows as the customer gets more value. The bill should rise when they're winning, not when they're suffering. Charging an email tool per contact stored tracks value (bigger list = more reach); charging it per bounce would be charging customers for your own failure.
  2. It's easy to predict and budget. A buyer should be able to look at the metric and roughly forecast next quarter's bill. Metrics that swing wildly month to month (raw compute seconds, unpredictable event spikes) trigger bill shock and budget fights — even when the average price is fair.
  3. It's hard to game. If a customer can get the full outcome while keeping the metric artificially low (sharing one login across a team, batching to dodge per-call pricing), your revenue leaks while your value doesn't.

These three pull against each other, so you're choosing the least-bad trade-off, not a perfect metric. Predictability favors seats and flat tiers; value-alignment favors usage and outcomes.

Where seat-based and usage-based diverge — a worked example. Imagine a document-automation tool. Two accounts:

  • Account A: 2 power users who each run 5,000 documents a month — 10,000 documents, heavy value.
  • Account B: 50 occasional users who log in once a week and run 40 documents each — 2,000 documents, light value.

Price per seat and Account B pays 25× more than Account A while getting a fraction of the value — they'll feel ripped off and churn, and Account A is a steal you're under-monetizing. Price per document and the bills finally match the value each account extracts — but Account B can no longer predict its spend, and a single batch job can spike the invoice. The "right" answer is usually a hybrid: a platform fee or seat floor for predictability, plus a usage component on the metric that tracks value (documents), with a published per-unit rate so there's no bill-shock surprise.

How to set the actual number with no data

  1. Find 5 reference prices. Direct competitors, adjacent tools, what the buyer already pays. Write them down.
  2. Anchor at 2× the cheapest, 0.5× the most expensive. That's almost always the sweet spot for a new entrant.
  3. Run the Van Westendorp 4 questions on 10 prospects ("At what price would this be too expensive? Too cheap? Starting to feel expensive? A bargain?"). The intersection gives you a defensible range.
  4. Charge more than feels comfortable. First-time founders under-price by 30–50%. If no one objects, your price is too low.

Three tiers, almost always

The standard structure: a low entry tier to remove friction, a mid tier where 70% of customers land (this is where you make money), and a high "Enterprise — contact us" tier that anchors the mid tier as reasonable. Don't ship a single price — you lose negotiation room and the anchor effect.

Free vs free trial vs freemium

  • Free trial (14 days). Best for products with clear time-to-value under a week.
  • Freemium. Only when the free tier costs you near-zero to serve AND drives organic acquisition (network effects, content, virality). Otherwise it's a tax.
  • No free. Underrated. If your buyer is a business, a 30-minute demo + paid pilot often converts better than a self-serve free trial.

The annual discount nobody talks about

Offer ~17% off for annual billing (two months free). It improves cash, kills monthly churn, and signals confidence. Almost every successful SaaS does this — and most first-time founders forget it.

When to raise prices

  • New customers only, every 6–12 months, ~10–20% at a time.
  • When you've added meaningful new capability.
  • When inbound demand is exceeding capacity — that's the market telling you you're too cheap.

Grandfathering: do it on a clock, not forever

The instinct is to grandfather existing customers indefinitely to avoid awkward conversations. Don't. Grandfather for a defined window — 6 to 12 months is standard — and tell them early ("your current rate holds through [date], then it moves to the new plan"). Early notice turns a price hike from a betrayal into a heads-up, and the window gives loyal customers a real benefit without making it permanent.

Permanent grandfathering looks generous and quietly becomes a tax. Every customer you locked in at the old price is a customer who never participates in any future raise — so your blended price erodes as your best, longest-tenured accounts stay frozen at year-one rates. Two years in, your largest cohort is also your cheapest. A defined window keeps the goodwill without capping your own expansion.

Don't price in a vacuum — tie it to your unit economics

A price isn't right or wrong on its own; it's right or wrong relative to what it costs you to acquire the customer. Two rules of thumb are worth holding in your head as you set the number:

  • CAC payback — how many months of gross-margin revenue it takes to recover what you spent to land a customer. A common target is under ~12 months for SMB/self-serve and under ~18 months for enterprise. Longer than that and you're financing growth out of your own cash for too long.
  • LTV:CAC ≈ 3:1 — the rough floor for a healthy SaaS. Below ~1:1 you lose money on every customer; far above 3:1 often means you're under-pricing or under-investing in growth.

The reason this lives in a pricing guide: a price change moves both numbers at once. Raise price 20% and (assuming roughly stable conversion) payback shortens and LTV rises — the same customer is suddenly far more economic to acquire. Cut price to chase volume and you can quietly push payback past 18 months and LTV:CAC under 3, turning a "growing" business into one that burns cash on every new logo. Run the price you mean to charge through these two checks before you commit to it.

Design for expansion — the price after the first price

The initial price gets the customer in the door; expansion revenue is where most SaaS businesses are actually made. The number that captures this is Net Revenue Retention (NRR) — what a cohort of customers is worth a year later, after upgrades and expansion minus churn and downgrades. NRR above 100% is the goal: it means your existing base grows revenue even if you never sign another customer, which is the closest thing to a flywheel a SaaS has.

Pricing decides whether that's possible. A flat single tier caps every account at one number — NRR can only ever fall. To get NRR above 100%, your value metric and mid-tier have to leave room to grow with the account: seats that get added as the team adopts you, usage that climbs as they succeed, a natural next tier they grow into. Designed well, a customer who starts at $200/mo is at $600/mo two years later without a single renegotiation. That land-and-expand motion frequently matters more than the initial price — a slightly low entry price that expands beats a high one that's stuck.

Common mistakes that cap revenue forever

  • Pricing below the cost of switching from a spreadsheet. If you're charging $9/mo, you're competing with "stay on Excel" — a brutal fight.
  • One number, no tiers.
  • Hiding the price. Public pricing on the website filters out tire-kickers and shortens sales cycles. The only reason to hide it is genuine enterprise complexity.
  • Discounting to close. Every dollar you discount in year one, you eat forever. Trade scope for price instead.

Pricing as part of the plan

Your pricing decision drives your financial model, your sales motion, and your positioning. Build the model around the price you mean to charge — not a "conservative" version of it.

Keep reading

Stop reading. Start building.

Put this into practice with 100+ AI agents and proven frameworks — from idea to product-market fit.