You built something genuinely new. That was the goal. Now it is the problem. When there is no obvious competitor to anchor against, pricing feels like guesswork with real consequences. Price too low and you cap growth or signal low value. Price too high, and you stall adoption before you even learn. Most founders hit this moment right after their first few demos, when prospects stop asking about features and start asking, “So… how much is it?”
To put this guide together, we reviewed founder essays, pricing teardown posts, and podcast interviews from SaaS leaders who launched into empty categories or fundamentally redefined existing ones. We focused on what they actually did in their first 6 to 18 months, then cross-checked those decisions against publicly shared outcomes like revenue growth, expansion rates, and positioning shifts. The goal was not theory, but repeatable patterns that work when there is no pricing playbook to copy.
In this article, we will walk through a practical framework for pricing a SaaS product from scratch, grounded in customer value, early signals, and controlled experimentation.
Why This Is Harder (and More Important) Than Normal Pricing
When competitors exist, pricing is often lazy but functional. You benchmark, adjust slightly, and move on. When no competitor exists, pricing becomes part of product discovery. You are not just charging for software. You are teaching the market how to value a new category.
At pre-seed and seed, pricing mistakes compound quickly. Underpricing attracts the wrong customers and distorts feedback. Overpricing hides demand and slows learning. In the next 60 to 90 days, the real goal is not “perfect pricing.” It is confidence that your price reflects real pain, real budgets, and a believable path to expansion.
Step 1: Start With the Problem, Not the Product
When founders price without competitors, the most common mistake is anchoring on features or cost. Instead, anchor on the problem you eliminate.
Patrick Campbell, who later built ProfitWell into a pricing authority, has explained in multiple early talks that willingness to pay correlates far more with the cost of the problem than the sophistication of the solution. Early SaaS winners priced against what customers were already losing in time, money, or risk.
Translate this into numbers. In early customer conversations, quantify:
- How often the problem occurs per month
- How long it takes to handle today
- Who is involved and what their time costs
- What breaks or is delayed when it goes wrong
If a workflow failure costs a team four hours a week at an effective rate of $75 per hour, that is roughly $1,200 per month in pain. Your price does not need to match that, but it must feel obviously cheap relative to it.
Step 2: Identify the Closest Budget, Even If It Is Not Software
“No competitor” rarely means “no alternative.” It usually means your product replaces a messy workaround.
In Stripe’s early days, there was no direct analog for developer-first payments with clean APIs. But the founders still anchored pricing against existing merchant account fees, engineering time, and operational overhead. They priced as a simpler, more predictable replacement for an ugly stack, not as a magical new thing.
Ask customers what line item your product would come from if they bought it today. Common answers include:
- An existing SaaS tool they hate
- Contractor or internal headcount
- Agency spend
- Manual operational overhead
This budget anchor gives you a pricing ceiling and credibility. If your product replaces a $500 per month tool plus five hours of ops work, pricing at $300 per month feels rational even if nothing “like you” exists.
Step 3: Choose a Value Metric That Scales With Success
When there is no competitor, your value metric matters more than your base price.
Value metrics are the unit you charge on: seats, usage, revenue, workflows, API calls. The best early-stage SaaS companies choose metrics that grow as customers get more value, not ones that punish adoption.
Des Traynor from Intercom has written about how early pricing experiments taught them that charging per seat discouraged usage in a communication product. They shifted toward metrics tied to customer interactions instead, aligning price with value delivered.
For a new category, sanity-check your metric with one question:
If a customer is wildly successful with this product, will they pay you more without resentment?
If the answer is unclear, your metric is probably wrong.
Step 4: Price Higher Than You Are Comfortable With
This part feels counterintuitive, but it shows up repeatedly in founder stories.
When Superhuman tested early pricing, Rahul Vohra shared that they intentionally set prices high and looked for signals of intense value rather than mass adoption. The now-famous “how disappointed would you be if this disappeared” question helped them identify customers who found the product mission-critical. Those users did not flinch at pricing that scared casual users away.
For early-stage founders, this translates into a simple rule:
If no one complains about your price, it is almost certainly too low.
Complaints are data. Silence is not.
Step 5: Use Packaging to Reduce Risk Without Discounting
Instead of lowering price, reduce perceived risk.
Founders often jump straight to discounts when pricing feels shaky. Stronger options include:
- A narrower starter tier with a clear upgrade path
- Usage caps that unlock with growth
- Time-bound pilots that convert to paid
Notion’s early team allowed generous free usage for individuals while pricing teams based on collaboration value. This let users self-qualify without collapsing perceived value.
Your goal is not to make the decision cheap. It is to make it safe.
Step 6: Validate Pricing Through Behavior, Not Opinions
Never ask, “Would you pay $X?” That question produces lies.
Instead, look for behavioral signals:
- Do buyers negotiate terms or ask about annual discounts
- Do they ask what happens if they exceed limits
- Do they forward pricing to a decision-maker
- Do deals stall on value or on budget mechanics
In early HubSpot sales conversations, Dharmesh Shah has described how real pricing clarity emerged only after dozens of awkward budget conversations. The patterns, not the answers, revealed the truth.
Aim for 10 to 15 real pricing conversations before changing anything.
Common Early-Stage Pricing Mistakes to Avoid
Founders without competitors tend to repeat the same errors:
- Cost-plus pricing that ignores customer value
- Copying enterprise pricing too early without enterprise readiness
- Locking pricing before understanding expansion behavior
- Underpricing to “get logos” and then being stuck
Pricing is positioning. Changing it later is possible, but painful.
A Simple Framework You Can Use This Week
Here is a lightweight decision table to pressure-test your price:
| Question | What You Want to See |
|---|---|
| Is the problem painful and frequent? | Weekly or daily impact |
| Is there a clear budget anchor? | Tool, headcount, or ops cost |
| Does the metric scale with success? | Yes, naturally |
| Do some prospects push back? | Yes, respectfully |
| Do strong users expand usage? | Within 30 to 60 days |
If three or more answers are “no,” pricing is not your biggest issue yet. Discovery is.
Do This Week
- Quantify the cost of the problem for five customers in dollars and hours.
- Ask each customer what budget your product would replace.
- Write down your current value metric and one alternative.
- Raise your price for new customers only and watch reactions.
- Remove discounts, add a smaller starter tier instead.
- Track where deals stall for the next 10 sales conversations.
- Look for expansion behavior, not signups.
- Write a one-page pricing rationale so your team stays aligned.
Final Thoughts
Pricing without competitors feels lonely because it is. You are teaching the market how to think about a new category, and that takes conviction plus iteration. The founders who get this right do not guess better. They listen harder, price against real pain, and let behavior correct them quickly.
You do not need the perfect number. You need a defensible one, tested in the wild, with the courage to adjust as you learn. Start there, and keep going.
