# Getting Your Numbers Together
{% 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 %}
### Introduction: Financial Accounting Disguised as Field Intelligence
Daniel Honan's book, Profitable Painter: How to Scale Your Painting Business, positions itself as the definitive guide for painting contractors looking to grow their businesses. Chapter 7, "Basics of Getting Your Numbers Together," promises clarity and control. Honan claims that knowing your numbers lets you "diagnose problems and solve them before they grow," "bid jobs confidently," and "set prices based on profit, not fear."
What the chapter actually delivers is a framework for historical financial accounting that provides neither clarity during the work nor control over outcomes.
The fundamental confusion appears immediately: Honan believes "getting your numbers together" means organizing bookkeeping systems and reviewing financial reports. He's describing administrative compliance—the backward-looking work of reconciling what has already happened for tax and financial reporting purposes.
What painting contractors actually need is real-time measurement of production variables that enables them to understand what's driving outcomes while they can still affect those outcomes. Honan is teaching owners how to understand what happened last month. What they actually need is a system for understanding what is happening right now, so they can improve what will happen tomorrow.
The difference between financial accounting and field measurement determines whether a company can improve or merely document its dysfunction at higher revenue levels.
Honan's chapter reveals, through both explicit instruction and glaring omission, that he fundamentally doesn't understand what makes painting operations function. He's written a guide to tracking money without ever addressing how to track, measure, or improve the work that generates that money.
### The Bookkeeper Problem - **Who Gathers Your Numbers?**
Honan states clearly: "You, the owner, are responsible for understanding the numbers, but you don't need to be the one gathering them. That's the job of your bookkeeper—ideally someone who understands the painting industry."
This single recommendation exposes the entire flaw in his thinking.
A bookkeeper reconciles accounts. They process payables and receivables. They categorize expenses. They maintain financial records for tax compliance and generate P\&L statements. This is backward-looking administrative work—essential for running a legal business entity but completely divorced from operational control of the actual work.
What painting contractors actually need when "knowing their numbers" is real-time field intelligence: knowing daily whether a 5-day job is tracking with the estimate, understanding by noon whether morning production matched projection, recognizing immediately what's consuming resources and why, capturing cause-and-effect relationships while the work is happening, and making immediate corrections when variables deviate from standard.
None of this is bookkeeper work. A bookkeeper isn't on the job site at noon, seeing that prep is running long because conditions weren't what the estimate assumed. They're in an office days or weeks later, entering expenses from receipts, wholly divorced from the field context that explains those numbers.
The suggestion that a bookkeeper who "understands the painting industry" can gather meaningful numbers reveals that Honan doesn't know what numbers actually matter. A bookkeeper who understands painting might correctly categorize sprayer purchases as equipment expenses rather than materials. But they don't know—and have no way to know—that a crew burned an extra hour on a ceiling because the previous coat was applied too heavily and needed an additional hour to dry, and now the team is unable to start painting walls.
That *subtle* extra hour is the number that matters. It's the data point with immediate instructional value for the next similar job. It's what improvement is built on. But it's not a number any bookkeeper will ever see, because it requires measurement during the work, not financial categorization after the fact.
Honan's bookkeeper model means contractors are getting financial summaries weeks later, stripped of all field context. They can see that Job #247 cost more than estimated, but they have no record of why. Was it an inefficient prep sequence? Poor material yield? Surface conditions? Scope creep? The context is gone. The crew has moved on. They're left guessing what might have happened.
This is the infrastructure of permanent ignorance. You can run a painting business this way for decades and never allow the work to teach you, because you're not measuring the work—you're just generating expense reports.
Measurement is how you convert experience into knowledge. Forty years of painting isn't just time served—it's forty years of documented patterns and failures, but only if you tracked what actually happened while it was happening.
### Monthly Tracking - **Running Blind at Scale**
Honan recommends reviewing numbers "monthly at a minimum" and suggests weekly dashboards are "even better." But his default recommendation—monthly review—reveals an astonishing lack of understanding about operational control.
The monthly review answers the question, "Did we lose money?" Real-time tracking answers the question, "Why did it happen, and can we fix it before tomorrow?"
A monthly review means you're running blind for weeks at a time.
Consider what happens in a month: a residential repaint company might complete 15–25 jobs, a crew of three painters works approximately 480 labor hours, thousands of individual production decisions get made, and hundreds of opportunities for efficiency or waste occur.
If you're only reviewing numbers monthly, all of that activity happens with zero real-time feedback. You're operating on assumptions about productivity, hoping crews are working efficiently, and waiting until the month's end to find out whether the jobs were profitable.
By the time the monthly P\&L arrives, you've already completed dozens of jobs (some profitable, some not), paid for any inefficiencies that occurred, moved on to new work, potentially repeated the same mistakes, and lost all context that would explain the variances.
This isn't management. It's an archaeological investigation of what already happened.
The compounding effect at scale is staggering. Honan loves to reference companies with large crew counts. Imagine tracking 150+ employees with monthly reviews. That's 150+ people potentially drifting off course for weeks before anyone notices. All of it is invisible until the monthly financial summary shows you missed margin targets.
And even then, the monthly P\&L doesn't tell you which crews or what specific behaviors drove the loss. It just tells you that you lost money. So now what? Have a 'motivational' meeting about "doing better next month"?
Compare this scenario to actual operational control:
A contractor running a 5-day job who tracks numbers daily knows by the end of Day 1 whether the work is on pace. By Day 2, they know whether the estimate was accurate or needs adjustment. By Day 5, they know exactly what drove any variance from the plan.
Better yet: A contractor who tracks hourly knows by noon whether morning production matched the plan. If the preparation was budgeted for 4 hours but has reached 5 hours by lunch, the contractor will not wait until Friday to identify the overrun. They're diagnosing immediately: Was the scope assessment off? Is the approach inefficient? Does this condition genuinely require more time?
That immediate awareness creates the decision point: adjust the afternoon's approach, re-sequence the work, or accept that this specific condition requires the extra time and update estimating data accordingly.
This is operational control. You're diagnosing and correcting in real time, not discovering problems weeks later when correction is no longer possible.
Monthly tracking, by contrast, provides no operational feedback during the work. It's purely a financial retrospective. By the time you see the P\&L, the opportunity to improve that job is gone.
Honan's monthly review model can tell you that last month was unprofitable. It cannot tell you how to make next month more profitable.
This matters because efficiency improvement—getting more output per unit of input—is what creates the widening gap between revenue and expenses that defines scaling. Without real-time operational measurement, you can't improve efficiency. You're stuck documenting whatever productivity level you currently have.
Which brings us to the question Honan never addresses: How do you actually improve?
### System A vs System B - **Standardization Requires Real-Time Measurement**
Consider two models:
**System A - No System:** Each of the eight painters, each using their preferred tools and methods. Purdy brushes, Wooster brushes, and Corona rollers. Nine-inch rollers, twelve-inch rollers. Buckets, trays, and two-inch brushes. Everyone is doing it their own way.
**System B - Same System:** Two painters following documented standard work. Same tools, same products, same sequences, same techniques. Consistent execution.
Honan's monthly tracking model enables System A at scale.
When you're only reviewing financial summaries monthly, you have no mechanism to identify which of the eight different approaches is actually most efficient. The P\&L displays the overall results, encompassing all the variability in performance. Some jobs are profitable, some are not. Some crews are quick, some slow. There is insufficient data to determine which factors contribute to these differences.
So everyone keeps doing whatever they've been doing. Preferences persist because there's no measurement system to challenge them with actual data.
"I like Purdy brushes" remains a valid operating principle because no one has data to prove that another brand produces 180% better results.
"I prefer 9-inch rollers" continues unchallenged because no one has documented that 18-inch rollers achieve better coverage rates on large surfaces.
Preferences proliferate. Randomness compounds. The company operates as a collection of individual painters, each executing their own interpretation of how painting should be done.
System B requires real-time measurement to develop and maintain.
You can't establish standard work without systematic observation of what actually produces optimal results. Which tools? Which products? Which sequences? Which techniques?
These aren't philosophical questions. They're empirically answerable through measurement: time to completion, material consumption, coverage rates, quality outcomes, and consistency across repetitions.
But you only get this data through real-time job tracking. Watching the work happen. Documenting what produces results. Testing variables systematically. Building evidence.
Over 40 years of job tracking have documented what efficiency actually looks like. We already know which tools, products, sequences, and techniques produce optimal results under different conditions. That knowledge didn't come from monthly P\&L reviews. It came from real-time observation and measurement of thousands of jobs, with documented outcomes.
That's not preference—that's data.
And once you have evidence-based standards, you need real-time measurement to maintain them.
Without real-time measurement, operational drift is guaranteed. Tasks deviate. Tools drift. Methods diverge. Month-end P\&Ls can't detect drift—they can only report the damage.
Standard work only works if it is executed as specified. Real-time tracking tells you immediately when deviations occur: a crew using a different product than specified, an application technique not matching the documented method, a sequence out of order, or coverage rates below standard.
You correct it in real-time, before the deviation becomes the new norm.
Monthly tracking can't maintain standards because by the time you discover a deviation, dozens of jobs have already been executed incorrectly. The drift has already occurred.
Honan's framework never addresses any of this. He provides no discussion of how to identify optimal approaches, document standard work, measure compliance with standards, or improve methods.
He thinks painting companies should do what they do now, and the only question is if they're charging enough.
You can't improve productivity without measuring it. You can't standardize without documenting what "right" looks like. You can't scale efficiency that you never established.
Monthly financial tracking enables System A—eight painters doing eight different things with no way to determine which approach is actually best.
Real-time operational measurement enables System B—documented standards, consistent execution, and systematic improvement.
The difference isn't cosmetic. It's the difference between random results and predictable outcomes.
### The Software Illusion - **Tools Without Understanding**
Honan devotes considerable space to software recommendations: QuickBooks Online for bookkeeping, Google Sheets for job costing, a CEO dashboard that pulls data from QuickBooks and your CRM, and Google Drive for cloud storage.
The recommendations themselves are reasonable. The problem is what's missing: any explanation of what to measure, why it matters, or how to use the data to improve operations.
Software is a tool. It doesn't generate insight—it just records whatever you tell it. If you don't know what variables drive outcomes, software won't tell you. It will just organize your ignorance more efficiently.
Honan treats software selection as the solution to "getting your numbers together." But software doesn't determine what numbers matter. Understanding production physics determines that.
Consider [job costing](https://jackpauhl.gitbook.io/archive/field-notes/operations-systems/job-costing) templates. Honan mentions them as a way to compare estimated versus actual labor and materials. But knowing where time went is only helpful if you know where time should go. Otherwise, you're just documenting current performance without any basis for improvement.
Real-time tracking systems are built around operational questions:
* What's the standard time for prepping 500 linear ft of previously painted trim?
* How does surface condition affect that standard?
* When actual time exceeds standard, what specific conditions caused the variance?
* How do we adjust either the method or the estimate based on this data?
These questions require understanding what actually produces results. Software can help organize the answers, but only if you're asking the right questions.
Honan's software recommendations skip this entirely. He's describing data collection without operational context—which is precisely what produces the monthly P\&L problem. Lots of numbers, no insight into what drives them.
The irony is that contractors don't need specialized software to begin measuring operations. A notebook and pen work fine for tracking daily progress against the estimate, documenting conditions that affect productivity, and recording what actually happened versus what was planned.
The measurement mindset matters infinitely more than the tool used to record it.
But Honan treats software selection as the primary concern, suggesting he's focused on administrative systems rather than operational improvement.
### The Pricing Problem - **Raising Prices to Hide Inefficiency**
Honan's solution to underpricing is straightforward: raise your prices.
He provides detailed frameworks for markup calculations and profit margin targets. It assumes the operational side is fixed, so the only variable you can control is price.
This is growth mode thinking masquerading as business strategy.
Raising prices increases revenue without improving productivity. It's a vertical shift of the revenue line while the expense line stays parallel. The gap between them (profit) increases, but only because you charged more for the same work.
This model works in markets with pricing power and limited competition. It fails when competitors can deliver equivalent results more efficiently at lower prices.
True scaling requires improving the denominator—getting the same output with less input. The goal is to achieve the same revenue with lower costs. Better yet: more revenue, proportionally slower cost growth.
This phenomenon occurs only through operational improvement: developing methods that reduce labor hours, establishing standards that ensure consistent efficiency, measuring in real time to maintain those standards, and refining the process.
Honan's framework provides none of this. He bases his entire approach to profit on pricing-side adjustment, treating the work itself as an incomprehensible and unimprovable entity. That assumption is false, but you'd never know it from reading his chapter.
The outcome is predictable: contractors raise prices, which works until market pressure forces them to compete on price again. At this point, they have no operational efficiency advantage to fall back on. They've been hiding inefficiency behind markup rather than eliminating it.
Consider the alternative approach:
A contractor who measures field operations in real-time knows their actual productivity. They know which methods produce better results in less time. They can reduce labor hours through improved processes, which lowers costs while maintaining quality.
Now, when they raise prices, they're capturing value from genuine efficiency gains—not just charging more while hoping to maintain margin.
This is the difference between operational control and financial management. One improves the work. The other tracks the results.
### The Marketing Distraction - **Optimizing Lead Sources While Operations Drift**
Honan includes a section on tracking marketing ROI—measuring which lead sources produce the most revenue per dollar spent.
This is helpful information for a company that has already optimized operations. For a company that hasn't, it's a distraction.
Marketing ROI tells you where leads come from. It doesn't tell you whether your crews work efficiently, whether your estimates reflect field reality, or whether your methods are optimal.
A painting company can have perfect marketing ROI tracking and still lose money on every job because its operations are inefficient. They'll just be generating unprofitable work more cost-effectively.
The emphasis on marketing metrics reveals Honan's growth-focused thinking: more leads, more jobs, more revenue. He's optimizing the front end (lead generation) without addressing the back end (production efficiency).
This philosophy is backwards. A company that improves efficiency can afford to pay more per lead because it extracts more profit per job. A company with poor operational efficiency will struggle regardless of lead cost, because it can't reliably deliver profitably.
Tracking marketing ROI is fine. But it's a second-order optimization that only makes sense after you've addressed first-order operational fundamentals.
Honan's framework treats marketing tracking as equivalent to operational measurement. It's not. One brings in work. The other determines whether that work generates profit.
### Growth Mode vs. Scale Mode - **The Fundamental Distinction Honan Misses**
Scaling isn't a modern invention; it's a manufacturing principle. In 1988, Sidney Conn defined it perfectly in *Inc. Magazine*:
> *"When we scale up, it's in manufacturing. Our sales staff can take on new orders without many new people."*
Notice what scaling actually means: you don't scale by hiring more people to sell. You scale by refining your production—your field operations—so existing capacity can absorb increased volume.
Growth without operational architecture is dangerous. You can grow yourself to death. Most companies chase more leads, more sales, and more conversions—but if you suddenly doubled or tripled volume, most operations would fail. The infrastructure isn't there to support it. Adding revenue without building an operational foundation to support it doesn't lead to scaling. It produces failure at higher volume.
Honan never mentions how to improve production efficiency. His entire framework assumes you scale by getting bigger, not by getting better.
Consider the distinction between two business models:
**Growth Mode:** Revenue and expenses rise in parallel. The gap between them (profit) exists but doesn't widen significantly as volume increases.
**Scale Mode:** Revenue accelerates while expenses grow more slowly. The gap between them widens dramatically with volume.
Growth mode depends on getting bigger. Scale mode depends on getting better.
Honan's entire framework produces Growth Mode, not Scale Mode.
Growth mode occurs when you add volume without improving efficiency: you get more jobs through marketing, add more crews to handle the work, overhead increases with headcount, and revenue and costs rise together.
This is precisely what Honan's system enables. His monthly tracking model provides no mechanism to improve efficiency, so adding volume means doing the same work the same way on a larger scale.
His "solution" to underpricing is to raise prices, which increases revenue without improving productivity. That's a parallel upward shift of both lines, not the widening gap that defines Scale Mode.
Scale mode requires improving productivity. Revenue must grow faster than expenses, which only happens when you're getting more output per unit of input: the same labor hours producing more completed work, the same overhead supporting more revenue, and efficiency gains.
This process requires exactly what Honan's framework lacks:
1. **Real-time measurement** to identify current productivity levels
2. **Standard work** to establish optimal methods
3. **Systematic improvement** to increase efficiency over time
4. **Operational control** to ensure standards are maintained
Without these, you can't improve the ratio of outputs to inputs. You're stuck with whatever productivity level currently exists, which means revenue and expenses rise together.
Honan's solution to profit is simple: raise prices and hope actual costs don't exceed the estimate. That's not a system. That's a wish.
When you track numbers during a 5-day job, you're controlling the expense line in real-time. You know immediately when costs are running ahead of plan, diagnose why, and make the necessary corrections.
When you review P\&L monthly, you discover weeks later that costs exceeded expectations, with no context to explain why and no ability to correct what already happened.
His monthly tracking, bookkeeper-gathered numbers, raise-your-prices solutions—all of it produces parallel line growth. This approach only exacerbates the already existing inefficiencies.
True scaling requires improving efficiency, which requires real-time measurement of field operations and an understanding of what actually produces results.
Chapter 7 does not address any of these aspects.
### The Numbers That Actually Matter
Daniel Honan's Chapter 7 promises to teach painting contractors how to "get your numbers together" to gain control and clarity. What it delivers are instructions for organizing accounting systems—a fundamentally different thing.
The confusion explains everything wrong with his framework: bookkeepers gather financial data, not operational performance metrics; monthly P\&L reviews document what happened, not what's happening; job costing templates reviewed after the fact can't improve jobs in progress; pricing adjustments mask inefficiency instead of fixing it; and marketing ROI tracking optimizes lead sources without improving production.
None of this helps a painting contractor understand whether their crews work efficiently, whether their methods are optimal, whether their estimates reflect reality, or whether their operations can improve.
This is what separates companies that randomly succeed from companies that intentionally improve. This is what converts experience into documented knowledge. This is what makes scaling possible.
You can run a painting business using Honan's approach. You'll have clean books, monthly financial statements, and organized QuickBooks files. You might even grow revenue substantially.
But you won't systematically improve. You won't build the foundation that enables you to scale.
Getting your numbers together entails measuring what drives outcomes in real-time during the work, rather than organizing receipts for your bookkeeper to categorize weeks later.
Honan has written more than 20 pages about numbers without once addressing the ones that actually matter. That's not an oversight. That's a complete misunderstanding of what makes painting businesses function.
The omission of production measurement isn't just a gap in his chapter—it's the hard boundary of his expertise. You can't teach what you don't measure.
Honan, like every other consultant operating at a distance, loves to oversimplify. They can ignore production reality. They can pretend operational measurement doesn't matter. They can build entire frameworks around accounting and call it "getting your numbers together."
However, the reality on the ground always presents a distinct narrative. The field is where profit is made or lost. The field is where efficiency exists, or it doesn't. The field is where the actual work happens.
And you have to be there to read the data.
### A Final Clarification—Visibility Is Not Causation
Recently, I’ve reviewed multiple testimonials from painting contractors who credit financial cleanup, accounting structure, and tax optimization for improvements in profit, cash flow, and margins. The stories are consistent.
In every case, the owner begins by admitting they did not understand their numbers. Books were messy. Taxes were being overpaid. Pricing errors were invisible. Once those issues were corrected, financial results improved quickly.
But it’s important to understand what actually changed.
In every testimonial, the intervention is administrative: classification, visibility, entity structure, and reporting. None of them describes changes to how work is executed in the field. No one mentions jobs finishing faster, fewer labor hours per job, reduced rework, tighter sequencing, or higher output per painter per day.
When revenue increases are mentioned, they are framed temporally—since working with an accountant—not causally. It is entirely plausible, and often likely, that revenue increased simply because more work was done during that period. Accounting does not create revenue. It records it.
Likewise, margin expansion and profit growth in these examples are consistent with pricing corrections, tax savings, and the elimination of obvious financial blind spots. Those gains can appear immediately without any change in production behavior.
**This distinction matters because visibility is not causation.**
This confusion between measuring results and managing the drivers that produce them is not new. Management theorists identified it decades ago and warned explicitly against mistaking scorekeeping for management. Also read: [Measurement Is Not Management](https://jackpauhl.gitbook.io/archive/field-notes/operations-systems/measurement-is-not-management)
Accounting tells you where money went.
It does not tell you why time was lost.
It does not tell you which methods outperform others.
It does not tell you how to produce more with the same labor.
Once an owner understands their numbers, they often feel like the business has been transformed. In reality, the business has become *legible*. That is a necessary step, but it is not the same as improving operations.
The next constraint always appears after visibility is achieved. Owners reach a point where margins look better, cash looks healthier, and yet the work still feels heavy. The days don’t shorten. Throughput doesn’t increase. Capacity still caps growth.
That is not an accounting problem.
That is a production problem—and it can only be solved where the work actually happens.
**Related:**
**Chapter 6:** [The Illusion of Numbers - Scaling Happens in the Field, Not in a Spreadsheet](https://jackpauhl.gitbook.io/archive/field-notes/operations-systems/the-numbers-illusion)
**Chapter 9:** [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)
