Looking back: April 2026
Consulting teaches you pricing in a way that’s painful but permanent. Every hour of yours was sold at a specific rate, and every hour that didn’t get captured on a timesheet was revenue the firm never recognized. The discipline that system imposed taught me more about scope than any other experience in my career.
The Core Lesson
In most businesses, scope is abstract. “What did we commit to?” is answered with some hand-waving about “the deliverables” and “what the customer wanted.” The real answer is usually negotiated in the moment, often at the expense of the delivery team.
In consulting, scope was literal. Every conversation, every document, every meeting had a billable-hour cost attached. If scope was ambiguous, someone was either eating the hours or charging them anyway — and both outcomes had consequences. Eat too many hours, and the engagement’s margin collapsed. Charge hours that weren’t clearly in scope, and the client got angry.
The discipline this forced: learn to scope precisely, or pay a specific, visible cost for not scoping precisely.
Three Patterns That Stuck
1. Every “yes” has a silent “no” attached.
When a client asked for something that was out of scope, the temptation was to say yes. It’s friendlier. It’s easier. It builds the relationship. But every yes to unscoped work was a no to something else — either the margin of the engagement, the delivery team’s ability to finish the in-scope work on time, or the next client’s priority on your team’s time.
Learning to say “yes — and here’s what would need to change to accommodate it” was the discipline that separated consultants who delivered profitable engagements from those who delivered loss-making ones. Saying yes without that clarifier was how engagements quietly went underwater.
2. The hardest scoping conversation is the one that happens after the SOW is signed.
The easy scoping conversations happen at the front end, when everyone is excited, the relationship is fresh, and both sides are being cooperative. The hard ones happen in month three, when the client wants something that’s slightly outside the original scope and assumes it will be handled.
The way I learned to handle this: treat the mid-engagement scope conversation as a craft of its own. Not a confrontation. A graceful, explicit re-negotiation: “Here’s what was in scope. Here’s what you’re asking for. Here are the three ways we could accommodate it — change order, trade-off within current scope, or we phase it into the next engagement.”
Delivered cleanly, that conversation usually strengthens the client relationship rather than weakening it. Clients respect professionals who know their scope. They quietly disrespect ones who don’t.
3. Unscoped work accumulates interest.
A single unscoped task absorbed here and there doesn’t look like much. Five of them compound into a margin problem. Ten of them produce a client who assumes the unscoped behavior is baseline — and then gets upset when the next engagement is scoped properly.
Unscoped work accumulates interest in the same way debt does. The engagement manager who let it accumulate without comment was preserving short-term relationship warmth while creating a medium-term expectation problem. I watched this lesson play out in multiple engagements. The warmth always faded. The expectation always stuck.
How This Applies in Other Industries
Every industry has a scope problem. Software implementation. Construction. Marketing agencies. Product development. Medtech installations. The pattern is always the same: a customer asks for something slightly more than what was committed, the vendor accommodates, and six months later there’s a margin or timeline problem that nobody can quite trace.
The fix is always the same, too: treat scope as explicit. Name it. Document it. When it changes, renegotiate. Don’t let it drift.
The vendors I’ve watched do this well come across as more professional, not less friendly. The ones who let scope drift come across as accommodating in the short term, and chaotic in the medium term.
If you’re in any commercial relationship and you can’t cleanly answer “what’s in scope right now,” you probably have scope drift. The fix is cheap: an explicit conversation. The cost of not having it is a relationship that slowly becomes dysfunctional without anyone being able to explain why.
Billable hours taught me this the expensive way. I’m grateful for the lesson. I’ve since applied it in every industry I’ve worked in, and it’s been one of the most durable, generalizable things I learned in consulting.