Your first SaaS price does not need to be the right price for the next five years. It needs to be a real number that a qualified buyer can accept or refuse, with terms you can explain and a date when you will review the result. This guide gives you a first-price decision record, plain-language founding-customer terms and a worked offer log you can use without signing up for anything.
Decide what your first price has to accomplish
Early pricing has two jobs. It asks a buyer to make a real commitment, and it teaches you which customers value the product enough to pay. Maximizing early revenue is usually secondary. A free arrangement can be useful for a design partnership or a bounded pilot, but it cannot tell you whether anyone will pay.
Treat the number as a hypothesis with an owner and a review date. Write down the customer it is meant for, the unit you charge for and the evidence behind it. When the price later changes, you will know which assumption changed instead of reacting to the most recent conversation.
This guide starts once you have a usable product and at least one plausible buyer. If you are still checking whether the problem exists, use the discovery and design-partner guides linked below first.
Why common first-price advice conflicts
Founder advice disagrees because it assumes different customers. Read each rule as a claim about a situation, then check whether you are in that situation. None of the sources below gives a benchmark for your product.
| Dimension | What it recommends | When it may apply, and its limit |
|---|---|---|
| SaaStr: small customers | Charge a little less than you want, and slightly less than low-end competitors. | Volume products with small deals. Requires a comparable product; a competitor's price is context, not your value. |
| SaaStr: large customers | Charge more when deals are large; Jason Lemkin cites more than $50k–$100k a year. | Large organizations with significant problems. Most first products sold by one founder are not in that range. |
| SaaStr: early discounts | Avoid steep discounts; price at or slightly below established alternatives, then raise prices later. | Known categories with recognizable alternatives. Less helpful when there is no comparable product. |
| Schematic | Start with a flat monthly fee, roughly half of competitor rates in an existing market or a card-friendly price in a new category, to win 5–10 learning customers. | Learning-focused first cohorts. A flat fee is simple but may not match the unit customers value. |
| Arvid Kahl | Your initial price is never perfect, can change and should be aspirational; early customers often pay with their own time today. | Bootstrapped self-serve products. Time-limited grandfathering for early customers also limits later flexibility. |
Collect the evidence a first price can actually rest on
Before choosing a number, collect four kinds of evidence and label each one. Observed evidence is something you checked yourself. Reported evidence is something a buyer told you. Estimates are your own calculations. Anything else is unknown.
- The current workaround: what the buyer does today, who does it, how often and what it costs in money or time. Ask about a recent instance; record the answer as reported unless you have measured it.
- Visible alternatives: the published prices of tools or services the buyer could use instead, with the page URL and access date. Record "contact sales" as unknown rather than guessing a number.
- Your cost to serve: setup, support time and infrastructure for one account during the first months. Label it as an estimate.
- The buying process: who approves spending, whether a card payment or an invoice is expected, and whether a purchase needs procurement. Leave unconfirmed steps marked unknown.
Copy the first-price decision record
Copy the blank fields into your own document. The filled column continues the fictional HandoffKit example from the pilot guide: a client-handoff product for small agencies. Every organization, price, number and outcome in it is invented to demonstrate the method. It is not a Soloop customer case or a recommended price.
On a small screen, scroll each table sideways to read all columns.
| Dimension | Your record | Fictional HandoffKit record |
|---|---|---|
| Decision | [Which price, for which customers, and what you need to learn] | First recurring price for agencies with 3–10 account managers that hand over client accounts at least monthly. |
| Pricing unit | [What the buyer pays for, and why that unit] | Per agency team, up to five account managers. Seats were rejected because one manager often prepares handoffs for colleagues. |
| Current workaround | [Recent instance, frequency and cost; label reported or observed] | Operations lead reports about 20 handoffs a month and three incomplete handoffs last quarter, each needing about two hours of follow-up. Reported, not measured. |
| Visible alternatives | [Product, published price, URL and access date] | General project-tool template at $10 per user per month ($50 for five users); specialist onboarding tool at $149 per workspace per month. Both fictional. |
| Cost to serve | [Setup, support and infrastructure per account; estimate] | About two founder support hours per account per month during the first quarter, plus hosting. Estimate. |
| Target price | [Hypothesis for later customers and its reason] | $120 per team per month: above the general tool, below the specialist tool. Hypothesis, not yet supported by the reported rework alone. |
| Founding offer | [Price, term and payment options] | $90 per month, 25% below target, for 12 months from first payment; or $1,080 paid annually. |
| Exchange | [What the founding customer contributes] | A 30-minute monthly review. A written account of measured results only if the customer later approves it; no testimonial is promised in advance. |
| After the term | [What happens when the founding rate ends] | Moves to the published price then in effect after 30 days' written notice; the customer may cancel instead. |
| Review | [Number of offers or date that triggers a review] | After five founding offers or on Jan 31, 2027, whichever comes first. |
| Unknowns | [What this price cannot yet show] | Each agency's approval threshold, renewal, and whether the pilot's time difference holds at other agencies. |
Check the price against the evidence before you offer it
Compare the price with the value you can actually support. In the fictional example, the reported rework is three handoffs × two hours = six hours a quarter, or two hours a month. At an assumed fully loaded cost of $50 an hour, that is about $100 a month. The $90 founding rate sits just below that figure; the $120 target sits above it.
The pilot guide's fictional time difference does not close the gap. Four minutes saved on 20 handoffs would be 80 minutes a month, but four independent attempts at one agency cannot establish that saving. The honest conclusion is that the $120 target depends on value the founder has not yet shown, such as fewer missed details or less review time. Keep it labeled as a hypothesis and ask about that value in the next conversations.
Also check the floor. Two support hours per account are manageable for a handful of founding customers. They would not be at a much lower price with many more accounts. A price that only works while you personally support each customer needs a review date.
Make the offer and log each response
State the price in the conversation, explain what is included and what the founding term means, then stop talking and record the answer. Keep acceptance, invoice and confirmed payment as separate entries. A verbal yes is not revenue.
In the fictional example, the founder makes the same founding offer to five qualified agencies, including Northstar Studio after its pilot.
| Dimension | Response and stated reason | Recorded status |
|---|---|---|
| O1 Northstar | Owner chooses the annual option to fix the budget for a year. | Accepted; $1,080 invoice sent. Payment not yet confirmed. |
| O2 Agency B | Accepts monthly billing; wants to try it on the next two handoffs. | First $90 payment confirmed. |
| O3 Agency C | Declines: about two handoffs a month, and its checklist works. | Declined. Workflow is too infrequent; segment boundary, not a price objection. |
| O4 Agency D | Asks for $60. When asked why, says only two of six managers would use it. | No decision. Founder keeps the offer; possible pricing-unit question logged. |
| O5 Agency E | Interested; tools are approved during a January budget review. | Undecided until the stated review. No follow-up discount offered. |
Decide what to change for the next customers
Review when the trigger in your record is reached, not after each objection. Change one thing at a time so the next set of offers can teach you something. Keep the founding terms you promised for the customers who accepted them.
In the fictional review, nobody rejects the product solely on price. Agency C shows a qualification boundary, so the next offers go only to agencies with at least ten handoffs a month. Agency D raises a question about the unit, so the founder asks about it in the next discovery calls before changing it. With one confirmed payment, there is not yet evidence to raise the target price or abandon it.
- Keep the price when qualified buyers accept and pay, and objections concern timing or approval rather than value.
- Change the unit when several buyers describe value in a different way than you charge for it.
- Change the segment when refusals come from customers whose workflow is too small or too different.
- Raise the price for the next cohort when qualified buyers accept quickly and your cost to serve is above plan. Tell existing founding customers exactly what does and does not change for them.
- Lower or restructure the price only after you can name the evidence; a single request for a discount is not that evidence.
Write the founding-customer terms in plain language
Put the founding offer in writing before the customer pays. Plain language prevents a temporary rate from turning into a permanent discount nobody remembers agreeing to. Use your normal agreement or terms of service for legal and data-handling commitments; this list is not a contract template or legal advice.
- The price, currency, billing period and payment method.
- What is included: the workflow, support level and any limits on accounts or usage.
- How long the founding rate lasts, and from which date.
- What happens at the end of the term, how much notice the customer receives, and how to cancel.
- What the customer agrees to contribute, such as a regular review. Ask separately for any public reference later; do not make it a condition of the price.
- What is not promised, such as a roadmap feature, an integration or a measured result.
Bring one pricing research question to Soloop
Use the record yourself first, then pick a question that public sources can answer. For example: What do the alternatives this kind of buyer could use charge, which unit do they charge for, and which prices are not published? Research can fill the visible-alternatives row; only your buyers can tell you what they will pay.
A brief to copy: My product is [URL or demo] for [role and workflow]. I am setting a first price for [customer segment]. Research the published pricing of [named alternatives or category] from their own pricing pages. For each, record the price, billing unit, plan limits, the URL and access date, and mark prices that require contacting sales as unknown. Separate published facts from your inferences, and end with the questions I should ask buyers before making an offer.
Soloop's manual describes market and competitor research using public sources, with results and any collected source links in Tasks. Open the result and check the pricing pages behind any figure you rely on, because published prices change. You choose the price, make the offer and confirm payment; this guide does not describe a Soloop feature that sets prices or collects your customers' payments.
The Explore Soloop link opens the public entry and does not transfer this record or your customer notes. A completed decision record is already a useful outcome even if you never open a Soloop workspace.
Sources and limits
Sources checked October 9, 2026. The decision record, prices, offer log, arithmetic and review outcome are original Soloop editorial examples. They have not been tested with customers. Recheck published prices before relying on them, and adapt the record to your own buyers rather than reusing the example's numbers.
Jason Lemkin advises charging less than you want for small customers and more for large deals, which he places above roughly $50k–$100k a year. Practitioner opinion, not a measured benchmark.
SaaStr: Overcharge or undercharge your first customers?Lemkin recommends pricing near established alternatives instead of steep discounts, and raising prices for later customers.
SaaStr: Discounts for first customersRyan Echternacht (Aug 22, 2025) suggests a simple first price aimed at 5–10 learning customers and different pricing questions depending on how well you know the category.
Schematic: Setting your first priceArvid Kahl (Jan 3, 2020) argues that early pricing is never perfect, can be changed and should be aspirational, and notes that early customers may pay with their own time rather than an existing budget.
The Bootstrapped Founder: Your initial pricing will never be rightSoloop documents public-source research with task results. Choosing a price, making offers and confirming payment remain the founder's work.
Soloop product manual