Business

The Pricing Problem Nobody Solves

The Pricing Problem Nobody Solves — Business article by Steve Ysreal Monas
Most startups get pricing wrong—not because they pick the wrong number, but because they're asking the wrong question. H

This post contains affiliate links. If you purchase through them, I may earn a small commission at no extra cost to you.

You've built something people want. You've validated the market. Now you need to set a price.

So you do what everyone does:

You look at competitors. You calculate costs. You add a margin. Maybe you use psychological pricing ($99 instead of $100). Maybe you offer a "launch discount."

And then you wonder why revenue isn't scaling the way you hoped.

📋 Recommended Tool

Email Marketing Automation Playbook — To turn the email insights from "The Pricing Problem Nobody Solves" into a repeatable system, the Email Marketing Automation Playbook gives you the sequences, segmentation strategies, and automation flows that drive consistent engagement.

Get the Template →

Here's why: you're solving the wrong problem.

The question isn't "What should I charge?"

The question is "What value am I capturing?"

And most startups never ask it.

The Cost-Plus Trap

Let's start with the most common mistake: cost-based pricing.

You calculate what it costs to deliver your product or service. You add a reasonable profit margin. Done.

This feels rational. It feels fair. And it's completely wrong.

Because customers don't care what your costs are.

They care what your product is worth to them.

Think about software. The marginal cost of serving one more customer is effectively zero. Does that mean you should charge zero? Of course not.

Or think about consulting. If you solve a million-dollar problem in one hour, should you charge your hourly rate? Or should you charge based on the value delivered?

Cost-based pricing ignores value. And when you ignore value, you leave money on the table.

The Competitor Trap

Okay, so you look at competitors instead.

If your product is similar, you price it similarly. Maybe slightly lower to compete. Maybe slightly higher to signal quality.

This is marginally better than cost-based pricing, but it's still wrong.

Because you're anchoring to other people's pricing mistakes.

Your competitor probably didn't carefully research willingness to pay. They probably just looked at their costs, or looked at their competitors.

It's pricing by imitation. And it creates a race to the bottom.

Plus, you're assuming you're delivering the same value as your competitor. But if your product is genuinely better—faster, easier, more reliable—why would you charge the same?

Competitor-based pricing treats your product as a commodity. And commodities compete on price.

Is that the game you want to play?

The Real Question

Here's what actually matters:

What problem are you solving, and what is that problem worth to your customer?

Not what does it cost you to solve it. Not what competitors charge. What is the outcome worth?

Let's say you sell project management software to construction companies.

Cost-based pricing: "It costs us $5/month per user to run the servers, so we'll charge $15/month."

Competitor-based pricing: "Our competitors charge $20-30/month, so we'll charge $25/month."

Value-based pricing: "Our software prevents project delays. A single delay costs our customers an average of $50,000. If we help prevent just one delay per year, we're worth at least $10,000 annually. So we'll charge $500/month."

See the difference?

When you anchor to value, your pricing conversation changes entirely.

How to Find Value

Okay, but how do you actually measure value?

Here's the process:

1. Identify the core problem you solve.

Not the features. Not the technology. The outcome.

Are you saving time? Reducing risk? Increasing revenue? Avoiding costs?

2. Quantify the impact.

Talk to customers. Ask:

  • "Before using our product, what was this problem costing you?"
  • "How much time/money are you saving now?"
  • "What would happen if this problem came back?"

Get specific numbers. Even rough estimates are better than nothing.

3. Capture a fraction of the value you create.

If your product saves a customer $100,000 per year, you could theoretically charge up to $99,999 and they'd still come out ahead.

But you don't want to capture all the value—that kills adoption. A good rule of thumb is to capture 10-30% of the value you create.

So in this case, you might charge $10,000-30,000 annually.

4. Test and iterate.

Pricing isn't set in stone. Start with a hypothesis. Talk to customers. See what converts. Adjust.

The goal isn't to find the "perfect" price. It's to find a price that captures meaningful value while still driving adoption.

The Segmentation Opportunity

Here's where it gets interesting:

Different customers get different value from the same product.

A solopreneur and a Fortune 500 company might use identical software. But the value—and the willingness to pay—are wildly different.

This is why good SaaS companies have tiered pricing.

Not because some features cost more to deliver. But because different customer segments have different willingness to pay.

The key is to segment based on value, not arbitrary limits.

Bad segmentation:

  • Basic: 10 users
  • Pro: 50 users
  • Enterprise: Unlimited users

This is just arbitrary gatekeeping. It doesn't map to value.

Good segmentation:

  • Starter: For individuals and small teams ($X value)
  • Growth: For companies scaling operations ($10X value)
  • Enterprise: For organizations with complex compliance needs ($100X value)

Notice how each tier targets a different use case—and therefore a different value proposition.

The individual gets basic productivity tools. The scaling company gets workflow automation. The enterprise gets security and compliance.

Different problems. Different value. Different pricing.

The Psychological Element

Value isn't purely rational. Perception matters.

Two identical products can command vastly different prices based on positioning alone.

Think about bottled water. The product is functionally the same whether it's in a plastic bottle at a gas station ($1) or a glass bottle at a restaurant ($8).

The difference isn't cost. It's context.

For B2B products, this means:

Price signals quality. If you're priced too low, customers assume your product is inferior—even if it's better.

Expensive creates commitment. When customers pay more, they're more likely to actually use the product and see results. (This is why free trials often underperform paid pilots.)

Positioning affects perception. If you frame your product as a "cheap alternative," you're anchoring to the bottom. If you frame it as "premium and worth it," you're anchoring to value.

