Value-Based Pricing for Service Businesses
Stop charging cost-plus. The Israeli SaaS pricing shift applied to your service business.
The hourly rate trap
Most US service founders price their work as 'hours × rate.' If a project takes 40 hours and you charge $200/hour, the price is $8,000. Simple. Defensible. Common.
It's also the wrong question. Because what matters to the customer isn't how many hours you spent. It's the outcome - what changes in their business as a result of working with you.
If a 40-hour project saves the customer $200,000 in operating costs, $8,000 is a giveaway. If a 40-hour project produces something the customer ultimately scraps, $8,000 is a robbery. Hours have no relationship to value. Pricing should reflect value.
How Israeli SaaS got here first
When Israeli founders started building SaaS companies in the early 2010s, they didn't have the option of cost-plus pricing. Their costs were a few servers and three developers. If they'd priced on cost, they'd have charged $50/month - and starved.
So they priced on outcomes. Wix didn't charge for 'website building hours.' It charged for 'a website that works for your business.' Monday didn't charge for 'task management.' It charged for 'a team that ships faster.' The pricing wasn't tied to delivery cost. It was tied to what the customer got.
The same logic works for service businesses. Stop pricing your hours. Start pricing your outcomes.
How to do it
Start with the customer's number. What's the specific business outcome you're delivering? Revenue lift? Cost reduction? Time saved? Risk eliminated? Pick one specific number.
Estimate the value to the customer. If you save them $200,000/year, that's the anchor. If you generate them $500,000 in new revenue, that's the anchor. If you save them 20 hours/week of founder time worth $10,000/month, that's the anchor.
Price as a percentage of value. Industry norms vary, but 10-20% of first-year value is a defensible anchor for service work. If your outcome is worth $200,000 to the customer, $20,000-$40,000 is the conversation.
Stop showing your hours. Hours are an internal management tool, not a customer-facing artifact. The customer doesn't care if it took you 40 hours or 400. They care about the outcome.
The objection you'll hear and how to handle it
Some customers will push back. 'Why is this $30,000 when I could pay a freelancer $50/hour?' This is the objection that breaks most founders' resolve.
The answer isn't to defend hourly. It's to reframe: 'A freelancer at $50/hour will give you 600 hours of effort. We're going to deliver a specific outcome that saves you $200,000 in operating costs over the next year. You're not paying for 600 hours. You're paying for the $200K.'
If the customer doesn't see the value at that frame, they're the wrong customer. Israeli founders learned this the hard way - chasing every customer who pushes back on price kills your margin and your sanity. Walk away from the wrong customers. Focus on the ones who see value.
Key takeaways
- →Hours have no relationship to customer value - stop pricing on them
- →Anchor pricing on the customer outcome: revenue lift, cost reduction, time saved
- →10-20% of first-year value is a defensible anchor for service work
- →Stop showing hours in proposals - they're an internal tool
- →Walk away from customers who insist on hourly - they're the wrong fit