The Job
That Almost Broke Me

I've told this story to a handful of people over the years, usually late in the evening when the conversation gets honest. It's not the kind of thing you lead with when someone asks how your business is going, because the version most people tell is the cleaned-up version — the one where the struggle was temporary and the outcome was inevitable and the whole thing makes sense in retrospect. This is the other version.

Early in my career I took on a project that went sideways in every direction possible. Wrong materials delivered and not caught until we were already committed to the timeline. Crew turnover in the middle of a build, which if you've been through it you know doesn't just cost you labour hours — it costs you continuity, it costs you momentum, and it costs you the specific institutional knowledge of that site that walked out the door with the guy who quit. A client who changed his mind twice a week, sometimes more, always with complete certainty that the new direction was obviously the right one. And a winter that arrived harder and earlier than any reasonable forecast would have suggested, which in BC can turn a manageable schedule into something that looks like a punishment.

By month four I was lying awake doing math in my head that never added up in my favour.

The Night the Numbers Stopped Working

There's a specific kind of exhaustion that sets in when a project goes wrong and you can't find the bottom of it. It's different from being tired at the end of a hard day. It's the exhaustion of knowing that tomorrow is going to require the same amount of you as today did, and the day after that, and that there's no clear point on the horizon where it gets easier. You stop sleeping properly. You start doing mental accounting at 2am that you already know the answer to but can't stop running anyway.

I remember standing on that site one morning, early enough that nobody else was there yet, looking at what we'd built and what still needed to happen and the gap between the two. And the thought that came, clearly and without any drama, was: I am absolutely not cut out for this. Not in a self-pitying way. More like a practical assessment of a situation that had gotten beyond me.

I almost believed it.

What I didn't have the perspective to understand at the time was that this feeling — this particular combination of exhaustion, doubt, and the quiet suspicion that you've fundamentally miscalculated your own capabilities — is not a signal that you're failing. It's a signal that you're in the part of building a business that nobody photographs for the Instagram version of entrepreneurship. It's the part that's real.

What Fear Actually Sounds Like

The thing that I know now, after enough years and enough hard projects and enough nights doing math that doesn't work out, is that the fear of failing doesn't go away when you get more experienced. It just changes shape.

Early on it sounds like "what if I'm not good enough?" It's the imposter's question — the one that wonders if the confidence you projected to win the bid was borrowed against a skill set that isn't actually there yet. Later, after you've proven to yourself that you can do the work, it sounds different. It sounds like "what if I've gone too far to turn back?" What if the thing I've built is too big to stop and too fragile to keep going? What if the gap between what I'm promising and what I can deliver has quietly grown beyond what I can close?

Same fear. Different costume. And the costume gets more convincing as the stakes get higher, which is why experienced operators who've built real things still have nights where the math doesn't add up and the morning feels a long way away.

Hard situations produce fear. That's not a character assessment. That's just physics.

What Actually Pulled Me Through

It wasn't confidence. I want to be clear about that because the story people tell in hindsight almost always involves some version of unwavering belief in themselves that carried them through, and in my experience that's mostly fiction. Confidence is a byproduct of doing the work, not the thing that makes the work possible.

What pulled me through that project — and what has pulled me through every hard stretch since — was stubbornness and a very short memory. Stubbornness in the sense that stopping felt worse than continuing, not because the path forward was obvious but because the alternative was giving something up that I wasn't willing to give up. And a short memory in the sense of making the next decision, then the next one, and refusing to give the voice in my head a permanent boardroom seat.

That voice is always going to be in the room. It's going to show up every time something goes wrong on a project, every time a crew member quits at the worst possible moment, every time a client makes a decision that adds three weeks to your schedule with no adjustment to the budget. The question isn't how to silence it — you can't. The question is whether you're going to let it run the meeting or whether it's just going to sit in the corner and grumble while you get on with the next decision.

Most of the time, the next decision is enough. You don't need to see the whole path. You just need to make the next call.

The Pattern I've Watched in Other Owners

I've been coaching trades business owners long enough to have heard a lot of these stories. And the pattern is consistent enough that I'd call it universal: almost every person who has built something real in this industry has a project like the one I just described. Usually more than one. The job that almost ended it. The stretch where the math didn't work and the confidence wasn't there and they went forward anyway because the alternative was worse.

What's interesting is that almost none of them talk about those periods as defining moments in the way that the success stories get talked about. The wins get stories. The hard stretches get glossed over or compressed into a single sentence about a "challenging period." But when you sit with someone long enough and the conversation gets honest, the hard stretches are where the real development happened. That's where they figured out what they were actually made of — not in the projects that went smoothly, but in the ones that didn't and required them to keep going without any guarantee that keeping going was the right call.

What You Can Actually Control

The project eventually finished. It came in over budget and behind schedule and I learned things from it that I couldn't have learned any other way. The client, for all his indecision, was satisfied with the result. We did not make money the way the original estimate had projected. We made enough to stay in business and move to the next job, which at month four had genuinely not seemed like a certainty.

Looking back at what I could have done differently, the list is long. Better qualification of the client before we started. Tighter scope language that would have given us more protection against the direction changes. A material procurement protocol that doesn't allow delivery acceptance until someone with authority has verified the order. A contingency budget that reflected the actual risk profile of the project rather than the optimistic one.

None of those things would have made the project easy. They would have made it manageable. And that's the honest goal — not to eliminate the hard stretches, but to build the systems and the judgment that make them survivable without requiring you to white-knuckle it for months on end wondering whether you're going to come out the other side.

The Bottom Line

If you're in a hard stretch right now, the most useful thing I can tell you is that it's not unique to you and it's not evidence that you chose wrong. Every operator who has built something real in this industry has a version of this story. The ones who made it through were not the ones who felt certain. They were the ones who made the next decision when they didn't know if it was right, and the one after that, and kept going until the situation changed.

Build better systems so the hard stretches are less frequent. Build better processes so that when they come, you're not running them on pure willpower. And when the voice in your head starts running the numbers at 2am and they don't add up — take a breath, get up, and go make the next decision.

That's the job. It always has been.

If resilience and the operational side of surviving the hard periods in your business is something you want to work through more deliberately, that's exactly the kind of conversation coaching is built for. Learn more about how the coaching works.

Related: The Job That Cost Me $22,000