An opinionated framework for setting, defending, and changing prices when you don’t have a sales team, a CFO, or a market research budget.
How this guide works. This is a methodology page. We don’t list every pricing tactic in existence. We argue for a specific approach based on patterns we’ve seen across hundreds of indie SaaS launches. How we research.
The most expensive mistake a solo founder makes in their first year is not a bad architectural choice or a missed launch. It’s pricing the product at $9/month because that’s what they saw on a competitor’s page in 2018. Three years later, that founder is still trying to claw back the margin they gave away on day one, while their competitor — with a worse product — charges $79/month and runs profitably.
This playbook is built on the assumption that you are technical enough to ship a product, that you have at least one paying customer or a credible path to one, and that you intend to run this thing as a real business. If those things are true, the question is not “what should I charge?” The question is “which assumptions about pricing am I quietly importing from places they don’t belong?”
You don’t. You compete on specificity.
When a buyer is comparing two SaaS products, the one that costs $20 less per month does not automatically win. The one that more obviously solves the buyer’s exact problem wins. Price only becomes the deciding factor when the buyer cannot tell the products apart on the actual job they need done.
If you find yourself thinking “my competitor charges $29, so I should charge $19 to win,” you’ve already lost. The undercut signals that you don’t believe your product is worth what theirs is — and buyers can read that signal as accurately as anyone else. They will assume your product is the cheaper, lower-quality option, and they will be right, because that’s how you positioned it.
The right move at indie scale is to narrow your audience until your product is the obvious choice for the people you’re selling to. A project management tool for solo SaaS founders is not the same product as a project management tool for marketing agencies, even if the underlying database schema is identical. Specificity creates pricing power. Generality forces you to compete on price.
Concrete example: ConvertKit (now Kit) entered a market where MailChimp charged $10/month and Constant Contact charged $20/month. ConvertKit launched at $29/month for the smallest tier. They did not compete on price. They competed on the specificity of being “email for creators,” and they grew to $30M ARR in roughly five years. The lesson is in their pricing page, not their feature list.
Write down, in one sentence, the specific person your product is for. Not “small businesses.” Not “creators.” Something like “course creators who use Stripe and want to sell digital downloads without setting up a Shopify store.” If you cannot price your product in a way that this exact person would consider reasonable, your audience is too broad, not your price too high.
This is true at scale. It is not true at indie scale.
When you have ten thousand customers, the market sets your price because you are now subject to competitive dynamics, churn pressure, and acquisition cost ceilings. When you have ten customers, you set the conversation. The market hasn’t formed an opinion about you yet. There is no “market price” for your specific product because your specific product is, by definition, new.
This matters because solo founders look at the established players in their space and treat their prices as anchors. You should not. Established players have completely different cost structures (real salespeople, customer success teams, marketing budgets) and completely different value propositions (multi-year track records, integrations, trust). Their pricing reflects their reality, not yours.
At indie scale, your job is not to fit into an existing pricing landscape. It is to construct one for the small subset of buyers you’re targeting. Tools like modern payment processors make it trivial to charge any amount you want with monthly, annual, or usage-based billing. The technical constraint that used to force founders into round numbers and standard tier structures no longer exists.
Stripe’s own analysis of pricing experiments — published periodically on the Stripe blog — consistently shows that conversion is more sensitive to perceived value than absolute price within a wide range. The buyer’s mental question is not “is this cheap?” It is “is this worth it for me right now?”
This is the most consistently wrong belief in solo SaaS pricing. Round numbers like $30, $50, and $100 feel professional to founders. They do not feel professional to buyers.
The behavioral economics work on this is well-established. Prices ending in 9 (or 7) consistently outperform round-number prices in checkout testing. The effect is strongest at the lower end of the pricing spectrum, where the difference between $29 and $30 reframes the price from “thirty dollars” to “twenty-something dollars” in the buyer’s head. This is called the “left-digit effect” and it has been replicated across dozens of studies, most notably summarized in research from the University of Chicago Booth School and MIT.
For SaaS specifically, the patterns are slightly different but the principle holds:
The exception: if you are pricing toward enterprise (annual contracts of $5K+), use round numbers. The buyer is putting your tool through procurement. Procurement processes prefer round numbers because they round up to budget allocations easily.
Once you’ve discarded the three bad assumptions, the question becomes: what pricing structure should you actually use? Here are the five patterns we see working consistently for solo SaaS founders in 2026.
You charge a fixed amount per user added to the account. Workhorse pattern for collaboration tools, project management, and anything with a team angle. Easy for buyers to understand, scales naturally with the customer’s growth, and creates a defensible expansion path: customers spend more as they hire.
The trap: per-seat pricing penalizes adoption. If your tool is sticky and useful, the buyer doesn’t want to add seats because each seat costs them money. Linear and Notion solve this by making the per-seat price low enough that admins don’t fight it ($8–$15/seat). If you charge $50/seat, expect customers to share logins.
Use this pattern when your product genuinely scales in value as more people use it — communication tools, shared knowledge bases, anything inherently collaborative.
You offer 2–3 tiers, each unlocking more features or higher usage limits. This is the dominant SaaS pattern, and it works because it lets buyers self-select into the tier that matches their willingness to pay.
The math: if you offer one price, you capture revenue from buyers willing to pay that exact amount and lose buyers who would have paid more or who can’t justify quite that much. Tiers expand the band. Three tiers (let’s call them $29, $79, $199) capture roughly twice the revenue of a single $79 price point in our observation, because the cheaper tier converts price-sensitive buyers and the expensive tier extracts more from buyers willing to pay for advanced features.
Bad tiering looks like “basic / pro / enterprise” with vague differences. Good tiering ties tier upgrades to the actual moment a buyer’s needs change. For example: hobbyist tier (1 project), startup tier (10 projects, custom domain), business tier (unlimited projects, team seats). The buyer knows exactly when they’ll upgrade.
You charge based on how much the customer uses the product. Common for AI tools (per-token), email tools (per-send), and infrastructure (per-API-call).
This pattern works when your costs scale with usage and when buyers can predict their usage. It fails when costs are fixed but you charge by usage anyway — light users feel they’re subsidizing heavy users, and heavy users feel they’re penalized for engagement.
The hybrid that works best: a low base subscription plus usage overages. Customers get predictability for normal usage and you get upside when they grow. Both Stripe and Lemon Squeezy support this billing structure natively, so the technical implementation is no longer a barrier.
You sell a one-time payment for “lifetime” access to the current feature set, then offer paid upgrades or add-ons over time. Popular on AppSumo and similar marketplaces.
Most solo founders should avoid this pattern. It front-loads revenue at the cost of permanent customer-support obligations and makes it impossible to fund ongoing development from recurring revenue. The exception: if you’re using lifetime deals as a launch tactic to seed initial users and gather feedback, with a hard cap on total deals sold, it can work as a one-time event. Treat it as a marketing campaign, not a business model.
You offer a free tier that’s genuinely useful, and a paid tier that unlocks features the most engaged users will hit naturally. Notion, Linear, and PostHog all use variants of this.
The hard part is making the free tier useful enough to drive adoption without making it useful enough to suppress conversion. The free tier should solve the buyer’s problem incompletely — enough to demonstrate value, not enough to satisfy them once they’re actively using it.
If you’re using PostHog as your analytics tool, instrument the moment when free users hit the limit that pushes them to upgrade. That conversion event is the most important number in a freemium business.
Once you’ve decided your current price is wrong — almost certainly too low — the question is how to change it without alienating existing customers.
The protocol that works:
Step 1: Grandfather existing customers. Anyone who signed up before the price change keeps their original price for the lifetime of their subscription, as long as they remain continuously subscribed. This is non-negotiable. Customers who feel punished for being early supporters will churn and tell other people you can’t be trusted.
Step 2: Apply the new price only to new signups. The pricing page changes. Existing customers see no change to their billing.
Step 3: Announce the change publicly. Write a short email or blog post explaining the change. Mention that existing customers are grandfathered. Counterintuitively, this often drives upgrades from existing free users who realize they’re about to lose access to the lower price.
Step 4: Measure for four weeks. Compare conversion rate, average revenue per signup, and free-trial-to-paid rate against the four-week period before the change. A 20–40% drop in conversion at a doubled price is a winning trade. A 50%+ drop suggests the new price is genuinely wrong, not just unfamiliar.
Step 5: Do not revert in week one. The first week of any pricing change is noisy. Buyer behavior takes time to settle. Founders who panic in week one and roll back changes are the same founders who never raise prices and stay perpetually underpriced.
If you’re testing a price increase and conversion drops within an acceptable range (let’s say 30%) at twice the price, your revenue per visitor went up 40%. That’s the math you’re after. Don’t let the conversion-rate drop scare you into reverting a profitable change.
Solo founders are constantly asked for discounts. By students, by nonprofits, by “influencers” offering exposure, by buyers in countries with weaker currencies, by their own friends. The default answer should be no, with two exceptions.
First exception: legitimate annual prepayment discounts. Charging 10x the monthly price for a year (instead of 12x) is reasonable. It improves your cash flow and reduces your churn risk. Anything more aggressive than that signals desperation.
Second exception: targeted regional pricing for buyers in markets with significantly different purchasing power. This is operationally complex but increasingly easy to implement with modern billing platforms. It’s most appropriate when you’re selling to individual creators or small businesses in markets where your standard USD pricing represents 10x the local equivalent.
One-off discounts to specific buyers who ask are almost always a mistake. They train your sales process to expect haggling, they leak through screenshots and word of mouth, and they signal that your prices aren’t real. If your price isn’t real, why should the buyer take it seriously?
The signs that your prices are too low, in approximate order of how often we see them:
For deeper pattern-matching on which kinds of products tend to support which prices, the micro-SaaS examples we’ve catalogued include real prices from real solo founders. Looking at what’s working at indie scale is more useful than reading aggregate SaaS pricing reports written for VC-backed companies.
Run through this list quarterly. Each “no” is a place to investigate.
Stop importing pricing assumptions from B2C consumer apps. Replace “compete on price” with “compete on specificity.” Replace “the market sets my price” with “at indie scale, I set the conversation.” Replace “round numbers feel professional” with “left-digit effect is real and ending in 9 wins below $200.”
Then pick the pricing pattern that matches the structure of your business: per-seat for collaboration, value-tiered for general SaaS, usage-metered for infrastructure-shaped products, freemium for products with a clear engagement-driven upgrade trigger. Avoid lifetime deals as a business model.
When you change prices, grandfather existing customers, change only new signup prices, announce publicly, and measure for four weeks. Don’t panic in week one.
The single most reliable pattern across hundreds of solo SaaS launches we’ve seen: founders who raised prices once in their first year did better than founders who didn’t. The act of raising prices, regardless of what you raise to, forces you to confront whether your product is worth what you’re asking. That confrontation is the actual playbook.
The stack, prompts, pricing, and mistakes to avoid — for solo founders building with AI.