How to Increase Your Construction Company's Profit Margin Without Cutting Quality

If you want to increase your construction company's profit margin, you've probably already gone through the exercise every owner does at year-end: you sit down with the accountant, look at the results of three delivered projects, and discover that the margin that closed on paper isn't the margin that's left in the cash account. The project "went well" — it was delivered, the client was satisfied, nobody broke down. And yet the profit came in lower than the budget promised. Same feeling every year: I worked the same, I billed the same, and less was left over.

Then comes the natural reflex, and it's almost always wrong: cut. Switch to a cheaper supplier, squeeze the subcontractor, trim a support crew, spec a lower-grade material. You touch quality to defend the margin — and on the next project, rework and client complaints eat back what you "saved."

I spent my career inside industrial pulp and paper projects — multi-billion-real developments — for Suzano, Klabin, and others. And I learned something that applies just as much to a giant factory as it does to your R$ 30 million building: the margin rarely leaks through the cost you can see. It leaks through the losses nobody measures. Cutting quality attacks visible cost — the cost that's already in the budget and that you've already negotiated down to the bone. The invisible losses are somewhere else, bleeding every day, and they don't show up in any report. That's what we're going after in this article.

Why the construction company's margin tightens every year

The margin tightens under a squeeze that comes from outside and inside at the same time, and neither one is fully within your control.

From outside: the selling price has a ceiling. The client compares, financing limits it, the competitor covers it. You can't pass the real cost through to the price with the freedom you'd like. On the cost side, cement goes up, steel swings, the good engineer's salary rises, and the construction cost index doesn't ask permission. The gap between what you charge and what you spend keeps closing, year after year, without you having done anything wrong.

Inside is where the problem you can attack lives — and it's the part almost nobody sees. Most of a project's loss isn't one big, visible overrun. It's the sum of small, daily losses that vanish somewhere in the accounting. Waste, in fact, is recognized as the industry's number-one problem: market surveys point to something around 73% of the construction industry seeing waste as its main pain point. It's not a lack of work. It's work turning into loss along the way.

The cruel detail is that these losses don't have their own line item in your report. The emergency purchase disappears inside "materials." The idle crew disappears inside "labor." The rework disappears inside "unforeseen events." You see the smaller margin at the end, but you can't point to where it went — because the project report records what happened, not what leaked. And what you don't measure, you can't cut.

Cutting cost vs. stopping the bleeding (the difference)

Here is the distinction that changes the entire strategy, and I want it to stick: cutting cost and stopping money from leaking are different things — and the second one is where the margin you're looking for actually is.

