Why Your Business Can Feel Successful While Making You Poor

I know a contractor I'll call Gavin. Fifteen years in the business. Team of twelve. Strong demand, clients who refer him constantly. And just last month, he told me something that stopped me cold: he'd been racking up debt to buy the parts for a job — even though the deposits for that job had already cleared his account.

How does that happen?

That question is really what this post is about. Because Gavin isn't unusual. His situation plays out in hundreds of service businesses — contractors, consultants, agencies — businesses doing real revenue, sometimes a million dollars a year or more, where the owner is still privately wondering whether they can make payroll this month.

I recorded a full video walkthrough that goes deeper on all of this — including how to start fixing it in the right order. But here's the framework: there are three reasons your business can have good sales and still leave you broke, and they need to be worked on in a specific sequence.

Problem 1: You don't have a financial operating system

Here's what Gavin does have: QuickBooks, a bookkeeper who reconciles weekly, an accountant who files his VAT and corporate tax, and a cash flow spreadsheet he checks most days. He is not an unsophisticated guy.

But none of that infrastructure was ever built to tell him what his cash is supposed to do.

Standard small business accounting was designed to do three things: record transactions accurately so the books reconcile, produce P&Ls and balance sheets for tax filing, and calculate what you owe the tax office at the end of the quarter. That's it. It does those three things well. It was never meant to do anything else.

What it doesn't do — what no standard accounting setup does — is tell you whether the €40,000 sitting in your account today is yours, or earmarked for the VAT bill in six weeks, or supposed to pay for materials on the next job, or already promised to payroll. These reports are retrospective. They tell you what happened. They don't pre-allocate cash to its future purposes, because that was never the job description.

So Gavin, when he needs to decide what to pay this week, falls back on the instruments most legible to him: the bank balance and the spreadsheet. Neither of which contains the information the decision actually requires.

Here's the loop that runs as a result. Money arrives. The balance looks healthy. Gavin pays what seems urgent — rent, payroll, a supplier. Then a tax bill appears, bigger than expected. He pays that. The balance shrinks. His chest tightens. He buries himself in more work, chases receivables, stalls a supplier, reaches for the card.

He once told me: "Tens of thousands flow through my hands every day, and yet there are days I'm not even sure we can buy toilet paper. Every end of month is a scramble."

And the deposit story? Here's what actually happened. The deposits hit the account, the balance went up, something else was more urgent that day, so the deposit got used. By the time the parts needed to be ordered, the money was gone.

People are quick to call this dishonest. I'd push back on that. This is what happens when the bank account is your primary instrument, and the rest of your financial system was built to answer the tax office's questions, not yours.

The fix: Add a structural layer on top of the accounting you already have — one that decides what the cash is for before you have a chance to spend it. Mike Michalowicz's Profit First describes one practical way to do this: set up a series of separate bank accounts, each for a specific purpose (income, owner pay, operating expenses, tax), and assign allocation percentages to each. Whenever money comes in, it gets distributed automatically based on those rules.

If you're on the smaller end of small business, you can implement this roughly as-is from the book. If you're bigger — with a CFO, working capital lines, or accrual obligations that span quarters — the tactic gets a bit clunky, but the principle still holds: cash needs pre-allocation, and the allocation rules need to be decided before the money arrives.

But here's the thing: even if you build the perfect cash system, it won't fix you if your prices are built on numbers that don't reflect reality. Which brings us to problem two.

Problem 2: You don't have a clear picture of what your work actually costs

Let me ask you a direct question: which of your last five jobs was the most profitable? Not which one paid the most — which one, after everything you actually spent to deliver it, left you with the most margin?

If you can answer that within thirty seconds, you can probably stop reading here.

Most business owners can't. And in service businesses especially, the problem isn't that the data doesn't exist. The problem is whether the data is accurate — and whether it actually reflects the true cost of delivering the work.

Back to Gavin.

A client calls about a job. Gavin quotes two hours. He starts the work, hits a complication, spends another hour figuring it out. The job takes three hours. When he invoices, he charges for two — because he thinks: if I were more experienced, I'd have known how to handle that. It's not fair to charge the client for my learning curve.

What Gavin just did is subsidize that client by an hour. Out of guilt. He was being genuinely nice about it.

Then the next client calls, referred by the first. Similar job. Gavin remembers it as a two-hour job — because that's what he charged. He quotes two hours. This one takes three and a half. He writes off another hour and a half for the same reason.

By the time he's done ten of these jobs, the quotes he's giving out have been calibrated against years of essentially untrue costs. Every new client is priced based on what he chose to charge for past work, not what that work actually cost to deliver.

