The Projects That Almost Broke Me
Nobody talks about this part.
The agency world is full of founder stories about landing the big client, shipping the ambitious project, scaling the team. The success reel plays on a loop and it's immaculate. What you don't hear about is the project that dragged on for eight months when it should have taken three. The client who changed the brief four times and then asked why the delivery was late. The moment you sit in your office at 7pm, after everyone else has gone home, and genuinely wonder why you do this.
I've had those moments. More than a few.
The gap that nobody warns you about
The hardest thing about running a creative and technical agency isn't the work. It's the gap.
The gap between what you see and what the client sees. Between the quality you know you're producing and the quality they're able to perceive. Between the decision you know is right for their business and the decision they feel comfortable making.
This gap is built-in. It's structural. A client comes to you precisely because they can't do what you do — which means they can't always evaluate what you do either. They know what they like and don't like. They can feel when something is wrong. But they can't always articulate why, and they sometimes can't distinguish between "this is genuinely wrong" and "this makes me uncomfortable because it's different from what I expected."
And when the gap shows up — when a client pushes back on something that's objectively the right call — the frustration is specific. It's not anger. It's a kind of weariness. The feeling of having to fight for quality in front of someone who hired you for it.
The unnecessary changes
Every agency founder has a list. The logo that went through seventeen rounds. The website that was approved in wireframe, approved in design, approved in staging, and then completely reconsidered at launch. The campaign that was creatively solid, strategically correct, and then softened into something mediocre because someone's cousin thought it was "too bold."
I've stopped being surprised by this. But I'd be lying if I said it doesn't still sting sometimes.
What I've learned to do — and this took years — is separate my attachment to the work from my commitment to the relationship. The work can be compromised. The relationship shouldn't be. If a client needs three extra rounds of changes to feel confident in a decision, those rounds are part of the service. Not because the client is right, but because confidence in the outcome matters as much as the outcome itself.
That reframe doesn't make it painless. It makes it manageable.
The thing that keeps me here
When the frustration peaks — when I'm in the middle of a project that has stretched past its deadline, with a client who keeps changing their mind, and the team is tired and the brief has drifted — I do something that probably sounds strange.
I make a list.
Not of what's going wrong. Of where I started. Of the specific clients, in the early years of Netspace, who took a chance on a young agency with ambition and a short portfolio. Who wired the fee before the project was done because they trusted us. Who sent referrals. Who gave us the first big project that let us hire the third person, then the fifth, then the tenth.
I didn't become the director of N0 and Netspace because I'm particularly talented. I became it because some people believed in me before I had the track record to justify that belief. That's not something you repay with invoices and deliverables. It's something you carry.
So when I'm exhausted and frustrated and tempted to mentally check out on a difficult client, I remember where I came from. I remember that the switch — leaving finance for tech, ten years ago — was a leap that could have gone badly. It didn't, in large part, because of the clients who stayed.
You don't get to spit in the soup.
What I tell my team
Frustration is information. When a project is dragging, when the same conversation keeps happening, when you feel like you're explaining the same thing for the fourth time — that's a signal. Something in the process isn't working. Either the briefing was unclear, or the expectations weren't aligned, or the relationship needs a different kind of conversation.
The frustration isn't the problem. It's pointing at the problem.
When I feel it, I try to ask: what specifically is making this hard? And then I fix that thing — not by working harder on the deliverable, but by addressing the actual source. A direct conversation about expectations. A reset on the timeline. A clearer decision-making framework with the client.
Most frustrating projects aren't unsolvable. They're just unaddressed.
The ones that almost broke me
I'll be honest: a few projects came close. The kind where you've given everything and it's still not enough, where the client's expectations have disconnected entirely from reality, where you're managing a team that's losing confidence in the outcome.
In those moments, the 2pm rule saved me more than once. Going home, closing the laptop, sitting with my kids — there's something about the forced perspective of being a parent that puts even the worst project into scale. The thing that felt catastrophic at 1pm looks different at 8pm after dinner.
It's still there. It still needs to be solved. But it's not everything anymore.
And usually, by the next morning, I have a clearer idea of what needs to happen next.
That's all you need, really. Not a solution. Just a next step.