By Greg Allan, tradesman and creator of Data First Coaching
Why does a week full of small carpentry jobs still feel busy but barely pay?
Most carpenters running between small jobs feel flat out by Friday and still cannot work out where the money went. A morning fixing a door, an afternoon hanging skirting on a renovation, a quick patch on a pergola before heading to the next site, every hour looks full on the job sheet. The bank account tells a different story.
The reason is rarely the price charged. It is that a trade business usually measures how busy the crew was by hours billed on site, not the hours actually paid out for the day including the drive. A half day fix-out and a full day framing job can carry almost the same travel, so the small job absorbs a cost that never shows up anywhere on the invoice.
Why doesn't the drive between jobs ever get counted as a cost?
It doesn't get counted because the clock most carpenters watch starts when the nail gun comes out, not when the ute leaves the yard. A small reno job, an hour hanging an architrave, a quick door hanging fix, can carry a half hour drive out and another drive back, and none of that ever lands against the job.
Operational efficiency only tells the truth when it runs from the moment the carpenter drives out to the moment they drive back in, not from the moment the tools come out. Two small jobs with travel wedged between them can eat most of a morning before a single architrave is cut, and that time still has to be paid for even though it was never billed.
Can a job get invoiced as normal and still be running at a loss?
Yes, and this is exactly where small jobs hide the gap. The job gets finished, the client pays, the invoice looks clean. But if the real time on site, travel included, was never set against what was allowed for the job when it was quoted, the job can still be running at a loss while every record says it was done properly.
Picture a carpenter juggling a fix-out, a deck repair and a small reno job across one day. He tries to work out his true cost of operations by pulling his wages and overheads together. The first number comes out far too high, as if every hour paid was also an hour billed. Strip out the office time and the driving between jobs and the number swings the other way, suddenly too low to cover what it actually costs to run the business for a day. Neither number is any use for pricing a quote, because neither one reflects what a day of scattered small jobs genuinely costs once travel is counted properly.
What number actually tells a carpenter the truth about small jobs?
The number that matters is the true cost of operations, measured against gross profit margin on each job, not a one-off figure checked at tax time. For a carpenter, that means knowing what an hour of paid time genuinely costs once wages, travel and overheads are included, and checking every quote against it before the job is booked, not after it is invoiced.
This is data first thinking. Instead of guessing from memory how a small job usually goes, the carpenter's own numbers, pulled from real jobs run this month, not last year, show where the gap between billed hours and paid hours actually sits. A builder paying day rate to a subcontract carpenter faces the same problem from the other side, so the same logic applies whether the work is priced as a fixed quote or a day rate.
How can AI agents help carpenters stop travel from eating small job profit?
An AI agent is software that does a job the way the carpenter would do it themselves, using their own prices, their own wording and their own rules. For small job costing, that means an agent can sit between the quote and the job, pulling real wages and overhead data to work out the true cost of operations before the job is booked, rather than leaving it to be discovered after the invoice is sent.
Once that number is set, the overhead and non-billable cost, including travel, can sit in its own bucket instead of being spread thinly and invisibly across every job on the board. An AI agent built on the carpenter's own data keeps that costing current as wages and hardware prices move, so the carpenter is pricing a fix-out, a deck repair or a lock-up stage framing job against a number that actually reflects the drive, not a guess made once and forgotten.
How does Data First Coaching approach this?
Data First Coaching, built by Greg Allan, starts with the carpenter's own numbers rather than a conversation about pricing. Through the Trade Business Intelligence, it looks first at the gap between hours billed on site and hours actually paid across a week of small jobs, because that gap, not the quoted price, is usually where the real loss starts.
As Greg puts it, “the job still gets done, you still charge the money, so you think you're doing okay.” Finding where that assumption breaks down for a particular carpenter's run of small jobs is worked through inside the Academy, with other members, because the Trade Business Intelligence is powered by every member who is open minded, innovative and willing to share what their own numbers show.
Looking for a business coach who starts from your numbers? Carpenter Business Coach or every answer for carpenters.
