The client was a mid-sized manufacturing firm. The project was straightforward on paper: redesign their production workflow to reduce waste. This was during my special engineering period, before 2013, when I was working with industrial clients at Benninghoven. The timeline and fee seemed reasonable for the scope.
By month three, the project had ballooned. The workflow redesign revealed IT infrastructure problems, which revealed data management problems, which revealed training problems. Each discovery felt like a natural extension of the original scope. Each extension felt too small to renegotiate separately. Each “while you’re at it, could you also…” felt too easy to say no to.
By month six — two months past deadline — we had delivered roughly EUR 120,000 worth of consulting at our standard rates. We’d been paid EUR 40,000. The project had consumed my time, my associate’s time, and our capacity to take on other work. Our cash reserves were decimated. Other clients were wondering why their inquiries weren’t being returned.
I was sitting in a hotel room in Wiener Neustadt when I did the math and realized we were three weeks from not being able to make payroll.
That project taught me more about business than any success ever has. Here are the specific lessons, stripped of the pride that took years to swallow.
The Scope Creep Mechanism
Scope creep doesn’t announce itself. It doesn’t arrive as a single, identifiable moment where the project doubles in size. It arrives as a series of reasonable requests, each one adding 5-10% to the workload, each one too small to trigger a formal renegotiation.
“Could you also look at the data migration?” That’s a week of work, but it’s related to what you’re already doing, and saying no feels petty.
“The team has some questions about the new system — could you run a half-day training?” Half a day. How could you say no?
“We’ve noticed another bottleneck in Department B. Since you understand our operations now, could you take a quick look?” A quick look that turns into three weeks of analysis.
Each request is defensible in isolation. Together, they triple the project. And because you agreed to each one individually, you can’t point to a single moment where the client did anything wrong. The scope creep was collaborative — they asked, and I said yes, again and again, because I was too focused on being helpful and too unfocused on being profitable.
This is the mechanism that kills small consulting firms. Not bad clients. Not bad projects. The inability to say “that’s outside our current scope, and here’s what it would cost to add it.”
The Under-Pricing Error
The original fee of EUR 40,000 was wrong. Not slightly wrong — structurally wrong.
I priced the project based on what I thought the client would pay rather than what the project was worth. This is the most common pricing error among founders and consultants, and it stems from the same insecurity: the fear that if you charge what you’re worth, the client will walk away.
The correct price for the project, based on the complexity, the timeline, and the value we were creating, was approximately EUR 75,000. At that price, the scope extensions would have been absorbed by the margin. At EUR 40,000, there was no margin to absorb anything.
I learned to price differently after this project. The framework I now use — and teach through Subtract to Ship — starts with the value delivered, not the cost of delivery. If a workflow redesign saves a manufacturer EUR 500,000 per year, a fee of EUR 75,000 is 15% of the first year’s value. That’s a bargain, and any client who won’t pay it doesn’t understand the value, which means they’ll be a difficult client regardless of what you charge.
The 70/30 rule is partially about this: when you spend enough time selling, you develop the confidence to price correctly because you know you can find another client if this one walks. When you spend too little time selling, every client feels like the only option, and you discount to keep them.
The Walk-Away Point
The project should have ended at month four. The original scope was delivered. The additional work was new scope that warranted a new engagement, new pricing, and a new timeline.
But I didn’t walk away. I didn’t even pause. I kept working because the momentum of the relationship was carrying me forward, and stopping felt like letting the client down.
This is the trap of the helpful founder. You want to be the person who goes above and beyond. You want the client to say “they went further than we expected.” You want the referral that comes from extraordinary service. And all of these desires are legitimate — in moderation.
Without moderation, helpfulness becomes self-harm. Going above and beyond on scope while staying at the original price isn’t generous. It’s financially reckless. The client isn’t benefiting from your generosity — they’re benefiting from your inability to set boundaries.
The walk-away point should have been defined in the contract. “Upon completion of the defined scope, any additional work will be scoped and priced separately.” One sentence. In the contract. Before the project started. That one sentence would have prevented three months of overwork and a near-bankruptcy.
The Recovery
Surviving the financial crisis required three immediate actions:
Action one: The difficult conversation. I called the client and explained, professionally, that the additional work had exceeded the original scope by approximately 200%, and that we needed to either (a) renegotiate the fee or (b) conclude the engagement at the current deliverable. The conversation was uncomfortable. I’d avoided it for three months, and each month of avoidance had made it harder.
They agreed to an additional EUR 25,000. Less than the work was worth, more than I’d expected. The money arrived two weeks later and kept us solvent.
Action two: Emergency cash management. I cut every non-essential expense immediately. Office lease — moved to a home office. Software subscriptions — cancelled everything we could survive without. Planned hires — frozen. This is the same principle behind the profit first system: when cash is tight, you need complete visibility into what’s going out and absolute control over what can be stopped.
Action three: Revenue diversification. In the two weeks following the crisis, I sent thirty outreach emails to past clients and new prospects. Not panicked emails — professional, value-oriented emails offering specific services at specific prices. Five responded. Two became clients within a month. The revenue gap started closing.
The Frameworks That Emerged
This near-bankruptcy produced three frameworks I’ve used for every engagement since:
The scope boundary document. Before any project begins, a one-page document that defines exactly what’s included and exactly what’s not. Specific deliverables, specific timelines, specific exclusions. “This engagement includes X, Y, and Z. It does not include A, B, or C. Additional scope will be assessed and quoted separately.” The client signs it before work begins.
The monthly scope review. On the first of every month during an active engagement, I compare the actual work done to the original scope. If the actual exceeds the defined by more than 10%, a conversation happens immediately — not at project end. This catches creep while it’s still a 10% problem rather than a 200% problem.
The walk-away price. Every engagement has a number that represents the point at which continuing is more expensive than stopping. If the total value of work delivered exceeds the contract value by more than 30%, the engagement pauses and renegotiation begins. Non-negotiable. The velocity principle applies to financial decisions too: fast recognition of a problem enables fast response to a problem.
What I’d Tell Every Founder
If you’re in a project that’s consuming more resources than it’s producing revenue, do three things today:
Calculate the real cost. Not just the fee versus the hours. Include the opportunity cost of the work you’re not doing. Include the stress cost on your health and relationships. Include the risk to your financial reserves. The real cost of an under-priced project is always higher than the fee gap suggests.
Have the conversation. The one you’ve been avoiding. The client either values your work enough to pay a fair price, or they don’t. If they don’t, that’s information you need now, not in three months.
Set the boundary for next time. Write the scope document. Define the walk-away point. Put it in the contract. The fifteen minutes it takes to write these clauses is worth whatever the next scope-creep project would cost you.
I survived the project that nearly bankrupted me. The frameworks that emerged from it protected me for the next fifteen years. The tuition was expensive. But the education was permanent.
