Cost reduction in construction: where your project's margin is really leaking

When a construction company owner asks me about cost reduction in construction, the conversation almost always starts in the wrong place: the month's blowup. The concrete pour that went over budget, the subcontractor's change order, the steel invoice that came in higher than expected. Big, visible things that hurt immediately and become a topic at the board meeting.

But let me tell you what I learned after years inside job sites: the blowup you see is almost never what costs you the most. What costs you the most is what disappears inside the numbers — the small, daily loss that has no line item of its own in the report, and that's exactly why nobody ever adds it up.

I spent my career on industrial pulp and paper projects — developments in the billions of reais — for Suzano, Klabin, and others. And the same logic applies to a plant like that and to your R$ 8 million building: margin is rarely destroyed by one blow. It leaks — drop by drop, every week, in a line the system records as "materials" or "labor" and never isolates. In this article I'll show you where your construction company's margin is leaking, how to measure what's invisible today, and what you can stop — some of it without spending a dollar on software.

The blowup you see × the loss you don't

There's a cruel asymmetry on job sites. The blowup is loud: it busts a budget line, shows up red in the report, and everyone scrambles. Because it's loud, it gets managed — you negotiate, approve, or cut. It hurts, but you deal with it.

The invisible loss is the opposite. It's silent and doesn't blow anything up, because it fits inside what was budgeted. The purchase that cost 28% more because it was made in a panic gets recorded as "materials" — and the materials budget had slack, so no alarm goes off. The team's idle hours waiting on a decision stuck in a WhatsApp thread get recorded as "labor," and payroll closes the same as always at month's end. The rework on the wall built to the wrong elevation gets recorded as... nothing. It just vanishes.

That's why cost reduction in construction that actually delivers results doesn't start by cutting what you see. It starts by seeing what you don't. And the whole industry lives with this: market surveys point to waste as construction's number-one problem — roughly 73% of companies rank it at the top of the list. It's not a problem specific to your site; it's structural in how construction is managed. The ones who stop the leak are the ones who learned to measure the invisible loss.

The 3 places where margin leaks: team, procurement, and rework

After mapping job sites from the inside, invisible loss concentrates in three areas. This isn't mysticism — it's where the money actually escapes on a mid-size construction company.

1. Team: the expensive professional doing a robot's job. This is the biggest one, and the most poorly understood. Your engineer is the most expensive person on the site — and spends a good chunk of the day asking "what's the status?", hunting for the latest version of a drawing, putting together a report at night. That's not managing a job — it's administrative work eating up the technical capacity you pay dearly to have. Every hour he spends chasing information is an hour he's not spending anticipating a problem — and the problem he doesn't anticipate turns into, guess what, a visible blowup down the road. It's a leak that costs you twice. I go deeper on this in Productivity on the job site: what does it cost you to have your engineer chasing information instead of running the project.

2. Procurement: margin lost to panic buying. Materials are 40% to 60% of a project's budget — the biggest line item there is, and the most sensitive to disorganization. When the schedule and supply chain aren't in sync, materials end up behind the stage that consumes them, and you buy at the last minute: without quotes, with rush freight, from whichever supplier has stock instead of the ideal one. The average markup on that emergency purchase is around +28%, and it disappears inside "materials" because nobody measures it separately. It's no coincidence that the market reports close to 88% of project delays are linked to material and supply issues. I wrote out the full math on this in What an emergency purchase on a construction site really costs.

3. Rework: redoing what was already done. The wall built to the wrong elevation, the installation done from an outdated version of the project, the stage signed off without review that has to be redone. Rework is expensive because you pay twice for the same thing — materials, labor, and time — and it still pushes the schedule back. And the root cause is almost never technical: it's wrong information reaching the right person, or the right information arriving too late.

