Revenue is up. That is the problem.

The Verdict

Your revenue grew. Your margin did not. The problem is not your pricing. It is the person whose name appears on every deliverable before it goes to the client. That person is probably you.

The Scene

Picture this. Professional services firm. Eight people. Three years of 20% growth. The owner had done everything right. Hired carefully. Built a process. Brought in a project manager specifically to take things off his plate. Margin: flat for two years. He had already raised rates. Twice. Nothing moved.

One question cuts through it. Who reviewed the last five deliverables before they went to the client. The answer is almost always the same. "Me." "Every one?" "Every one."

He was not a control freak. His team had simply learned to wait. His review was the gate. His calendar was the bottleneck. The business had grown around him without anyone noticing that he hadn't.

The Mechanism

Here is what this looks like from inside. Revenue grows. The owner's available hours do not. Work piles up behind the one person whose sign-off the whole system requires. The team finishes at full speed. Then they wait. Projects that are 95% complete sit in a queue until a window opens. The window comes late. The client feels it. The delay gets absorbed into delivery time. Margin takes the hit.

Nobody names it because it does not look like a structural problem. It looks like a busy owner. The accountant sees a growing revenue line with a flat margin and suggests raising rates. The coach sees stress and suggests delegation. The project manager builds a better tracker.

This is not a character flaw. It is a system that was never designed to run without you. The fix is to design it so it can. That means two things. First. Define what a finished deliverable looks like in writing, with enough specificity that someone other than you can make the call. Second. Give someone the authority to make it.

That is not a loss of control. It is the difference between standards that live in your head and standards that live in a document anyone can apply.

The Tell

Pull your last ten client deliverables. For each one, write down who touched it before it went out. Count how many have your name. If the answer is more than half, you are the constraint. The question is not whether your standards are too high. The question is whether anyone else knows what they are.

The Signal

This is the most common structural problem I find in professional services firms that have grown past their first three years. It never gets named. Owners feel the pressure. They hire into it. They raise rates around it. The constraint stays.

Reply and tell me what your number is. I read every one. If you know an operator who suspects the problem is structural but cannot name it, forward this. That is the whole pitch.

Most consultants bring frameworks. I bring a diagnosis.