Pricing is positioning. This is the definitive pillar — models, scripts, raises, audits — for solo founders setting and revising prices in 2026.
Methodology. This pillar synthesizes pricing literature from April Dunford’s Sales Pitch work, Patrick Campbell’s ProfitWell research on willingness-to-pay (now part of Paddle), and a decade of public pricing posts from Pieter Levels, Jason Cohen of WP Engine, and the Indie Hackers archive. Where we name a SaaS company, the pricing claim is taken from the live pricing page on the date listed in the article meta. Personal recommendations come from running pricing experiments on three solo SaaS products. How we research.
Most solo founders pick a price the same way they pick a domain name: in five minutes, from a gut feeling, the night before launch. Then they treat that number as fixed for two years, watch their MRR limp along, and conclude they have a marketing problem. They do not have a marketing problem. They have a pricing problem — and pricing is one of the highest-leverage variables in a SaaS business. ProfitWell’s long-running benchmarks have shown that companies spend orders of magnitude more time on customer acquisition than on monetization, despite monetization producing larger relative gains for the same effort. For a solo founder, that imbalance is even more extreme.
This pillar is the definitive treatment of pricing for solo SaaS founders. It is long because pricing is genuinely subtle, and the bad advice in this category is loud. By the end you will have a framework for choosing a model, a script for figuring out what your customers will actually pay, a rule for setting the first price, a process for raising it, and a quarterly audit so you do not let your pricing rot. Read it once linearly; come back to specific sections when you are about to make a pricing change.
The single biggest mental shift solo founders need to make about pricing is this: your price is part of your positioning, not the output of a spreadsheet. April Dunford has written for years that positioning is the act of placing your product in a market context where its value is obvious. Price is one of the loudest signals you send about what context you belong in. If you charge $9 per month, you are telling the market you are a side-project tool for individuals. If you charge $290 per month, you are telling the market you are a serious work tool that buyers expense. Those two products may have the same features — but they live in different categories, attract different buyers, support different acquisition channels, and have wildly different unit economics.
This is why “cost-plus pricing” (figure out your costs, add a margin) is almost useless for SaaS. Software has near-zero marginal cost. The interesting question is not “what does it cost me to deliver this?” — the answer is “basically nothing.” The interesting question is: what is this worth to the customer who has the most acute version of the problem you solve? That number is rarely close to your costs. Often it is 10× or 100× what you are tempted to charge.
Patrick Campbell’s ProfitWell research, summarized in talks at SaaStr and on the Protect the Hustle podcast, found that B2B SaaS companies systematically underprice. The median company that does a willingness-to-pay study discovers customers would have paid 25–40% more for the same product. That delta is pure margin — and for a solo founder, it is the difference between a $3K MRR side project and a $10K MRR business. To use price as a positioning lever well, you also need to be clear on the basic vocabulary — what MRR is, what ARR is, what LTV is, and what CAC is — because every pricing decision shows up in those metrics.
If you are still treating pricing as an arithmetic problem, stop. Spend the next three sections rewiring how you think about it. Then we will talk numbers.
There are roughly four pricing models that work for SaaS in 2026. Most products use one of them as their primary structure and borrow elements from one other. Hybrid models exist, but for a solo founder choosing for the first time, picking a single dominant structure is the right move.
You charge per user. The most familiar model in B2B SaaS — Slack, Notion, Linear, Figma, GitHub all use it. Per-seat works when the value of your product scales naturally with the number of people using it inside an account: more seats means more collaboration, more documents, more usage. It is easy to communicate (“$10 per user per month”), easy to forecast, and aligns price with growth of the customer’s team.
The trap: per-seat pricing punishes adoption. Buyers ration access to your tool to keep their bill down, which means fewer users get value, which means churn risk goes up. For a solo founder, per-seat works best when each seat is genuinely a separate worker doing a separate job — design tools, code editors, sales CRMs — not when seats are an artificial proxy for usage.
You charge a flat fee per tier (Starter / Pro / Business / Enterprise) and put different feature sets, limits, or support levels in each tier. Examples: Beehiiv (subscriber tiers + features), Vercel (Hobby / Pro / Enterprise), Lovable (credit-based tiers). This is probably the most common structure for indie SaaS in 2026 because it lets you anchor on a clear “most popular” tier and gives you upsell room.
Three-tier structures consistently outperform two-tier or four-tier structures in conversion testing because of decoy pricing — the middle tier is what you want most people to buy, and the cheap and expensive tiers exist to make it look correct. If you only run two tiers, you lose this anchoring effect; if you run five, decision fatigue rises and conversions fall. Start with three.
You charge based on consumption: API calls, gigabytes processed, emails sent, AI tokens used. Examples: Resend (emails sent), Supabase (compute + bandwidth), Twilio (messages), OpenAI (tokens). Usage-based aligns price tightly with value delivered — customers only pay when they get something out of your product. This makes it the most fair-feeling model and the easiest to start small with.
Usage-based has been the fastest-growing pricing model in SaaS for several years according to OpenView’s annual SaaS Benchmarks report, in part because AI products almost universally adopt it (since their COGS scale with usage). The downside for solo founders: revenue is harder to forecast, and customers can get nasty surprises on their bill. If you go usage-based, build in clear caps, transparent dashboards, and proactive emails when a customer is about to cross a threshold.
You give a meaningful slice of the product away for $0 and charge for power features, limits, or commercial use. Examples: Notion, Loom, Calendly, Figma, PostHog. Freemium is a product-led growth motion: the free product is your top of funnel. Done well, it produces enormous distribution — Notion grew to nine figures of ARR largely on freemium virality. Done badly, it is a charity that drains your margins to support users who will never pay.
The rule for solo founders considering freemium: only adopt it if your free tier is so structurally limited (by collaborators, by export, by branding, by usage caps) that any serious user must upgrade within weeks. If a power user can run their entire business on your free tier indefinitely, you have built a non-profit. Lovable’s credit model is a clean version: you can try it for free, but the moment you actually build something real, you need a paid plan.
| Model | Best for | Watch out for | Examples |
|---|---|---|---|
| Per-seat | Tools where each user does separate work | Adoption rationing | Slack, Linear, Notion |
| Value-tiered | Most indie SaaS | Picking arbitrary feature splits | Beehiiv, Vercel, Lovable |
| Usage-based | Infrastructure, AI, messaging | Bill shock, hard to forecast | Resend, Supabase, OpenAI |
| Freemium | PLG with strong network effects | Free users who never pay | Notion, Loom, Calendly |
Picking a model is downstream of who you are selling to. If you are selling a developer tool, default to value-tiered or usage-based. If you are selling a team collaboration tool, default to per-seat. If your product has clear consumption mechanics and your COGS scale with usage, default to usage-based. Freemium is the one model you should have to justify picking, not the one you default to.
Once you have picked a model, you need a starting number. Most solo founders pick this number badly because they anchor on the price that feels right to them — and founders are systematically more price-sensitive than their customers, because founders are paying for tools out of personal cash flow while their customers are usually expensing.
Pieter Levels has written several times on his blog and on Twitter/X that his rule of thumb is to set the price to double whatever instinct says, then increase from there. This sounds like a joke. It is not. It is a corrective for the systematic underpricing bias above. If your gut says “I think I should charge $19 per month,” start at $39. If your gut says $49, start at $99. The asymmetry of the bet is the point: if you priced too high, a few prospects will tell you so and you can lower; if you priced too low, you will get plenty of customers but never know you left half your revenue on the table.
Before locking a number in, do a comparable analysis. List five to ten products that solve the same job-to-be-done and write down their pricing. Categorize them by tier (cheap individual tools, mid-market team tools, expensive enterprise tools). Decide which category you want to be in — this is the positioning question from earlier — and price within that band, not below it.
For example, if you are building a content calendar tool, your comparable set might include Buffer, Hootsuite, Later, and Typefully. Their entry-level individual plans cluster around $15–$30/month. Their team plans cluster around $50–$120/month. If you price at $9, you are saying “I am cheaper than the cheapest” — which buyers read as “less serious.” If you price at $29, you sit comfortably in the individual band. If you price at $79, you are positioning as a team tool and need feature breadth to back it up.
Before committing to a price, run five willingness-to-pay interviews. This is the single most undervalued action a solo founder can take. The script borrows from van Westendorp’s Price Sensitivity Meter, with simplifications for one-on-one conversations:
The fifth question is the gold question. It surfaces real objections (“I need to see if it integrates with X”) instead of theoretical ones. Run this with five target customers. Set your initial price at or slightly above the median of their “expensive but considering” answers — not the average, because outliers will pull the average down. For a deeper treatment, our customer interview playbook covers the full set of questions to ask before launch, and our 48-hour validation guide integrates pricing into the broader validation process.
One number does not fit all customers. The buyer at week one (an early adopter who is taking a chance on you) is not the buyer at month nine (someone who found you via SEO and expects polish). Solo founders who keep the same price for the same product for two years systematically leave money on the table.
The first 10–30 customers are doing you a favor. They are accepting bugs, missing features, and the risk that you might disappear. In exchange, give them a real, named lifetime discount (“Founding member — 50% off forever”) and a private channel to talk to you. This builds a cohort of evangelists who feel ownership over the product. It also creates a story you can tell publicly: “We have 25 founding members, and the next 10 spots will close on May 31.” Scarcity helps; ownership helps more. These customers are also your best design partners — the ones whose feedback shapes the product.
Once you are out of the founding-member phase — somewhere between customer 30 and 100 — raise to your “fair” price. This is the price you arrived at from your willingness-to-pay interviews and comparable analysis. At this stage you are still rough, but you are no longer charity. Keep the founding members on their lifetime deal; new customers pay full freight.
Past 100 customers, you have data. You know who churns and who sticks. You know which features people use and which they ignore. This is when you should introduce a premium tier that captures the willingness-to-pay of the customers who are getting the most value. This tier might be 2–3× your standard price and bundles things that bigger customers want: priority support, higher limits, integrations, audit logs, SSO. You are not changing the price for existing standard-tier customers; you are giving heavy users a way to pay more for more. Our solo founder pricing playbook walks through the exact tier construction.
Beyond the price itself, several mechanics shape conversion and retention. Each has a defensible use case and several wrong ones.
A free trial works when your product’s value is felt within the trial window and when the customer can fully experience the product without committing. Standard trial lengths are 7, 14, and 30 days. Counterintuitively, shorter trials often convert better than longer ones because they create urgency — ProfitWell data has consistently shown 14-day trials converting at higher rates than 30-day trials in many B2B categories. Default to 14 days. Use 7 if your product is simple enough to evaluate in a week. Use 30 only if there is a clear seasonal or workflow-bound reason (e.g., monthly close cycles for a finance tool).
The case against trials: they suit products where the value is felt in the first session. If your product is value-on-day-one (a one-shot AI tool, a generator, a calculator), a trial just delays revenue. Use a money-back guarantee instead.
A 30-day money-back guarantee is functionally equivalent to a free trial but creates a different psychological frame. The customer pays first, gets the product, and can request a refund. This works for products where the value is immediate and the friction of starting a trial would lose conversions. The refund rate is typically 2–5% for products that are roughly fit-for-purpose — well below the conversion lift you get from removing the trial step.
Offering an annual plan at a 15–20% discount serves two functions. First, it bumps your effective LTV because annual customers churn less (cancellation friction is higher). Second, annual customers pay you 12 months upfront — cash you can use to fund growth. Solo founders should add an annual option as soon as they have monthly pricing established. Most B2B SaaS companies see 20–40% of revenue come from annual plans within a year of offering them.
Lifetime deals (one-time payment for unlimited future use) are popular on AppSumo and similar platforms. They have a place in your toolkit, but mostly only at one moment: as a launch boost when you have no audience and need cash. The math gets ugly fast — if you sell 1,000 LTDs at $59 each, that is $59K of cash but also 1,000 forever-customers consuming support and infrastructure with no recurring revenue. Use LTDs once, take the cash, then pivot the business to recurring. Treat them as a controlled detour, not a strategy.
Most solo founders never raise prices. This is the single most common mistake in indie SaaS pricing. Your costs go up. Your product gets better. Your category matures. The price set on launch day is almost always too low six months later, and dramatically too low two years later.
Before raising for everyone, run a 4–6 week cohort substitution test. For new signups only, put the higher price in front of them. Track signup rate, trial-to-paid conversion, and 30-day retention. Compare to the previous cohort at the old price. If signup rate falls less than the percentage price increase, you have made more revenue per visitor — which is the only metric that matters. If conversion or retention falls off a cliff, pull back.
Concretely: if you raise from $29 to $49 (a 69% increase) and signups fall 30%, you are still ahead. Revenue per visitor went from $29 × 100 = $2,900 to $49 × 70 = $3,430 — an 18% revenue lift. This is the core insight from ProfitWell’s pricing experiments: most companies could raise prices by 25% with conversion impact below 10%.
Existing customers should keep their existing price for the first raise. This is a goodwill move that pays back enormously: it builds trust, reduces churn at the moment of the change, and gives existing users a story to tell their network (“I’m grandfathered — signed up before they raised prices”). Once you are on your second or third raise, you can choose to bring grandfathered customers up to current pricing — but always with notice and always with the option to lock in a year at their old price first.
Email every existing customer 30 days before any pricing change. Explain why (“The product has changed substantially, our costs have grown, we have added X and Y”). Show them what their plan will cost. Offer them a chance to lock in a year at the old price. Be human about it. Do not bury the change in a footer or hope nobody notices — that is how you turn a small percentage of churn into a Twitter incident. For more on the timing question, see when to do a pricing increase.
Pricing is not a one-time decision. It rots. Your customers change, your competitors change, your costs change, your product changes. The solo founders who win at pricing review it on a calendar — once per quarter, ideally on the same day as your monthly metrics review. Here are the five questions to ask:
Document your answers each quarter in a single Notion doc. After four quarters you will have a real pricing data trail — the kind of evidence that makes the next pricing decision dramatically easier.
Pick a model that fits your buyer. Anchor on willingness-to-pay, not on what feels comfortable. Reserve a discount for early adopters; charge fair for the next cohort; introduce a premium tier when you have data. Raise prices on a four-week cadence test, grandfather existing customers, and audit the whole picture every quarter. Most solo SaaS pricing problems are not pricing problems at all — they are inattention problems.
This pillar is the hub. The deeper you want to go on a specific question, the better served you are by one of the linked playbooks below. The fastest route to better pricing is reading the solo founder pricing playbook immediately after this and then implementing the pricing experiments playbook for your first systematic test.
If you are still earlier in the journey — pre-revenue or pre-product — the zero to $1K MRR playbook walks through the first ten paying customers, where pricing decisions have outsized impact. Understanding product-market fit, SaaS positioning, and churn rate will sharpen every pricing call you make.
For the payment infrastructure side — what to actually use to charge customers — our best payment processor guide and Lemon Squeezy vs. Stripe comparison cover the trade-offs. The merchant-of-record explainer matters more than most founders think: it is a pricing decision in disguise (because tax handling determines what your headline price actually nets you). Tool-side, our breakdowns of Lovable pricing and Supabase pricing are useful real-world examples of value-tiered and usage-based models.
Finally, if you want to ground pricing in the broader picture of running a solo SaaS, our SaaS metrics that matter guide covers the four numbers (MRR, churn, NRR, CAC payback) that should inform every pricing review. Pricing is not a one-shot decision. It is a recurring discipline. Treat it that way and it becomes the most leveraged hour you spend each quarter.
The stack, prompts, pricing, and mistakes to avoid — for solo founders building with AI.