How One Agency Lost $100K on a Single Project (And What It Took to Fix the Problem)
Brian ran a 40-person custom development agency. Within his first two weeks on the job, he discovered a six-figure write-off. Not because the work was bad. Because nobody could see it coming.
The project that broke everything
Good client. Solid work. Then the client acquired two companies mid-project, and the scope tripled overnight.
What happened next is predictable if you’ve spent any time in agency operations. The project team said yes. Made the client happy. Absorbed the new work without a change order or a revised timeline. Nobody told anyone what the expanded scope would actually cost.
When the invoice landed, the client lost it. Never agreed to pay three times the original price. And honestly? Fair. Nobody had communicated the change. No documentation existed. Not a single person had stopped to say: this is a different project now, and here is what it costs.
Brian met them in the middle. He wrote off over a hundred thousand dollars. In his second week.
“My life is a warning to others,” he told us during a recent Parallax webinar. He wasn’t kidding.
Why scope creep costs agencies more than they think
Scope creep is the most common source of margin erosion in project-based businesses. PMI data shows it affects more than half of all projects. But the real damage goes beyond the one project that goes sideways.
When Brian’s two most experienced (and most expensive) developers got locked into the expanded project, every other client in the pipeline shifted. Nobody told those clients that their timelines had just moved two months. Nobody wanted to deliver that news, so nobody did. Brian found out when phones started ringing.
One project absorbed the senior team. Other projects slipped. Clients got angry about things that had nothing to do with their own work. The ripple effect turned a single scope failure into a company-wide fire drill.
Sound familiar? Most agencies have a version of this story. The write-off is the visible cost. Everything that shifts around it is the real damage: delayed projects, angry clients who had nothing to do with the original problem, trust you can’t invoice your way back from.
What zero visibility actually looks like inside an agency
Brian’s systems were a mess. And not in a “we should tidy this up someday” kind of way. In a “the accounting system was still DOS-based” kind of way.
His CRM was designed for manufacturing. It tracked inventory quantities, not project timelines or resource plans. Asana handled what was in flight, but backlogs lived in spreadsheets. And the timecard system? Looked like Windows 98.
Zero integration between any of them. So when Brian needed to understand what was happening across the business, he pulled data from four different places, stitched it together in Excel, and hoped the formulas didn’t break.
They always broke.
“I used to joke that I was going to submit some of my formulas to Microsoft’s formula contest,” Brian said. “I was proud of that complexity. And that was the problem.”
Eventually the spreadsheet got so complex that Brian was the only person who could update it. Project managers would email him changes. He’d manually input them. By Thursday or Friday, he had a view of the business. By Monday, stale.
Why agencies get stuck in reactive mode
Brian spent most of his time doing forensic analysis. Not leading. Not growing the business. Just forensics. A client would call, angry about a missed deadline or a surprise invoice. Brian would scramble to figure out what happened, who was on the project, what was promised, what was actually delivered.
“I wasn’t working on the business,” he said. “I was working inside it. And that’s not what the owners hired me to do.”
If you’ve managed agency operations, you recognize this. Your tools show you what already happened. Financials show up after the project closes. By the time you see a margin problem, the project is done and the only lever left is writing off the difference.
Brian couldn’t tell you his ten most profitable clients. He couldn’t tell you his ten least profitable clients. He couldn’t answer the question “who should we fire as a client?” because the data didn’t exist in any usable form.
“Hey, who are the clients we’re losing money on?” he said. “It was an anecdotal story from people. No data to back it up.”
The real cost of “we’ll figure it out”
Brian’s sales team had quotas. They were incentivized to close deals. So when a client asked “can you get this done by end of year?” the answer was always yes.
“I must have heard a million times: ‘ah, we’ll figure it out,’” Brian said. “That was literally our answer to any problem. With no strategy.”
Timelines were optimistic. Resource plans were nonexistent. The project team would get a signed proposal and ask “who agreed to this?” The answer, every time: “we did, so we could get the business.”
The project always took exactly as long as operations said it would. (It always does.) But the client expected what sales promised. That gap was baked in from day one.
This is the part that doesn’t show up in any dashboard. Optimism replaces planning. Nobody has the data to push back. Sales can’t see capacity, operations can’t see pipeline, and the guesses compound until something breaks.
Why name-brand software doesn’t solve agency problems
Brian’s agency was a technology company. They built custom software for clients. They knew exactly what tools existed and how to integrate them. The irony wasn’t lost on anyone.
“We sat around and laughed,” Brian said. “‘If we took two developers and let them go dark for a month, they could build exactly what we needed.’ But we couldn’t get out of our own way.”
When Brian went to ownership to make the case for new systems, the conversation always drifted toward the big names. NetSuite. Salesforce. The tools every CEO in a Vistage group recommends because they work well for manufacturing, insurance, and paper companies.
None of those were designed for agencies. Built to ship products, not to track time against services or forecast capacity across a portfolio of concurrent engagements. Project-level margin isn’t even a concept in most of them.
“There’s software for shrimp farmers,” Brian pointed out. “So when there’s software for shrimp farmers, there is absolutely something built for professional services organizations where time is the biggest asset.”
Discovery is the problem. Purpose-built tools don’t have the marketing budgets of a Salesforce. They don’t show up first in search results or get recommended in CEO peer groups where nobody else runs an agency.
How to make the business case for better agency operations
Brian had to justify the investment to owners who didn’t experience the chaos directly. Chaos is hard to put a dollar value on. But write-offs are not.
“You remember that hundred thousand I just wrote off?” Brian told them. “Do you know how much the business has written off over the last year? If it’s only going to cost $150,000 to put in an entirely new system, and we wrote off a quarter million dollars last quarter, the math is a no-brainer.”
That ended the conversation. Owners will spend $150K to fix a $250K problem every time. But Brian had to frame it in dollars, not frustration. “I can’t do my job with these tools” wasn’t enough. “Here is exactly how much money we are losing” was.
For agency leaders building a similar case: start with the write-offs. Then add the cost of reactive hiring, the margin erosion you couldn’t prevent, and the revenue from clients who left because communication broke down. The number is always larger than anyone expected.
The cultural shift that made the difference
New tools alone didn’t fix it. The team wanted better systems. They were tired of the chaos. But the real change was process.
Proposals went through operations review before reaching the client. Someone in ops confirmed that what sales was promising could actually be delivered with available resources. Change orders became standard. Any scope change got documented, priced, and agreed to before work started.
Weekly project reviews tracked margin and timeline in real time. Not after the fact. Not at month-end. During the project, while there was still time to adjust.
“Even our clients would say, ‘I’m expecting things to go a little wrong during this project. Just tell me,’” Brian said. “‘Don’t hide it from me. Don’t lie.’”
Communication was the biggest win. Clients didn’t need perfect projects. They needed to know what was happening. Once teams had the data to communicate early, the firefighting stopped. Brian went from years of never talking to a happy client to actually running the business he was hired to run.
What Parallax does differently
Brian joined Parallax because it solved the exact problem he lived through. It sits between your CRM, your project tools, your timesheets, and your financials, connecting data that already exists across those systems into a single forward-looking view.
You pick the CRM that works for your sales team. You pick the project management tool your PMs love. You pick the timecard system that’s least painful for everyone. Parallax brings those signals together so leaders can see capacity, margin, and delivery risk before commitments are locked in.
It doesn’t replace your tools. It makes them work together for planning in a way they were never individually designed to do. And if you swap out one tool (say your PM team wants to move from Asana to Monday), the rest of your stack stays intact. Parallax just connects to the new one.
That flexibility matters. The agencies that stay on duct-taped spreadsheets aren’t lazy. They’ve just been burned by systems that tried to do everything and did nothing well. Parallax is built specifically for project-based businesses that sell time. Not inventory. Not widgets. Time.
Key takeaways for agency leaders
Scope creep is a visibility problem, not a discipline problem. Brian’s team wasn’t careless. They were trying to make the client happy without the data to understand the cost of saying yes.
Your spreadsheet is a symptom. If the most complex formula in your company lives in a planning spreadsheet that only one person can update, that’s not resourcefulness. That’s missing infrastructure.
Reactive management has a dollar value. Add up the write-offs, the margin misses you discovered too late, the clients who left over communication failures. That number is your business case.
Name-brand software is not built for you. The tools your CEO peer group recommends were designed for product companies. Purpose-built options exist for services businesses. They’re harder to find, but they’re out there.
Culture changes alongside systems. Better tools without better process just gives you faster access to the same chaos. Ops review on proposals, documented change orders, and weekly margin check-ins are what close the gap.
FAQ
More than most people track. PMI data shows scope creep hits over 50% of projects, and the cost ranges from 10% to 50% of total project revenue depending on severity. But that’s just the direct hit. For a mid-sized agency running multiple concurrent projects, even small scope expansions compound into six-figure annual losses once you factor in the write-offs, the delayed timelines on other projects, and the downstream client trust damage that nobody ever puts a number on.
It’s rarely one thing. Disconnected systems prevent leaders from seeing margin and capacity in real time. Sales teams set optimistic timelines without operations input. Change order processes don’t exist or get skipped. And the whole culture tends toward reactive management where problems are only visible after the damage is done. Brian’s story is a textbook case of all four happening at once.
Two things need to happen together. First, connect your operational data (CRM, project management, timesheets, financials) into a single planning layer that shows margin, capacity, and delivery risk while there’s still time to act. Second, pair that with process changes: pre-sale ops review on proposals, documented change orders, weekly project margin reviews. Tools without process is just faster chaos. Process without tools is just more spreadsheets.
It’s the disconnect between the decisions leaders need to make right now (pricing, hiring, resourcing) and the information their systems can actually provide at that moment. Delivery tools show what’s happening today. Finance systems explain what already happened. Neither one was built to answer the question leaders actually need answered: what’s likely to happen next? That gap is where agencies lose money, and it’s the reason most operational problems feel like they appear out of nowhere.
