Submissions are open — put your project in front of the r/startupaccelerator community →
Monetization3 min read

Pricing your first SaaS: the anchor, the ladder, and the free-tier trap

Most first-time founders price from fear. A simple structure — one anchor, three rungs, and a free tier with a job to do — beats agonizing over the number.

The StartupAccelerator team

The short version

  • Price against the alternative the customer would otherwise use, not against your costs — buyers do not pay for your compute bill.
  • Charge on the axis that grows with the value delivered, so your most successful customers are not your cheapest.
  • Structure beats the number: an open-ended anchor tier, a middle plan you actually want to sell, and a free tier with a defined job.
  • If you cannot name the moment a free user decides to pay, the free tier is a cost centre with a signup form.

Pricing feels like a number problem, so founders spend weeks on the number and minutes on the structure. It is the other way round. The structure decides who buys, what they compare you to, and whether your revenue grows when your customers do. The number is just the part you can change on a Tuesday.

Three rungs and an anchor: the top tier exists to make the middle one look obvious, and the middle one is the plan you actually want to sell.

Price against the alternative, not the cost

Nobody pays for your compute bill. They pay to avoid the thing they would otherwise do — a spreadsheet, an agency, four hours a week, an intern. Find that alternative, price visibly under it, and the conversation moves from "is this worth thirty dollars" to "is this cheaper than what I do now". That is a much easier question for a buyer to answer.

Charge for the axis that grows

Per-seat, per-project, per-run, per-workspace — the right axis is whichever one increases as the customer gets more value. Get this wrong and you end up with your most successful customers paying you the least, which is how products end up rewriting their pricing under duress two years later.

  • Pick a metric the customer can predict. Surprise invoices churn people faster than high prices.
  • Never meter the thing you want them to do more of. Charge for outcomes, not for exploration.
  • Leave the top tier open-ended. "Contact us" is not a cop-out at the enterprise end; it is where your margin lives.

The free-tier trap

A free tier is a distribution strategy, not a kindness. If it does not create a path to paying — through a limit users hit while succeeding, or a collaborator they invite — it is just an expensive way to acquire people who will never buy. The test is simple: can you describe, in one sentence, the moment a free user decides to pay? If not, you have a cost centre with a signup form.

The first price you set is a hypothesis, and it is supposed to be wrong. What matters is that the structure around it survives being right.

Accelerator AI

Put this article to work

Ask it a question, or turn it into a to-do list for your own project. Both answer strictly from this article — nothing invented.

Answers are generated from this article only and are a working draft, not advice.

Questions this answers

How should a first-time founder price a SaaS product?

Start from the alternative your customer would otherwise use — a spreadsheet, an agency, hours of manual work — and price visibly under it. That moves the buyer question from "is this worth the money" to "is this cheaper than what I do now", which is far easier to answer. The first price is a hypothesis and is supposed to be wrong; the structure around it is what has to survive being right.

What should you charge per — seats, usage, or projects?

Whichever metric increases as the customer gets more value, and which they can predict in advance. Getting this wrong means your most successful customers pay you the least, and surprise invoices churn people faster than high prices do. Never meter the action you want customers to do more of.

Should a new SaaS have a free tier?

Only if it has a job. A free tier is a distribution strategy, not a kindness: it needs a limit users hit while succeeding, or a collaborator they invite. If you cannot describe in one sentence the moment a free user decides to pay, you are acquiring people who will never buy.

pricingmonetizationsaasrevenue
Found this useful? Send it to a founder who needs it.

Building something?

Put it in front of founders who read this — free listing, community-voted, reviewed before it goes live.

Submit your project →
Monetization3 min read Meter your AI feature: the cost ledger that decides your price Most founders shipping an AI feature have never measured what a single user costs them in a month. Ninety minutes of instrumentation produces that number, and three levers already in the API move it. Read the article → Growth3 min read Build a distribution radar: the agent that finds conversations Answering the right thread is the highest-quality distribution a new product has. Finding it every morning is a chore, and chores get dropped — so hand the finding to an agent and keep the answering. Read the article → Product3 min read Retention is the only moat left When anyone can rebuild your feature set in a weekend, the durable question is not what you built. It is why anyone opens it again on day thirty. Read the article →