Which of Your Problems Are Pricing Problems?

Four operational symptoms, one discriminating question each, and honest exits, including "your pricing is fine."

The short version: Pricing problems rarely look like pricing. They show up disguised as scope creep, a full calendar, or thinning margins. Pick the symptom you would actually complain about, answer one honest discriminating question, and most paths end with a fix you can make yourself, or with "your pricing is fine, the problem is elsewhere." No branch tells you to just raise your rates.

Pricing problems almost never announce themselves as pricing problems. They show up in costume. Chronic over-delivery reads as a scope problem, so it gets a scope fix. A fully booked calendar reads as a capacity problem, so it gets a hiring conversation. Thinning margin reads as an efficiency problem, so it gets a process review. The costume gets treated, and the problem stays, because the layer being fixed is not the layer the problem lives on.

If you ran the load test we published in June, you have already brushed against this layer once. Yesterday we argued that the five answers the test produces tend to converge on a single constraint. Today is the follow-up question that argument leaves open: is that constraint, or anything else on your list, a pricing problem wearing an operational costume?

Below is a sorter for four symptoms that come up again and again with founders of small services firms. Pick the one you would actually complain about and start there. Each branch turns on one discriminating question, a real test, not a relabeled way of telling you that you are undercharging. Most branches end with something you can fix yourself, or with the finding that your pricing is fine and your problem is something else. Two branches do not end that way, and we will be plain about why. And no branch anywhere in it ends with raise your rates.

Branch one: chronic over-delivery

The symptom: engagements reliably consume more hours than were sold. Evenings absorb the difference, and the overage has stopped feeling like an exception.

The question: does the overage cluster on specific clients or deliverable types, or does it spread evenly across everything you do?

If it clusters, this is scope discipline, the pattern usually filed under scope creep, and you can fix it yourself this month. Pull the two or three engagements where the overage concentrates, write down what "done" actually means for each deliverable, and route anything beyond that line through a named change conversation instead of just absorbing it. The price was never the problem on those engagements. The boundary was.

If it spreads evenly, the reading changes: the price is absorbing work it never named, across the whole book. And here the sorter has to be honest with you. Whether the price is short or your firm's standard of done has drifted upward without anyone deciding it cannot be determined from inside the workflow, because the people executing the price are the ones reporting the symptoms. Any outside vantage can run this test: a peer founder, a trusted client, an advisor, or a structured third-party look.

Branch two: fully booked, margin flat

The symptom: the calendar is full, the team is busy, the work is good, and the bottom line does not reflect any of it.

The question: if volume rose 20 percent next quarter, would profit actually move? Not revenue. Profit. Sit with that one honestly before answering.

If yes, your capacity is real and your pricing is fine. Your problem is throughput: work is queuing somewhere between sold and delivered, and the fix lives in sequencing and handoffs, not in the fee. That is a problem you can locate and work in-house.

If no, then being fully booked is not evidence of health. It is utilization compensating for the price: more hours sold to stand still. But whether the price itself is the root, or the margin is leaking somewhere inside delivery, cannot be determined from inside the workflow, because the people executing the price are the ones reporting the symptoms. Any outside vantage can run this test: a peer founder, a trusted client, an advisor, or a structured third-party look.

Branch three: projects keep slipping

The symptom: dates move. Not catastrophically, just chronically.

The question: do projects slip at the handoffs between people, or at the edges of what was sold?

If they slip at handoffs, your pricing is fine and your problem is operational, and it is fixable in-house. Give each recurring handoff a named owner and an explicit definition of ready, so work stops waiting in the gap between two people who each assume the other has it.

If they slip at the edges, where the client expected something the project plan never contained, then the sold scope and the priced scope are two different documents. That is a pricing problem, and it is one you can fix yourself: before the next signature, make the proposal and the price the same document. Whatever the price does not cover, the proposal does not promise.

Branch four: discount drift

The symptom: the list price has become a starting point. Exceptions keep happening.

The question: who initiates the exception, you or the client?

If you do, before the client has pushed at all, this is a positioning fix you can run yourself. Write down what the price is for in plain language, and stop quoting it before that conversation has happened. A price offered with an apology attached invites the discount it fears.

If the client does, look at which clients. If it is the same client type every time, the price was set for a market you are no longer selling to, and the fix is a deliberate one you own: decide which market you actually sell to now, and price for that market on purpose rather than discounting toward it by exception.

The exits, counted

Eight exits in this tree. Four end with a fix you can run yourself, and the actual move is named in each. Two end with your pricing is fine, and your problem is something else, throughput in one case, handoffs in the other. Two end with a structural fact and stop.

And notice what no branch ends with: raise your rates. That is the whole genre's favorite ending, and it is worth asking why. Raise your rates is the one piece of pricing advice that flatters everyone, applies to everyone, and can never be checked. Advice with those three properties gets repeated whether or not it is true. As a universal answer it is just another costume, and this tree refuses it. The useful output of a sorter is not a slogan. It is knowing which layer your problem lives on, and which of the exits above is honestly yours.

Continue the series

This is part 3 of a 4-part series on The Quarter Inheritance. The full arc:

• Monday: Nothing Resets on July 1
• Tuesday: You Ran the Load Test. Now What?
• Wednesday: Which of Your Problems Are Pricing Problems? (this post)
• Thursday: The Load Leaves Before the People Do (coming Thursday)

Content and Accuracy Disclaimer

This article was drafted with AI assistance and reviewed by the Altvina team. We rigorously fact-check all content to ensure reliability.

Should you notice any inaccuracies or outdated information, please contact us so we can correct it. Your feedback helps us maintain high standards of accuracy and transparency.