# The Numbers Illusion

{% hint style="info" %}
This is a living document. It is maintained and updated without notice. It's best to refresh pages to ensure delivery of the latest iteration from the CDN Content Delivery Network in your area
{% endhint %}

I purchased *Profitable Painter* because I thought I’d learn something new about scaling. Instead, I found myself writing the article the book should have given me. Chapter 6 promises to show painters how to “get past $1.5M using numbers,” but it never delivers anything that actually scales a business. That’s what bothered me—I spent the money, and I’m still the one explaining what scaling actually is.

The book is marketed as a roadmap for growing and “scaling” a painting business. It was written by Daniel Honan, a CPA who works with painting contractors, and much of the book tries to connect financial visibility with business growth. Chapter 6 is where Honan claims painters can “get past $1.5M using numbers,” and that's what this article responds to.

On the surface, it reads like scaling advice, but a few paragraphs in, you realize it isn’t about scaling at all. It is simply about getting control of a messy business through basic financial housekeeping. There’s nothing wrong with that, but it isn’t scaling. Honan assumes that looking at numbers somehow changes what happens in the field. That’s the main mistake, and it runs through the entire chapter.

He uses a contractor named James as the example. James was doing about $1.2M a year, worn out, chasing estimates, and still couldn’t pay himself every month. His gross profit jumped all over the place—from 18% to 55%—because the jobs, the estimating, and the execution were never the same. But instead of calling that what it is, the chapter treats it like James couldn’t “see” his numbers. The real issue wasn’t visibility. The issue was the work itself.

And James isn’t an outlier. I know a local contractor doing around the same revenue—about $1.2M, maybe a little more—and he was still $40,000 in debt. And here’s the part that matters: his work was new construction, painting the same four model homes over and over. It doesn’t get more repetitive than that. Painting new homes wasn’t the issue itself. The problem was that he assigned six people to a job that only needed two, and they were constantly redoing their work. His system was wrong, and the results showed it. Repetition doesn’t fix a bad workflow. Adding people doesn’t fix a bad workflow. The system (the order of workflow) has to be right first. And that correction was made in the field, not on a spreadsheet, raising prices or marking up labor and materials.

Back to James— James improved his numbers only after he started measuring what he was already doing. He reallocated his marketing budget, tweaked pricing, and hired a part-time production manager. With those changes in place, he finally paid himself $12,000 a month “consistently for the first time.” The sentence contradicts itself—but that isn't the real issue. Did you notice what's missing? No corrections were made in the field. The real issue is that if you’re doing $1.2M in residential repainting and you can’t pay yourself every month, the problem isn’t dashboards. That tells you something in the field is wrong. Dashboards don’t fix field problems; they display them.

Honan insists this is the formula for getting past $1.5M. But nothing in the chapter has anything to do with scaling. James didn't increase capacity. He didn't build anything that could run the same way twice. He didn't standardize production or implement Standard Work. He merely stopped leaking money. That's housekeeping, not growth.

To call this “scaling” is to misunderstand what scaling is entirely.

Scaling is growing revenue without costs rising at the same rate. When you scale, the business produces more without spending proportionally more. If your costs climb dollar-for-dollar with your revenue, you didn't scale—you just made yourself busier.

Honan never explains what the part-time production manager actually did. There's nothing about how crews were trained or onboarded. No Standard Work. No steps. No sequence. Nothing about reducing variables. Instead, the chapter stays focused on dashboards, cash flow, and gross profit targets—as if a spreadsheet is what makes the results better. It doesn't. Financials are the scoreboard, not the game.

The chapter acts like reports drive results. Gross profit, job costing, and cash flow all tell you what has already happened. They don’t fix anything. They don’t make tomorrow's results better. They show you the outcome of the decisions you already made.

| Metric Type           | Example                          | Function                                              |
| --------------------- | -------------------------------- | ----------------------------------------------------- |
| **Lagging Indicator** | Gross Profit / P\&L              | Tells you the score of the game that is already over. |
| **Leading Indicator** | Standard Work / Production Rates | Dictates the results of the game before it is played. |

You cannot reduce labor costs by adjusting a spreadsheet. You solve labor costs by fixing the work. You fix the work by defining the work. That means Standard Work—the exact sequence, tools, and motions required to achieve predictable production rates across crews. Without that, you don’t have a scalable business. You have a set of unpredictable results, and your P\&L will reflect every bit of that inconsistency.

Honan puts the entire burden of scaling on “getting your numbers together.” But getting your numbers together only shows you what already happened. It doesn’t change how the work gets done.

The industry repeats a backwards order: sell more work, look at the P\&L, see the margins drop, then hire a production manager and hope they can straighten it out. That approach fails because the systems were never established in the first place. You end up hiring someone to manage problems instead of managing a system.

The idea is simple. You reduce variables by creating Standard Work, so everyone performs consistently. Once the work is consistent, the results become consistent. Only then do you hire someone to manage the system. When the work is steady, the numbers settle down on their own. The numbers become confirmation, not the driver of results.

Honan talks about profit as if it disappears and then magically “returns” once you hire the right people and watch your numbers. But profit doesn’t come back on its own. Profit comes from steady, repeatable work. A spreadsheet can’t create that. Only a system can.

If you want to get past $1.5M, dashboards aren’t the answer. You need the work to run the same way, regardless of who’s doing it. You need fewer variables, predictable results, and crews that follow the same steps and standards every time. When the work is steady, the numbers show it. The Profit and Loss (P\&L) provides an accurate picture of the system's performance.

The chapter confuses seeing the truth with creating it. Seeing your numbers isn’t scaling. Scaling is building a system that produces clean numbers because the work behind the numbers is consistent. Once you do that, the financials stop being something you chase and start being something you trust.

And that’s the whole problem with Chapter 6. It treats looking at numbers as if that's what drives the business. It isn’t. Scaling has nothing to do with dashboards. It comes from how the work is done every day.

**Up Next:** Chapter 7: Profitable Painter ["Getting Your Numbers Together" - A Masterclass in Missing the Point](https://jackpauhl.gitbook.io/archive/field-notes/operations-systems/profitable-painter-chapter-7)

**Also Read:** Chapter 9: Profitable Painter [How To Estimate to Hit Profit Margins - The Truth About Job Site Variables](https://jackpauhl.gitbook.io/archive/field-notes/operations-systems/how-to-estimate-to-hit-profit-margins)