Notice the thread running through all three: none of them is a competence failure on your team's part. They're all symptoms of the same disease — information stuck in place. In someone's WhatsApp, in an email nobody opened, in the head of someone who's on vacation. The enemy of your margin isn't your team; it's information that doesn't flow.

How to measure what's invisible today

Here's the uncomfortable part: you can't reduce what you don't measure, and these leaks are invisible in your current controls. The first step of any serious reduction effort is putting a name and a number on each loss — and you can start today, by hand, with what you already have.

• Panic purchases: flag the orders from the last few months that went out as "urgent," add up the value, and apply a 28% markup to that slice. That's, with good approximation, your procurement leak.
• Locked-up capacity: ask your engineers how many hours a week they spend chasing status updates, hunting for files, and putting together reports; multiply by hourly cost and number of projects. This is usually the biggest shock in the tally.
• Rework: list, from the past year, how many times something had to be redone because of wrong information and estimate the cost. Even a rough estimate gives you the order of magnitude.

Add up all three. On most construction companies running projects above R$ 8 million, the total is startling — because it's the first time these numbers appear together, out from behind the disguise of "materials" and "labor."

To give a sense of scale: in our estimation model — a conservative, bottom-up calculation built on an R$ 8 million reference project, not a measured result from a client — the sum of the three leak categories represents on the order of 3.6% to 7.6% of the project's value. On an R$ 8 million project, that's somewhere between R$ 291,000 and R$ 605,000 going down the drain. That's roughly the equivalent of getting back nearly two full team members who today work like robots. I'll repeat, because this is the house rule: it's a model, not a measured case — our pilot is less than a month old. The number that actually matters is your project's, with your own numbers.

What you can stop without software

Before any conversation about technology, it's worth saying plainly: part of this leak you stop with discipline, and no software saves anyone who has no process. To start reducing costs on your next project, start here — for free:

Make the procurement workflow mandatory. No purchase above a threshold X goes out without three quotes. No exceptions — because the exception is exactly the hole margin leaks through. An emergency doesn't justify skipping the quote; the quote is what prevents the emergency.

Tie consumption to the schedule, every week. On Mondays, every crew answers: what does this stage consume over the next two weeks, and how much is already on site? And for every critical material, set the purchase lead time (supplier lead time plus buffer) — if the stage starts in X days and the lead time is Y, the order goes out in X minus Y days. Write it down, don't rely on memory.

Standardize project information. One valid version per document, in one place, that everyone knows is the one. Half of all rework dies the moment a crew stops building from the wrong drawing.

This works — it genuinely reduces the leak. But the limit is an honest one: all of it depends on disciplined people doing manual math, every week, amid 15 WhatsApp groups and an engineer firefighting — it's the first routine to fall apart when the project gets tight. Process reduces the leak, but doesn't eliminate it: to truly stop it, the cross-check — schedule × inventory, decision × crew, data × the right person — needs to happen on its own.

Where active coordination comes in

This is where most tools miss the mark. They hand you one more place to look at: a nice dashboard with the project's cost, updated — and completely passive. It shows you the leak after it happened and waits for you to look. Except you're not going to check on Tuesday night to find out the mortar runs out Thursday. That's why our thesis is simple: your project doesn't need one more dashboard to record the loss. It needs active coordination to prevent the loss.

Active coordination is the difference between a system that archives and one that acts: instead of showing inventory after the shortage, it cross-checks consumption, balance, and supplier lead time and warns you beforehand — the emergency purchase dies at the source, becomes a planned order with time to get quotes. Instead of waiting for the engineer to ask "what's the status?", it pings the crew and consolidates the answer. And instead of just storing the drawing, it guarantees one valid version for whoever's executing — and rework from the wrong version disappears.

Information stops getting stuck — and when it flows at the right time, the three leaks stop being inevitable. It's not AI magic or a dashboard promise: it's information arriving before it turns into cost.

Frequently asked questions

