Why IT Services Founders Cannot Raise Their Prices (And What to Do Instead)

Most IT services founders have had this experience. You know your rates are too low. You know your competitors charge more. You know your margins are being squeezed. But when you try to raise prices, the conversation stalls. The client pushes back. You hold the line for a day, then quietly go back to the rate they expected.

The problem is not your clients. The problem is how to raise IT services prices when your proposals are still built around hours.

You cannot raise the price of an hour. The market knows what an hour costs. There are benchmarks, rate cards, and a dozen competitors willing to undercut you. But the market has no benchmark for your result. That is where the real pricing conversation lives.

The Real Issue

Most IT services proposals follow the same structure. Scope of work, number of days, consultant grade, rate per day, total fee. It is logical. It is familiar. It is also a ceiling.

When you price in days and hours, you invite the client to compare you to every other firm pricing in days and hours. The conversation becomes about rate, not value. And when the conversation is about rate, the cheapest credible option wins.

Outcome-based pricing removes you from that comparison entirely. You are no longer selling a month of consulting. You are selling a specific result. The client is not buying your time. They are buying what your time produces.

The shift sounds simple. It is not easy. But it is the only way to consistently raise rates without triggering client resistance.

Why IT Services Founders Are Most at Risk

There is an additional pressure on IT services pricing right now. Clients are forming expectations around what AI will do to delivery time. If your proposal shows 40 consultant days and a client believes AI should cut that to 20, you have a problem. Not because they are right. Because you have no answer to the question when your pricing is built around time.

Founders who have already moved to outcome-based pricing are not exposed to this. The client buys the result. How long it takes is an internal delivery question, not a commercial one.

There is a second risk. Many IT services founders only present a rate card when they have more work than they can handle. The logic is: if I am busy, I can afford to price higher and lose some work. That is backwards. The time to move to outcome-based pricing is before you are under capacity pressure. The conversation is easier to have when both sides are calm.

The Framework

The Value Ladder gives you a practical structure for making this shift. It moves a founder from selling time to selling outcomes across three stages. Each stage requires a different kind of proposal, a different conversation, and a different client relationship. Here is how to apply it this week.

Action Step 1 - Rewrite One Proposal in Outcome Language

Pick one current engagement. Not your largest and not your most sensitive client. Rewrite the proposal so there are no hourly or daily rates visible. The only things the client sees are the result, the milestone, and the price.

The internal maths stays the same. You still know your cost base. You are simply not showing it. What the client sees is: here is the problem we are solving, here is what success looks like, here is the price to get there.

Do this with one proposal this week. You will find the number you arrive at is higher than your standard rate calculation. That gap is your current pricing ceiling.

Action Step 2 - Identify Three Clients Ready for an Outcome Conversation

Not every client is ready for this shift at the same time. Some will have bought hours from you for years and will need a transition. Others are already thinking in outcomes and are frustrated that your proposals are not.

Identify three clients who fall into the second category. They ask questions like: what will we have at the end of this? Can you guarantee the result? What does success look like? Those questions are signals. They are already thinking in outcomes. They are just not being sold that way.

Pick one of those three clients. Have one outcome-priced conversation with them this week. Not a revised proposal. Just a conversation about what result they are actually buying and what that result is worth to their business.

Action Step 3 - Audit Your Last Five Proposals

Pull up the last five proposals you sent. For each one, ask a single question: did it lead with deliverables or outcomes?

Deliverables are things you produce. Documents, workshops, reports, configurations. Outcomes are what those things enable. Reduced risk. Faster decision-making. A system that works without the founder in the room.

Count the ratio. If four out of five proposals led with deliverables, that ratio is your pricing ceiling. It tells you exactly where the margin is being left behind.

This audit takes 20 minutes. What it surfaces is often more clarifying than six months of sales training.

What Changes When You Act on This

A founder I worked with had held his rate at $185 per hour for four years. He quoted on a project at $48,000. We repackaged the same scope as a fixed outcome with a guaranteed milestone. Same work. Same time. Same consultant. The new price was $72,000. The client signed in nine days. He never went back to hourly billing on that account.

The change was not the work. The change was the conversation.

When you move to outcome-based pricing, three things shift. First, client resistance drops because the comparison point disappears. Second, your margins increase because the price reflects the value of the result, not the cost of your time. Third, scope creep reduces because the engagement is defined by an outcome, not by hours that can always be extended.

The founders who are raising rates right now are not doing it by negotiating harder on their existing rate card. They are doing it by changing what they sell.

This is exactly the kind of shift we install inside Everest Basecamp. everest-basecamp.loadinggrowth.com