I've talked to dozens of agency owners over the past few years. The ones running 20–50 person shops, billing decent numbers, growing steadily. And almost every single one has told me the same thing at some point:
"We thought the project was profitable. Then accounting closed the month and we found out we were down ₨800,000."
The numbers change. The story doesn't.
This isn't bad luck. It's a structural problem — and it has a structural fix.
The real reason agencies discover losses late
The problem isn't that agencies don't track hours. Most do, loosely. It's that the data that determines profitability sits in three or four completely separate places:
- The deal value is in your CRM
- The hours logged are in your time tracking tool
- The costs (contractor invoices, subscriptions, tools) are in a spreadsheet or accounting software
- The invoices sent are in yet another tool
None of these talk to each other in real time. So when you ask "are we making money on this project?", the honest answer is: you won't know until someone manually pulls all four data sources together. And that usually happens at month-end, long after the project is over.
By then, you can't fix it. You can only document the loss.
The 15–25% problem
There's a second issue that compounds the first: unlogged hours.
In most agencies, somewhere between 15–25% of billable hours go unlogged. Not because your team is lazy — because the logging experience is friction-heavy enough that people batch it, forget it, or estimate. By the time someone logs hours from memory at the end of the week, they're almost always underestimating.
If your team bills at ₨4,000/hour and you're losing 20 hours per person per month to underlogging, that's ₨80,000 per person in unrecovered revenue. On a 10-person team, that's ₨800,000 every month left on the table.
This isn't a time tracking problem. It's a workflow problem. Time tracking that's disconnected from where work actually happens will always have low compliance.
What "connected" operations actually looks like
The fix isn't a better spreadsheet or a stricter process. It's changing the architecture so that profitability is visible while the project is running, not after it ends.
Here's what that looks like in practice:
-
Your deal value becomes the project budget automatically. When you close a deal for $15,000, that number should become the project budget without anyone copying it. The moment you convert the deal to a project, the budget is set.
-
Hours are logged where work happens. If your team uses task management, time logging should happen directly from the task. One click to start a timer, one click to stop. Not a separate tool, not a weekly form.
-
Margin is calculated in real time. As hours are logged, the system should show you: budget consumed, revenue recognized, and estimated final margin — automatically, without a spreadsheet.
-
Invoices pull from logged hours. When it's time to invoice, you shouldn't be reconstructing billable hours from memory. You should be selecting the project, seeing all unlogged billable time, and generating the invoice from that list.
When these four things are connected, you stop discovering losses after the fact. You see them forming while you still have time to adjust scope, have a conversation with the client, or redeploy your team.
The uncomfortable conversation you're avoiding
There's one more thing that keeps agencies in this cycle: the reluctance to have hard budget conversations mid-project.
When you don't have real-time visibility, you can't have those conversations confidently. You're guessing. So you avoid it, hope it works out, and find out at the end that it didn't.
When you do have real-time visibility, the conversation becomes a lot easier. "We're 60% through the budget and 40% through the work. We need to talk about scope." That's a professional conversation. Clients respect it.
The data doesn't just help you close the loss — it gives you permission to have the conversations that prevent it.
A practical starting point
If you want to start solving this today, before you change any tooling:
- Pick one project and track it with obsessive accuracy for one month. Log every hour, every cost, every invoice. Calculate the actual margin at the end.
- Compare it to your estimate. Not the revenue — the margin. Most agencies estimate revenue reasonably well. Margin is where the surprises live.
- Find the gap. Was it unlogged hours? Scope creep that wasn't billed? Underestimated work? The answer tells you where to focus.
Once you know where your margin is going, you can build the operational fix around that specific leak. The tooling follows the diagnosis — not the other way around.
ACOS was built around exactly this problem. The operational loop — Deal → Project → Tasks → Time → Invoice → Profit — is designed so that every number flows forward automatically, and margin is visible in real time throughout the project lifecycle. If that's a problem you're trying to solve, try it free for 21 days.
