The $30K we gave away for free

What's the best part of running an agency?

‍

Different founders will say different things. Revenue milestones. Industry awards. Team wins. But for me, it was always the same moment — that look on a client's face when they see their idea come to life. When something they've been carrying around in their head suddenly exists on a screen, and it's better than they imagined. In those moments, you feel like your work means something beyond money. Like your business has a purpose. And if I'm being fully honest — it feeds your ego too. The recognition of your team's expertise. The confirmation that you're good at this.

‍

I've always been drawn to founders who genuinely burn for their ideas. Maybe that's why I instinctively avoided enterprise clients and gravitated toward startups — people building something they believed in, not just managing a budget. But that exact thing — the excitement, the shared passion — became the most expensive lesson I ever learned.

‍

The project everyone loved

‍

About seven years ago, give or take a week, we started a project that the whole team fell in love with. A startup building a platform for team management — initiatives, motivation, gamification, all the popular engagement methods packaged into one product. It was interesting on multiple levels. We weren't just building their product — we were learning from it. The way they organized their own team, the frameworks they used — our people were absorbing ideas we could apply internally. At one point, we even talked about becoming their client.

‍

The energy was electric. Our designers proposed improvements nobody asked for. Our developers suggested better architectures. The client loved it. We got messages like "Wow, you work at the speed of lightning" and "Thank you so much for your fast and great support." Everyone was high on it. The client, the team, me. Pure dopamine. But here's what none of us were tracking: every one of those brilliant little improvements was eating the budget alive.

‍

It happened in the friendliest way possible. A call where someone says "what if employees could rate each other, not just managers?" A chat message: "could we add different badge types?" What looked like one changed screen in Figma — just a tweak to the employee card view — turned into two weeks of active development because the original architecture, front and back, simply wasn't built for it. Nobody stopped to say: this changes the scope. This affects the timeline. This costs money. The PM didn't flag it. The dev lead mentioned architecture concerns on the big stuff but let the smaller things slide. And the team? They were emotionally invested. They wanted to make this project amazing. Salaries come from somewhere, but when you're in the zone, you don't think about where.

‍

The client approved everything enthusiastically — because why wouldn't they? Nobody was telling them it would cost more.

Then the invoice landed.

‍

What I found when I dug in

‍

The email from the client was short and sharp. "We need to talk. We've gone beyond our estimate and our budget. We're not paying. We agreed on one thing, you gave us an estimate, and now this."

I spent at least a week on the excavation. JIRA tasks, Confluence pages, Harvest time logs, QuickBooks records, email threads, chat histories. I pulled in project managers and senior developers to reconstruct what happened — every conversation, every "quick improvement," every moment where scope shifted without anyone documenting it. What I saw made my stomach turn. Developers had logged time honestly. Managers had assigned tasks based on discussions. But nowhere — nowhere — was there a connection between "we discussed this change" and "here's how it affects the budget and timeline." They discussed, they got excited, they built. Nobody thought about the financial consequences.

‍

Then came the calls with the client. Painful, detailed, line-by-line. We'd show where they'd requested changes. They'd respond — fairly, in many cases — "but why didn't anyone tell us this would affect the cost? We're not programmers. How were we supposed to know? Your people proposed half of these. If you'd told us the impact, we would have said no." In some places, they were right. In others, they'd pushed hard for changes themselves. But the pattern was the same everywhere: no written approval, no impact assessment, no formal sign-off. Just enthusiasm flowing in both directions with nobody watching the meter.

‍

The total damage — what they refused to pay, what we had to finish at our own cost because we'd already promised it, plus all the hours the team and I spent on the archaeology — came to over thirty thousand dollars. On a project that had started with everyone thrilled to be working together. And when we looked at other active projects after that, we found the same pattern everywhere. A "quick fix" here, a "small tweak" there. Five minutes, ten minutes, an hour. Across dozens of projects over a year, it added up to numbers that made my head spin. All lost in the friendly atmosphere of "we care about quality" — while nobody connected that caring to the invoice.

‍

What we built the next morning

‍

The very first rule was an emergency measure. I told the team: starting today, every change request — no matter how small — needs written client approval. Email, chat, carrier pigeon, I don't care. Get it in writing, screenshot it, put it in Confluence. No exceptions. Then we built the real system. For smaller projects, changes under a certain threshold — say, five hundred dollars and a one-time thing — the PM could approve, but had to tell the client: "This will cost X. We'll do it at no charge this time." That last part was important. It showed we cared, that we weren't nickel-and-diming them. But it also drew a line — next time, this is billable. The client saw generosity and professionalism at the same time. For long-term projects, different rules. Bigger changes got a mini scope of work — we had templates ready, the PM could fill one out and send it for signature within a day. And clear escalation points for anything above the PM's authority.

‍

Some clients didn't like the new system. They'd gotten used to getting extras for free and they knew exactly what they were doing. Losing them stung at first — until we calculated the margins on their projects. Most were at zero or negative. We'd been paying for the privilege of working with them. The clients who stayed actually started planning better. They valued the team more, not less, when the team valued its own time.

‍

Something to think about this weekend:

‍

If your team is passionate and your clients are excited — that's genuinely great. But passion without a simple change control process is charity work disguised as a business. Ask yourself: when a client says "can we just tweak this one thing" on a call — what happens next? Does someone assess the impact on scope and budget before the work starts? Or does your team jump in because they care, and the cost shows up weeks later in a spreadsheet nobody's watching?

‍

One rule. Written approval before work begins on anything not in the original scope. That's the floor. Everything else — thresholds, templates, escalation — builds on top of it. But without that one rule, enthusiasm writes checks your margin can't cash.

‍

So here's my question: how much work is your team doing right now that nobody's tracking — not because they're lazy, but because they care too much to stop and ask "who's paying for this?"