1. Isn't cost reduction just a synonym for cutting quality and squeezing suppliers? It's the opposite of what I'm arguing here. Squeezing suppliers and lowering standards attacks visible cost and often generates more rework down the line — you save on materials and pay on redoing the work. Stopping the leak is different: it's about no longer losing money that was already yours, in panic purchases, a locked-up team, and rework, without touching quality.

2. I already have Sienge/TOTVS. Doesn't my ERP show me the costs? It shows you what already happened — invoice entries, balances, measurements. It's a great record, and you should keep it. But it's passive: it doesn't cross-check the balance against the schedule to warn you before a shortage, nor does it chase down the crew that didn't respond — it waits for you to check. Active coordination acts on what's happening; that's why we integrate with the ERP, not replace it.

3. How much can I actually recover? It depends on your project — and that's the honest answer. Our conservative model points to roughly 3.6% to 7.6% of the project's value across the three categories, but I want to stress: it's a model estimate, not a measured client result. What you can pin down today is the procurement math (the 28% markup on the slice bought under panic), which you can verify yourself with your own data. The exact number is your project's, and that's what our diagnosis calculates.

4. Isn't R$ 10,000 a month on a system just one more cost in a year of tight margins? It only looks like a cost when you compare it to zero — and your informal management isn't free, its cost is just spread out and invisible. A single avoided emergency purchase already covers a good chunk of the month: it's about half the salary of a mid-level engineer for a manager who works across every crew nonstop — close to 1% of the project's value to recover the percentage points leaking today. The full return math is detailed in How to increase your construction company's profit margin without cutting quality.

5. My field crew won't follow one more process. It'll just become window dressing. Fair objection, and the honest answer is: if the process depends on the crew filling out forms and remembering everything, it will fall apart too. That's why the key is having the agent ask instead of waiting for someone to fill something out, accept answers by voice, and work on the job-site phone — and that's why we bring engineers into onboarding. A tool the crew works around doesn't stop any leak. Adoption isn't luck, it's design.

How TrackBuild attacks margin leakage in practice

Everything this article described — the loss that vanishes inside the numbers, the panic purchase, the engineer chasing information, the rework from the wrong version — is exactly what TrackBuild was built to attack: not with one more dashboard, but with active coordination over the three areas where margin leaks:

• Budgeted × actual in real time — the invisible loss stops being invisible: every line shows up with its own name, and the deviation lights up before it becomes a blowup, not after the month closes.
• Procurement alert tied to the schedule — the system cross-checks consumption, balance, and supplier lead time and warns you before the shortage; the emergency purchase becomes a planned order, with time to get three quotes.
• AI Communication Hub — the project's living memory answers any question with its source, with nobody having to chase information; this is where the 10 hours a week given back to every project manager come from — the expensive professional goes back to running the project.
• Engineers in onboarding — software the team works around doesn't save a dollar; rollout comes with method and engineering people, so the workflow becomes real job-site routine.

And because pricing is per module, with unlimited users, the construction company, the subcontractor, and procurement all work in the same flow, with no per-seat toll and no information stuck in someone's WhatsApp — which is where the margin starts to leak.

Find out where your project is leaking before you decide anything

You can't cut what you can't see. The first step of cost reduction in construction isn't squeezing a supplier — it's putting a number on the loss that today disappears inside the numbers. And that number is yours, not the example's.

The Leak Diagnosis is a free 30-minute call where we build, using your own data, the calculation of your project's three leak categories — capacity, procurement, and rework. No commitment. You decide with the number in hand.

Talk to us

---

Felipe Barreto is co-founder of engineering at TrackBuild. A civil engineer with a master's in civil engineering from UFMG, an MBA from IESE Business School, and a PMP certification, he managed the construction of plants for Suzano, Klabin, and other pulp and paper industry leaders — developments in the billions of reais. TrackBuild puts AI agents and specialized engineers into the day-to-day of the job site, with unlimited users, so information stops getting stuck and margin stops leaking.