And once the business has a team, this gets worse. Gavin doesn't just quote his own jobs anymore — most of the quoting is for work his crews do. He prices that work based on assumptions he built from his own inaccurate data, and that assumption now scales across every job his team touches.

There's another version of this that's worth naming directly: unpaid overtime. Every end of quarter, Gavin's team racks up significant extra hours — admin with month-end deadlines, a push to close jobs before cutoff. Gavin doesn't pay much attention because most staff are salaried. The labor cost on paper looks fixed.

But the work that happens in those extra hours is real work. A lot of projects get delivered on time because of it. And because nobody counts the overtime, every project looks like it came in on budget — which means the next quote gets built on the same assumption.

This model only works as long as people keep absorbing hours nobody is paying them for. The moment someone quits, asks for a raise, or simply burns out, the economics collapse.

This isn't a talent problem. You can't solve it by asking your team to work harder. It's a measurement problem. The numbers in Gavin's books say the model works. The reality his people are living tells a different story. The gap between those two is exactly where the business is bleeding.

Problem 3: The business model itself doesn't work

This is the hardest one to hear. But it's also the one that surprises people the most — because businesses can run for a very long time on a model that fundamentally doesn't add up.

Once Gavin stops editing his hours — once the quotes start reflecting what jobs actually cost — he discovers something worse. The prices his clients are willing to pay are below the real cost of delivering the work. Not because he's underpriced relative to competitors. Because the cost of delivery, honestly counted, is higher than the rate the local market will bear for his trade.

A concrete example with fictitious numbers. Say Gavin's crews bill at €110 per hour. Field staff are paid €30. On paper: an €80 margin. But add in the hours that aren't on the timesheet (real days run closer to nine and a half hours, not eight), the unbilled drive time between sites, the warranty callbacks, the proposal hours, the office manager, the estimator, the trucks, the insurance, the yard — and the real cost per billable field hour is closer to €100. The margin isn't €80. It's €10. Before Gavin pays himself.

If he raises his rates to €150 to fix this, he's afraid half his clients will leave. Not because he's doing bad work — but because the value perception his business has built, relative to other contractors in his market, might not justify the jump in price.

And if he can only charge €110, and €110 barely covers everything, then he has a fundamental problem that no cash system or timesheet reform will solve on its own.

To fix a broken business model, you have to actually rework it. Maybe Gavin stops taking small residential jobs with terrible margins and focuses on commercial. Maybe he repositions around a specialty where the rate is higher. Maybe he restructures the team — fewer people, higher utilization, lower overhead. These are bigger changes. And while fixing the cash system and fixing the measurement is genuinely helpful, those fixes make the problem visible. They don't fix the problem by themselves.

How to work on this — in the right order

If this sounds like your situation, here's how I'd approach it.

You run two tracks in parallel, and then, based on what you learn, tackle the third.

Track one: build a financial operating system. This comes first because managing cash without a system eats enormous mental bandwidth — and in 2026, setting up additional business accounts is actually pretty fast. The hard work is deciding the allocation percentages and briefing your accountant, but that shouldn't take long. It won't fix your business by itself, but it's low-effort, high-reward, and it frees your brain. Start this immediately.

Track two: audit what your work actually costs. This runs in parallel because it takes time. If your team doesn't yet have the habit of tracking hours accurately, building that habit and getting consistent data is a project in itself. You need at least a few weeks of clean data — often months, depending on your delivery cycle — before you can draw real conclusions. So the sooner you start, the sooner you know. High-priority. Start now.

Then, once track two has enough signal: ask the bigger question. Does this model actually work? Sometimes the answer is yes — the fixes are tactical. You adjust the price, fix the scope, stop absorbing rework, and calibrate the financial OS to the real numbers. Done.

Sometimes the answer is no, and what needs to change is bigger: your positioning, the type of clients you take, how work gets delivered, your cost structure. But you can only see that clearly once you have honest data. You cannot make a strategic decision on numbers you haven't updated in years.

I walk through all of this in more detail in the video above — including how to think about the allocation percentages for the financial OS, and what "auditing your costs" actually looks like in practice for a service business.

One more thing

This post isn't really about Gavin. It's about the gap between what a business looks like from the outside and what it feels like to run it. Good revenue and financial stress coexist more often than people admit — and if you're in that situation, it's not because you're doing something dishonest or incompetent. It's almost always because the systems around you were built to answer someone else's questions, not yours.

The work to fix it isn't technically complicated. What makes it hard is that it asks you to question assumptions you've built the business around for years. That's the part people stall on alone.

If you'd rather not do it alone, that's what I do.