You can have the exact same product and charge 10X more just by changing how you talk about it.

Common Pricing Mistakes

Let's talk about what not to do:

Mistake 1: Underpricing to win early customers.

"We'll start cheap to get traction, then raise prices later."

This rarely works. Early customers expect the low price to continue. When you raise it, they churn. New customers anchor to the old price and resist paying more.

Better approach: Start at the price you believe reflects value. Offer early adopters other perks (lifetime deals, extra support, input on the roadmap) instead of discounts.

Mistake 2: One-size-fits-all pricing.

If every customer pays the same, you're either overcharging small customers or undercharging large ones.

Segmentation lets you capture more value across the board.

Mistake 3: Charging for features instead of outcomes.

"Pay extra to unlock advanced analytics."

Why do customers want advanced analytics? To make better decisions. To increase ROI.

Charge for the outcome, not the tool.

Mistake 4: Never raising prices.

If your product is getting better, delivering more value, and solving bigger problems, your pricing should reflect that.

Grandfathering old customers is fine. But new customers should pay what the product is worth now, not what it was worth three years ago.

Mistake 5: Discounting too easily.

Every discount trains customers that your "price" isn't real.

If you're constantly offering 20% off, customers learn to wait for the sale. You've just cut your revenue by 20% for no reason.

Discounts should be strategic and rare—not a crutch for weak value communication.

When to Use Usage-Based Pricing

There's a trend toward usage-based pricing (pay per API call, per email sent, per transaction processed).

This can work well when:

  • Usage correlates with value (more API calls = more value)
  • Costs actually scale with usage
  • Customers want predictable, pay-as-you-grow pricing

But it can backfire when:

  • Usage is unpredictable (customers can't budget)
  • High usage doesn't mean high value
  • You're incentivizing customers to use less of your product

For example, if you charge per email sent, customers might send fewer emails—even if sending more would help them. You're literally discouraging them from getting full value.

Think carefully about whether your pricing model aligns incentives or creates friction.

The Anchoring Effect

Whatever price you show first becomes the anchor.

If you show a $10/month plan first, then a $100/month plan, the $100 plan feels expensive.

If you show a $500/month plan first, then a $100/month plan, the $100 plan feels like a bargain.

This is why many SaaS companies lead with their highest-tier plan or show "Enterprise" pricing first—even if most customers don't buy it.

It makes the mid-tier plan look more reasonable.

Same reason restaurants put a $200 steak on the menu. Most people won't order it. But it makes the $50 steak feel like a good deal.

Your pricing page isn't just numbers. It's psychology.

What Good Pricing Looks Like

Here's the test:

If you're not occasionally losing deals because you're "too expensive," you're probably underpriced.

Good pricing should feel slightly uncomfortable. You should have some prospects who love your product but can't justify the cost.

If everyone says yes immediately, you're leaving money on the table.

At the same time, if you're losing most deals on price, you're either overpriced or targeting the wrong customers.

The sweet spot is where some customers see the value and happily pay, while others balk.

That tension means you're close to optimal.

How to Test Pricing

Don't just pick a number and hope. Test.

1. Customer interviews. Ask what they'd be willing to pay. Use the Van Westendorp model: "At what price would this feel like a bargain? Expensive but worth it? Too expensive? So cheap you'd question the quality?"

2. A/B testing. Show different prices to different cohorts. Track conversion, revenue, and LTV.

3. Fake doors. Before building a new tier, put up a pricing page and see how many people click "Buy Now." If nobody clicks, don't build it.

4. Land and expand. Start with conservative pricing for a minimum viable product. As you add value, raise prices for new customers.

The key is to treat pricing as a hypothesis, not a decision.

When to Raise Prices

You should raise prices when:

  • You're consistently hitting capacity and turning away customers
  • You've added significant value (new features, better support, proven ROI)
  • Customer success data shows they're getting more value than you're charging
  • Your costs have increased significantly

How to raise prices without losing customers:

  • Grandfather existing customers. They stay at the old price. New customers pay more.
  • Give advance notice. "In 90 days, pricing will increase. Lock in current rates by renewing now."
  • Tie increases to value. "We've added X, Y, and Z, which deliver $A in additional value. Our pricing now reflects that."
  • Offer an upgrade path. "Your current plan stays the same. But if you want the new features, here's the new tier."

Some customers will churn. That's okay. If you're capturing more value per customer, you can afford to lose the least profitable ones.

What This Actually Looks Like

Let's take a real example: Slack.

Slack could have priced per user, like most enterprise software.

Instead, they priced on active users + message history.

Why? Because that aligns with value.

A company with 1,000 users but only 100 active shouldn't pay for 1,000 seats. That would discourage adoption.

But a company that relies on searchable message history as institutional knowledge? That's worth paying for.

Slack's pricing makes it easy to adopt (low barrier for inactive users) and expensive to leave (unlocking full history requires upgrading).

That's value-based thinking.

The Bottom Line

Stop asking "What should I charge?"

Start asking:

  • What problem am I solving?
  • What is that problem worth to my customer?
  • How can I capture a meaningful fraction of that value?
  • How do I segment customers so I'm not over/undercharging?
  • Am I aligning incentives or creating friction?

Pricing is not a math problem. It's a value problem.

And most startups never solve it.

But the ones that do? They scale faster, retain customers longer, and build more sustainable businesses.

Because they're not selling features. They're selling outcomes.

And outcomes are worth paying for.

More Articles

← Back to All Posts

Get New Posts in Your Inbox

Join readers who get my latest articles, book updates, and exclusive content delivered weekly.

No spam. Unsubscribe anytime.

You May Also Like