A look at how to systemize a contracting business when the real constraint isn't sales volume. It's the two hundred small decisions between signing a contract and pouring a foundation.
A custom home builder completing around 25 houses a year prices every job on a cost-plus-22 model — actual cost, plus a fixed 22 percent margin on top — which is supposed to protect a builder from surprises. Not this time: a stone veneer quote listed the material only as "cultured stone," with no type and no square footage attached, and by the time the actual product and quantity were locked in, the price had moved $12,000 past what the job was sold for. There was nothing in the file to push that difference back to the client, so the company absorbed it.
That $12,000 miss was part of a bigger pattern. Client communication and scope documentation had never been formally systemized, and it showed up everywhere at once: in how superintendents wrote weekly updates, in how estimates got worded, in how subcontractors handled a client's material picks.
The builder's own diagnosis was blunt. Across the company, "we can improve our communication." Two problems kept surfacing.
Superintendents answered client emails and texts after hours. That trained homeowners to expect round-the-clock availability, and it burned the team out. The weekly update itself had no standard either. At one point, updates ran 2 or 3 pages of repetitive detail. The correction overshot hard, into updates so short they told a homeowner almost nothing.
Both versions technically counted as "we sent an update." Neither one built trust. Neither one moved a decision forward.
Both problems came from the same root cause: nobody had defined what a weekly update was for. A superintendent juggling four jobs doesn't lack the information a client needs; he has it, he just doesn't have a system that pulls it out of his head and onto the page in a consistent, useful shape (the same instinct that makes a good superintendent good at his job is part of what makes him bad at writing about it). Ask him directly whether a client needs to approve cabinet hardware in 3 weeks, and he'll usually answer immediately. So why does that same fact disappear the moment he sits down to type a weekly recap from memory? Nothing in the process required him to check the schedule first.
The fix started with a single prompt. It was built during a working call with the builder's advisor and tested live against a real job's schedule, pulled straight from the project management software. The instructions were specific: a superintendent for a custom home builder writes a weekly update stating what progress was made, what's coming next, which client decisions are required and by what date, and what happens to the schedule if those decisions slip.
Three to five bullet points on the week just finished, three to five, not two pages. Two to four bullet points on the week ahead. Plain language. No construction jargon unless it's necessary.
The part that turned a template into a real SOP was feeding the schedule into it. A Gantt chart already existed for every job, tracking things like a cabinet delivery locked for a specific date weeks out. Read correctly, that single date implies a whole chain of earlier deadlines.
Cabinets delivering in a set window means hardware needs approval well before that. A slip there pushes trim and paint too, because those crews are already booked on other jobs.
A superintendent thinking a week ahead misses that chain every time. A prompt that reads the schedule first and works backward from it does not.
The builder didn't need convincing on the underlying philosophy. He was already living it with his clients. His own description of the job was blunt:
"You are the conductor, you're driving the bus. You help them when they stumble getting on the bus. If they drop their hat, you pick it up and hand it back to them. But they're not driving the bus."
That's the same logic behind the update process itself. Most homeowners have never touched the company's project management software before, and they don't know what a good weekly update looks like until somebody shows them one.
Setting that expectation early, in writing, at the start of the project, is what lets a builder point back later and say: we told you exactly how this would work, from the start.
The prompt was only half of it. Stuart Trier, Clear Results' founder and CEO, framed what the AI was for in a way that mattered just as much:
"If we were playing basketball, AI would give me a 45-inch vertical. If you think of AI as the shoes, I put the shoes on, all of a sudden I can jump 45 inches. It just makes you more powerful at what you're good at."
The system doesn't replace 30 years of construction judgment. It takes a schedule that already exists and a decision sequence the builder already knows cold. Brick first, for the foundation. Then doors and windows, then shingle color, then cabinets.
Then it turns both into a document a superintendent can knock out in minutes, not an evening
The $12,000 stone overage and the communication breakdown come from the same place. Nobody forced a specific, checkable detail into the record before the job started.
"Cultured stone" is a category name. Dozens of products fall under it, at very different prices per square foot.
Once the real product and square footage were confirmed, the price moved. The company absorbed the difference on a job it had already sold.
The company's own correction was already underway before this conversation. It's a clean example of what job costing for contractors requires in practice: fixed per-unit allowances rather than a single lump-sum vendor number.
The builder had started requiring tile pricing broken down by exact application. A mosaic floor tile in a shower, priced separately from wall tile, backsplash, and flooring, each at its own rate per square foot. That same discipline was missing on the stone job. That's exactly why it bled.
A related exposure showed up from an entirely different angle. The builder's own tile subcontractor, on a personal renovation project unrelated to any client job, installed roughly $6,000 worth of upgraded tile that an interior designer had selected, without first flagging the price difference.
It costs the builder directly. It's what pushed him to set a company-wide rule: if a sub sees a client's designer picking something that blows past the budgeted allowance, the sub calls first.
Left unchecked, that same exposure plays out on client jobs at a much larger scale. What happens when a superintendent tells a client the tile budget is $5,000, and the client's designer picks $18,000 worth of tile anyway? The subcontractor installs it without a word to anyone, and the company eats the spread.
Unbilled change orders and undocumented upcharges are among the most common ways a profitable-looking job quietly loses money. They stay invisible unless someone is tracking cost job by job, not in aggregate.
The answer isn't more oversight on every job. It's the same allowance-and-approval discipline the builder was already building for tile, applied everywhere a vague material description could turn into a five-figure surprise.
None of this is specific to custom home building. Swap the trade and the material changes; the failure pattern doesn't.
Same principle, different material. The trade changes, but the failure pattern doesn't.
This article is based on a real advisory conversation between Clear Results and a client. Details about the business and the people involved have been generalized throughout to protect confidentiality.
1) Is Clear Results a home service business coaching program? No. Clear Results runs strategic advisory sessions and coaching calls as part of how it works with clients, but it isn't built as a coaching company. The model is hands-on: installing and operating actual systems inside a business (schedules, scopes, weekly communication, job costing), not advising from the outside and leaving execution to the owner. The full framework is on the Operating System page, which covers all five systems Clear Results installs, including the Operations Engine and Profit Engine covered in this piece.
2) How do unbilled change orders and undocumented upcharges erode margin on a cost-plus job? Even on a cost-plus contract, a vague scope description leaves nothing to bill back to the client, so the builder eats the difference between what was quoted and what got installed. That's exactly what happened with the $12,000 stone quote in this piece. Fixing it means putting exact material types, square footage, and per-unit allowances on every estimate before it goes out, not after the fact. The Profit Leakage playbook breaks down four other places where margin disappears in the same invisible way.
3) What should a weekly client update for a custom home build include? A useful update covers 3 things and nothing more: 3 to 5 bullet points on what happened that week, 2 to 4 bullet points on what's scheduled next, and a clear list of client decisions required with real deadlines pulled from the actual construction schedule, not vague "soon" language. The goal is a document a superintendent can produce in minutes by reading the schedule first, not one assembled from memory. The Weekly Operating Rhythm playbook covers how to build that cadence company-wide.
4) How do you stop clients from expecting after-hours availability from field staff? Set the expectation in writing before the project starts, not after someone answers a 9 p.m. text and trains the client to expect it every time. Define exactly when staff are reachable, what counts as urgent, and how non-urgent questions get logged and answered on schedule. Once that expectation exists on paper, a builder can point back to it the first time a client pushes past it. The Accountability Without Micromanaging playbook covers the same principle applied to internal team expectations.
5) What is job costing for contractors, and how is it different from estimating? Estimating is the number quoted before a job starts. Job costing is tracking what a job actually costs while it's underway and after it closes, broken down by exact materials, quantities, and applications rather than a single lumped supplier number. A builder pricing tile at a separate rate for the shower floor, wall tile, and backsplash is job costing. A builder accepting "$5,000 for tile" and hoping it holds is only making an estimate. The Job Costing for Contractors playbook walks through installing the system end-to-end.
6) Should a custom home builder hire an in-house interior designer? Run the comparison before deciding either way. An outside designer typically costs a builder's clients around $10,000 per house; across 25 houses a year, that's $250,000 moving through outside firms annually. An in-house designer's salary runs closer to $40,000 to $50,000, which can pencil out once volume is high enough. What tends to decide it in practice is how much smoother client decisions go once someone with a design eye is involved from the start, not the salary line alone. The Pricing for Real Margin playbook covers how design-driven change orders affect job margin.
Every builder has a version of this $12,000 mistake sitting somewhere in a scope of work right now. Take the free diagnostic to find the constraint costing the most, or read the full Weekly Operating Rhythm, Profit Leakage, and Job Costing for Contractors playbooks for the systems behind this story.
Stuart Trier is the Founder and CEO of Clear Results. Over the past 20 years, Stuart has built, bought, and sold 11 companies across the home service, healthcare, and marketing industries. He built his first company from startup to $8M in revenue in 3 years before a successful exit, then built a chain of 28 healthcare clinics and sold the business to a publicly traded company. Following that acquisition, Stuart spent 3 years working alongside the CEO, helping lead the organization through a take-private transaction before participating in a nine-figure exit to a Fortune 10 company. Today, he's the lead investor behind an electrical services platform operating across 3 U.S. states, and has worked directly with owners through 1,800+ strategic advisory sessions.