Cutting cost means touching what's already in the budget. It's visible, planned, contracted cost. You switch the finish brand, renegotiate the subcontractor, pull someone off the crew. It has a clear limit (you've already bought well, already negotiated hard), and it has a cost: it almost always costs quality, schedule, or people. Cutting hurts at the right time — but it's a shallow well, and after two projects you've already scraped the bottom.

Stopping the bleeding is different. It's stanching what leaves the project without ever having entered the budget as a planned cost. The purchase that came out more expensive because it was made in a panic. Your engineer's hours — an expensive professional — spent hunting for information instead of running the site. The wall that went up at the wrong elevation because the right drawing was sitting in someone's inbox. None of that is "cost" in the sense you planned for. It's a leak. And unlike cutting, stanching a leak doesn't cost any quality — quite the opposite, quality usually improves right alongside it, because most leaks are born from disorganization, not from high standards.

That's why the answer to "how do I increase margin without cutting quality" isn't on the cost side. It's on the loss side. The right question isn't "where do I cut?" It's "where is the margin leaking that I'm not measuring?" And leaks have three main addresses.

The 3 levers: capacity, purchasing, and rework

When we map out where a project's margin escapes, it always concentrates in three blocks. They're not the only ones, but they're the ones that bleed the most and the ones you can most attack. In order of size:

1. Capacity — the expensive professional doing a robot's job. This is the biggest one, and the most invisible of all. Your engineer, your coordinator, your architect — expensive people — spend a good part of the day asking "what's the status?", looking for the latest version of a document, typing in invoices, putting together a report at night. It's technical capacity locked up in administrative work. You pay an engineer's salary to get engineering, and what you get back is a lot of hours of robot work. Every one of those hours is margin evaporating without showing up anywhere — because the salary is right there in the budget, you just don't know how much of it is being wasted.

2. Purchasing — the margin that leaks in a panic. Materials are 40% to 60% of a project's budget. It's the biggest cost line, and the one that reacts most to disorganization. A construction company without a structured purchasing flow loses in two ways: buying at the last minute — the emergency purchase that comes out, on average, 28% more expensive than it would with planning — and not negotiating systematically, buying from the usual supplier instead of quoting three. It's no coincidence that surveys point to around 88% of project delays being linked to material and supply problems. Every panic purchase is margin walking out the door on a line nobody measures in isolation. I detailed the mechanism in Reducing construction costs: where a project's margin really leaks.

3. Rework — redoing what was already paid for. The wall at the wrong elevation, the installation that clashed with the structure, the finish executed to the old spec. Redoing something means paying twice for the same thing: material again, hours again, lost schedule. And rework almost always comes from the same root — wrong or outdated information arriving on-site at the wrong time. It's an avoidable leak, and I wrote about its cost in Rework in construction: how much it costs and how to reduce it on your project.

Notice what the three levers have in common. None of them is "the team is bad" or "the standard is too high." All three are born from the same enemy: trapped information — in someone's WhatsApp, in the email nobody found, in the head of someone who left, in the spreadsheet nobody updated. When information doesn't flow at the right time, the purchase becomes an emergency, the engineer's hour becomes a search, and execution becomes rework. Attack trapped information and you move all three levers at once — without touching a single cent of quality.

The 3.6%–7.6% of project value model (our estimate)

Let's put a number on this, with an honesty I want to make clear before any of the math.

When we add up the three levers — locked-up capacity, panic purchasing, and avoidable rework — it comes to a recovery on the order of 3.6% to 7.6% of the project's value. On a reference R$ 8 million project, that's something between R$ 291,000 and R$ 605,000 currently going down the drain without showing up in any report. To give you a sense of the scale of the capacity block: in our model, it's equivalent to almost 2 people on the team — professionals you already pay and who work today, for a good part of their time, like administrative-task robots. The purchasing block alone — anti-emergency plus systematic negotiation — is worth on the order of R$ 90,000 to 180,000 per project at that reference size.

Now the honesty, which is worth more than the number: 3.6% to 7.6% is our estimation model — bottom-up, deliberately conservative — not a result measured on a client. Our pilot is less than a month old; it exists precisely to turn this model into a case study with a measured number. I'd rather tell you that to your face than sell you a percentage I haven't proven yet. What I'll stake my reputation on today is one piece of that model: our Communication Hub gives back 10 hours a week to every project manager — more than a full business day, every week, of qualified people going back to running the project instead of chasing information. That one is measured. The rest of the percentage is model — good, defensible, but model.

Why does this matter for the margin decision? Because it changes the comparison ruler. You're not evaluating "one more expense." You're evaluating recovering several percentage points of a project against a cost that represents about 1% of it. If you want to see this laid out as return on investment, with a full simulation, I wrote the step-by-step in Is construction management software worth it? How to calculate ROI. The logic is the same one I used in industry: you don't evaluate an investment by price, you evaluate it by return.

Where to start on your next project

You don't need us — or any software at all — to take the first step. You need to stop managing margin only by visible cost and start measuring the leak. On the next project you open, do three things:

1. Measure emergency purchases. One line per event: what, how much extra you paid, why. In three months you'll have the exact map of where the project bleeds on purchasing — and you'll almost always discover that most of the emergencies come from the same few items, the ones that were predictable.

2. Measure the technical hours spent on robot work. Ask your engineer, honestly, how many hours a week they spend chasing status updates, looking for documents, typing in invoices, and building reports. Multiply by their hourly cost. That's the size of your locked-up capacity — and it tends to be the number that scares people the most.

3. Log the rework. Every time something gets redone because of wrong or outdated information, write it down. Estimate the cost. On a single project, you'll already see the pattern.

This works, and it costs nothing but discipline. The honest problem is: it depends on disciplined people doing this logging in the middle of the chaos — in the middle of 15 WhatsApp groups, with the engineer putting out fires. It's the first routine that falls apart when things get tight. That's why manual measurement shows the size of the leak but doesn't stanch it by itself. To actually stanch it, the cross-referencing of information — schedule against stock, decision against execution, question against answer — needs to happen on its own, at the right time, without depending on anyone remembering. That's where active coordination comes in.

Frequently asked questions

1. Is increasing margin without cutting quality realistic? Isn't that just a nice pitch? It's the only sustainable path, and it's not a pitch. Cutting quality defends the margin once and sends the bill on the next project, in the form of rework and complaints. Stanching leaks — panic purchases, wasted technical hours, rework from wrong information — recovers margin without touching the standard, because those leaks aren't a high standard, they're disorganization. You're not going to lower the spec; you're going to stop paying twice for the same wall and stop buying cement 28% more expensive on a Friday afternoon.

2. I already have an ERP (Sienge/TOTVS). Doesn't it show me the margin? It shows you the margin after it has already leaked. The ERP records what happened — invoice entry, balance, measurement, budgeted against actual. It's a good system of record, and you should keep it. But it's passive: it doesn't cross-reference the stock balance with the schedule to warn you before the rupture, doesn't chase the daily standup, doesn't trigger the quote request. The margin leaks in the gap between the event and the record. Active coordination works in that gap. That's why we integrate with the ERP, we don't replace it.

3. My field team isn't going to use yet another system. Then I won't recover anything. That's the right objection, and the answer determines the outcome. A system that depends on the team filling out forms becomes shelfware — and shelfware doesn't stanch any leak. That's why the right model is an agent that asks instead of waiting to be filled in, that reads the invoice on its own, that accepts voice answers and works on a site phone, with a QR code. And that's why we come in with engineers during onboarding: without a method, the best tool in the world doesn't recover a single real. Adoption isn't luck, it's design.

4. Isn't R$ 10,000 a month to "recover margin" expensive? Compare it to what you're already paying for, not to zero. R$ 10,000 a month is roughly half a mid-level engineer's salary — except this "half engineer" works 24 hours a day, on every front, never forgets to cross-reference schedule against stock, and follows up with everyone without fail. It's about 1% of the project to go after the 3.6% to 7.6% leaking today. A single avoided emergency purchase per month, at the average 28% markup, already covers a good chunk of the bill.

5. Do you have a case proving this margin gain? I'm not going to sell you something I haven't measured on a client yet — our pilot is less than a month old. What I'll stake my reputation on is the time the Communication Hub gives back to every project manager; that's our own measurement. The 3.6% to 7.6% figure is a conservative model, and the pilot exists to turn it into a case study with a baseline at entry. The purchasing math, though — you can check that against your own data before signing anything. You decide with a number in hand, not with a promise.

How TrackBuild attacks the margin leak in practice

Everything this article described — technical hours locked up in robot work, the purchase that comes out expensive in a panic, rework from wrong information — is born from the same root, trapped information, and that's exactly what TrackBuild was built to attack. Not with one more report for you to look at, but with coordination that acts:

• AI Communication Hub (the project's living memory) — answers any question about the project instantly, with the source, instead of sending the engineer off to hunt for information. This is where the technical capacity given back to every project manager comes from — the time that goes back to running the project instead of chasing information. Attacks lever 1.
• Schedule-linked purchase alerts + Buyer Bot — the system cross-references each phase's projected consumption with the actual balance and the supplier's lead time, and warns you before the rupture, with enough time to calmly quote three suppliers. The emergency dies at the source. Attacks lever 2.
• Real-time budgeted vs. actual — the margin stops showing up only at closing with the accountant. You see the deviation while there's still time to act, not months later, when the money's already gone.
• Engineers in onboarding — software the team routes around doesn't recover any margin. Rollout comes with method and engineering people, so the routine becomes mandatory in the system and is designed together with your team.

And because pricing is per module, with unlimited users, you bring the entire project in — the general contractor, the subcontractor, procurement, the sub-subcontractor — with no per-seat toll. That's what lets information flow between everyone, and it's information flowing that stanches all three levers at once.

Find out where your project's margin is leaking

You won't recover margin you can't measure. And the example in this article uses market averages — your project has its own numbers, and those are the ones that decide.

The Leak Diagnostic is a free 30-minute call where we build, using your own data, the math on the three levers for your project: how much you're losing in panic purchases, locked-up technical hours, and rework — and how much of that can be recovered without touching quality. You leave the conversation with a number in hand, no strings attached.

Talk to us

---

Felipe Barreto is co-founder of engineering at TrackBuild. A civil engineer with a master's degree in civil engineering from UFMG, an MBA from IESE Business School, and a PMP certification, he managed factory construction for Suzano, Klabin, and other pulp and paper industry leaders — multi-billion-real developments. TrackBuild puts AI agents and specialized engineers into the project's daily routine, with unlimited users, so information stops getting trapped and margin stops leaking.