Your production manager knows more about your profitability than your accountant does.
I mean that literally, and I'll defend it. Your accountant sees the dollars after they've been averaged into a fog — a year of jobs melted down into a P&L. Your production manager sees the days. He knows which jobs came off the truck clean and which ones ate a second week. He knows which installs generate the callback calls and which ones you never hear about again. He knows which product line the A-team dreads and which one a B-crew can build in their sleep. Days, callbacks, crews — that's the raw material of gross profit per crew-day, which means the man who schedules your crews has been carrying your real job-level economics around in his head for years.
Nobody's ever asked him for them. Not once, in most companies. He gets asked about schedules and he gets asked about problems, and the knowledge that would reprice half the sales sheet just rides around in his truck.
Block Four asks him. Five questions, and for this block the owner's job is to sit still, keep the promise he made in Chapter 6 — nobody is in trouble — and hold his face steady, because his production manager is about to tell him things his sales floor would rather he didn't hear.
What's your typical days-to-build, by product?
Which jobs require the A-team, and which can run on a B-crew?
What's your callback rate by line — honest number?
What goes wrong most on site — permits, engineering, material lead times, inspections, subs?
Which jobs feel like they tie up the whole company, even when they look fine on paper?
Days-to-build. This is the most important boring question in the book. Crew-days are the denominator of the king metric — gross profit per crew-day — and here's the industry's dirty secret: almost nobody tracks them. Your books know what every job sold for and what the materials cost, down to the penny. Ask how many crew-days that sunroom actually consumed — the real number, with the return trip for the inspection and the half-day the electrician no-showed — and the building goes quiet. QuickBooks doesn't have a field for it. The schedule had a plan for it. Nobody wrote down what happened.
So I take the production manager's stated days-to-build by product, flag them like everything else, and I'll tell you what I tell every owner: this is the number your company needs to start writing down this week, before any system, before any software, before anything else in this book. A job's price tells you what the customer valued it at. Its crew-days tell you what it cost you in the only currency you can't buy more of. Two jobs, same ticket, same margin percent on paper — one builds in four crew-days, one builds in nine — are not the same job. They're not even close to the same job. And every company that doesn't track crew-days is averaging those two jobs together and calling the average a business.
Now let me hand you the king metric itself, because I've been waving at it since Chapter 7 and this is the chapter where you earn it.
GPPCD — gross profit per crew-day. The formula is one line of arithmetic:
GPPCD = gross profit on the job ÷ crew-days the job consumed
That's it. Contract price, minus materials, minus direct labor and subs — that's your gross profit, and your books already have it. Divide by the crew-days you just started tracking. A $28,000 sunroom with $16,000 of cost carries $12,000 of gross. If it built in four crew-days, it made you $3,000 a day. If it built in nine — same job, same signed contract, same proud line on the sales report — it made you $1,333 a day. One of those jobs is a business. The other one is a hobby with a deposit check.
And here's how to read the number, because a GPPCD floating alone tells you nothing until you put two lines under it. The first line is your break-even floor: take your monthly overhead nut from Block One and divide it by the crew-days you actually field in a month. That's what every crew-day must earn just to keep the lights on — for most shops it lands somewhere around $2,000 a crew-day, but compute your own, because your nut is your nut. The second line is your profit target — the number a crew-day has to hit for the company to actually be worth owning, and I set it around $3,500. That gives you three verdicts, and only three:
- PRINTS — above the target. This line makes money every day a crew touches it. Feed it.
- THIN — above the floor, below the target. Read this one carefully: THIN is *not* a loss. It's covering its overhead and dribbling out a little profit. It's a line you fix — faster builds, better price, tighter scope — not necessarily a line you kill.
- LOSES — below the floor. Every crew-day on this line costs you money you already spent. The sales sheet says it has a margin. The calendar says it's eating you.
Now the move that makes it a management tool: run it by product, not by job. One job can catch a bad inspector. A product line that averages thin over a year is telling you the truth about itself. Line up every product you sell — average ticket, average gross, average crew-days, GPPCD, verdict — and rank them. This is exactly the table my system builds automatically off the QuickBooks feed, job by job, every night; but you don't need my software to build it once by hand, and building it once by hand will change how you read your own sales sheet forever. Something like this comes back:
| Product line | Avg ticket | Avg gross profit | Avg crew-days | GPPCD | Verdict | |---|---|---|---|---|---| | Gutter protection | $6,800 | $4,100 | 1 | $4,100 | PRINTS | | Windows | $14,500 | $6,500 | 2 | $3,250 | THIN | | Sunrooms | $32,000 | $13,000 | 6 | $2,167 | THIN | | Decks (the favor line) | $18,000 | $5,400 | 5 | $1,080 | LOSES |
Every owner who's ever run this table has the same experience: the biggest ticket on the sheet — the line the whole company is proudest of — comes back mid-pack or worse, and some unglamorous one-day product he barely thinks about is quietly out-earning everything in the building, per day, by double. The sales floor ranks products by ticket. The calendar ranks them by GPPCD. They almost never agree, and the calendar is the one telling the truth.
One more thing before your sales manager panics: the lever on a THIN line is usually speed, not price — and I want to run the honest math on the sunroom row, because the two levers land closer than you'd guess and the difference between them isn't the arithmetic. Raise the price ten percent and every dollar of it falls straight to gross — costs don't move — so the row becomes $16,200 over six days: $2,700. Shave the build from six crew-days to five instead — better staging, materials on site before the crew, the inspection booked ahead — and the same job at the same price pays $2,600. Call it a tie on paper. Now look at what each lever costs to pull. The price raise happens outside your walls: a customer who shopped you against two other bids has to say yes to $3,200 more, and some of them won't — you'll buy that $2,700 with close rate, and a lost sale pays zero per crew-day. The day comes off inside your walls: nobody outside the building gets a vote, no customer even notices, and it's repeatable — take the build to four days and you're at $3,250, past anything a price raise was ever going to survive delivering. Days are the denominator, the denominator is yours, and it's the thing your production manager can actually control from his side of the whiteboard.
A-team jobs versus B-crew jobs. I flagged this back in Block One, and here's where it pays off. The production manager answers this question instantly, with specifics, because he lives it every Monday: these jobs anybody can build, these jobs need Dave. Every shop has a Dave.
Now hold the two lists side by side, because there's an invisible price tag on the second one. A product line that requires your best crew has a hidden constraint baked into its economics: it can only be profitable as fast as Dave is available. Sell more of it than Dave can build and one of two things happens — the backlog stretches and your customers cook on the schedule, or a B-crew gets sent to do A-team work and the callbacks start. Either way, the margin your sales sheet promises on that line only exists at a volume nobody's ever calculated. Your best crew is a bottleneck wearing a compliment. The books can't see it — the books think all crew-days are the same crew-days. This question is where the exam finds out otherwise, and it's a finding that changes what "grow that line" even means.
I know this problem from the inside, because at our peak we ran seven crews doing sunrooms — genuinely beautiful work, running Dale's software in the back end. It was called Jester then; the line of thinking behind it eventually grew into One Click Contractor. The kid writing the code was Dale's nephew Chris, still in high school at the time — today he's the CTO of One Click. That's how early we were running this stuff. And before any of that, I was building my own pitch books in CorelDRAW 3 on a 386. I've been putting whatever technology existed to work on this business since the technology barely existed. On that system, we were installing five hundred thousand dollars a month in rooms. That is an operation, I can assure you. And yes, we juggled crews with customers. We knew which customers would be forgiving and which ones would eat a B-crew alive, and we matched accordingly. It was a give and take, every week, and the whiteboard was a chessboard. Sometimes you got so far behind you'd take a chance on a guy off the street. Rarely did that ever work out — a crew is a culture, and you can't hire a culture at the going rate.
So we stopped trying. Our best recruiting mechanism didn't look like recruiting at all: we hired warehouse assistants at the shop. If a man made it thirty days moving material and showed good ethic, we'd ask if he wanted to learn to build something. The answer was usually yes, and he'd move to a crew as an apprentice. Our best crews were home grown, every one of them — raised in our warehouse, trained on our rooms, accountable to our production manager. They were Jason's boys. If your exam turns up a Dave bottleneck, that's the fix, and it takes a year, not a week. There is no shortcut to a crew you'd trust with your worst customer.
Callback rate, honest number. Notice the phrasing. I don't ask for the callback rate; I ask for the honest callback rate, and the word does real work, because every company keeps two of them. There's the official number — warranty claims, formally logged — and there's the real number: every truck roll back to a finished job for any reason. The courtesy trips. The "swing by and look at it" runs. The ones the salesman quietly arranged so the customer wouldn't call the office. The official rate might be two percent. The honest rate might be five times that, and every unlogged trip is a crew-day sliced off some job's margin without ever being charged to it.
Callbacks are margin leaving the building in work boots. A line with a fat stated margin and a fat honest callback rate doesn't have a fat margin — it has a fat gross and a hole in the bucket. This is also the number that settles the worst-line grudge from Block Two: the line the owner hates and the line that actually generates the truck rolls are frequently two different lines. His scar says one thing. The service log says another. We flag both, and the books get the last word, same as always.
What goes wrong most. Permits, engineering, material lead times, inspections, subs — I ask for the top three, and the answer comes fast because the production manager rehearses this list in his head all day. What I'm doing with it is simple: failure modes cost crew-days, and crew-days are the metric. A line that's forever hostage to an engineering review or a permit office or one flaky sub carries schedule risk the sales sheet never priced. Two products with identical margins on paper, where one sails through inspection and one sits three weeks waiting on a stamp, are — again — not the same product. One of them has your money and your crew calendar tied up in a government office lobby. This question puts the top three time-thieves on the record so that when we score the year, we know which lines' bad numbers are the job's fault and which are the process's fault. Different diseases. Different prescriptions. Same diagnostic.
The jobs that tie up the company. The last question in the block is the soft one, and it's deliberately soft: which jobs feel like they consume the whole building, even when the paper says they're fine?
It's the only belief question in Block Four, and I ask it because there's a category of cost no ledger has ever captured: management attention. Every shop has a job type that hits the whiteboard and makes three people sigh. The owner gets pulled in. The production manager babysits it. It generates meetings. On paper it closes at a decent margin, and everybody in the building knows it wasn't worth it, and nobody can prove it, because attention doesn't show up in QuickBooks.
Mine had a name. Marge. The biggest dog I ever built — our first endless pool inside a glass Four Seasons sunroom. Nobody had done one; that was rather the point, and the showcase logic wrote the contract: think what it'll do for the portfolio. I'll tell you what it did for the building: it sat in it for three months. A pool, inside a glass room, with every trade in the book taking a number — and every week it found a new way to need me, my production manager, and my best crew, while jobs we actually made money on waited their turn behind it. We got milked for a quarter of a year and we lost our ass, and here's the part that belongs in this chapter: the paper never looked that bad. The ticket was big. The margin at contract looked respectable. Every dollar of the loss came in through the door the books don't watch — crew-days, attention, and the schedule dragging behind it like a wrecked trailer. Ask the building about a job like that and everybody knows. Ask the books and they shrug.
The reality pair is a proxy — schedule disruption, management touches, how many other jobs slipped while that one was in the building — and I'll be honest with you: it's the roughest number in the whole system. Doesn't matter. Ask the question anyway. Because when the production manager names that job type, and the owner nods before he can stop himself, and then the GPPCD ranking comes back mediocre on a line everybody had been politely tolerating — that's usually all the proof an owner ever needed. He just needed somebody to ask the building instead of the books, and then check the building against the books.
Here's what Block Four really does, and then we'll follow the money into the close.
The lead engine chapter measured what it costs to get the work. This chapter measures what it costs to do the work — in days, in callbacks, in bottleneck crews and permit-office purgatory and management attention. And the reason it takes a whole block of questions is that almost none of those costs live in your accounting system. They live in your production manager. The exam's job is to get them out of his head and into a column, because the gap between what your books think a job costs and what your building knows a job costs is where entire product lines have been lying to their owners for decades.
Your production manager has been holding this testimony for years, waiting to be subpoenaed.
Now — the sales floor and the money. Close rates, financing, deposits, and how fast the cash actually shows up. And a theory of mine about discounts and painful customers that I've been testing at kitchen tables since before some of my readers were born.
WORKSHEET — BLOCK FOUR: The Build Reality
Stop here. Production manager's block. He'll be the most honest person in this whole exam — production always is, because the job site doesn't have feelings either. Full-size sheet at myeasysystem.com/worksheets.
In the room: Production Manager.
17. Typical days-to-build, by product (crew-days — the denominator of the whole book): ______________________________________________
The GPPCD table — by product line, trailing 12 months:
| Product line | Avg ticket | Avg gross profit | Avg crew-days | GPPCD (gross ÷ crew-days) | Verdict | |---|---|---|---|---|---| | ____________ | $ ________ | $ ________ | ______ | $ ________ | PRINTS / THIN / LOSES | | ____________ | $ ________ | $ ________ | ______ | $ ________ | PRINTS / THIN / LOSES | | ____________ | $ ________ | $ ________ | ______ | $ ________ | PRINTS / THIN / LOSES | | ____________ | $ ________ | $ ________ | ______ | $ ________ | PRINTS / THIN / LOSES |
Your break-even floor (monthly nut ÷ crew-days fielded per month): $ ________ /crew-day Your profit target (~$3,500 in most lines): $ ________ /crew-day 18. Which jobs require the A-team vs. can run on a B-crew? ______________________________________________ 19. Callback rate by line — the honest number: ______________________________________________ 20. What goes wrong most on site — permits, engineering, material lead time, inspections, subs? Top three: ______________________________________________ 21. [BELIEF] Which jobs feel like they tie up the company even when they look fine on paper? ______________________________________________
If question 17 came back blank, start tracking crew-days tomorrow morning. It's the one number this book cannot live without.
From The 48 Questions No Marketer Ever Had the Guts to Ask You. Read Chapter One free →