Managing contractors and subcontractors: how to put everyone on the same job site without paying per user

Contractor and subcontractor management almost always breaks at the same point: Monday morning, the window and door installer shows up with the crew ready and finds out on site that the opening's dimensions changed last week. The change was real, it was decided, it was communicated — it just stayed in the construction company's WhatsApp group, where the contractor wasn't a member. Result: a crew standing idle, a lost day, and a "who was supposed to tell who" argument nobody wins.

Nobody logs this as a loss — it becomes "windows fell behind" in the report. But it was a loss: the subcontractor billed for the idle day, your finishing crew slipped right along with it, and the relationship with a good contractor soured over an error that wasn't technical. It was informational.

I spent my career inside pulp and paper industrial projects — developments in the billions of reais, where on a single critical work front five or six companies work at the same time: civil, assembly, electrical, piping, insulation. And I learned something that applies just as much to a Suzano plant as to your R$30 million building: the problem with a job site that has many subcontractors is never the number of companies; it's that information doesn't circulate between them. Your job site doesn't have a contractor problem; it has a coordination problem.

In this article I want to show why contractor management breaks down, why the way most systems charge makes exactly this problem worse, and how to put everyone — construction company, developer, contractor, and subcontractor — inside the same job site, with the status of every work front arriving on its own and the record protecting both sides.

The job site with four companies inside (and none of them talking)

It's worth stopping to look at how many companies actually touch your job site at the same time.

There's the construction company — you, coordinating. Often the developer above you, demanding progress and transparency. The contractors for each specialty — structure, masonry, electrical, plumbing, windows/doors, painting. And the subcontractors of those contractors, who you sometimes don't even know are on site until a problem shows up. On a mid-size residential project, it's easy to have four, five, six different companies working on the same slab.

Now look at how information moves between them today: separate WhatsApp groups — one with electrical, another with windows, an email to the developer, the revised drawing sitting in someone's drive, Tuesday's meeting decision living in the site engineer's head. Each company sees a slice, nobody sees the whole. When electrical needs to know whether masonry has already gone up so they can run conduit, they call — and wait. When a design change goes out, it reaches some groups and not others.

It's no surprise the whole industry suffers from this. Market surveys point to material and information unavailability being behind roughly 88% of delays — and on a job site with many subcontractors, a good chunk of that is a work front stalled waiting on another, or a contractor who executed against information that had already changed. The enemy isn't your team or the contractor. It's information trapped — in the wrong group, in someone's email, in the head of whoever was at the meeting. I detailed this cost in Job site communication: how much information trapped in WhatsApp costs your construction company.

Why charging per user breaks coordination

Here's the part almost nobody looks at when choosing a system, and it's where contractor management stumbles the most: how the vendor charges.

The logic for fixing this is obvious — if information doesn't flow because each company is off in its own corner, the solution is to put everyone in the same place: the developer, you, the electrical contractor, the window/door subcontractor, the warehouse keeper, all seeing the same schedule, the same valid drawing, the same status for every work front. That's what makes information flow.

The problem is that most systems charge per user — and that turns into a silent trap. Every contractor you add is another license, another monthly cost. So what happens at every construction company? You do the math and only add your own team: "I'll just notify the contractor over WhatsApp to save a seat." And there it is — you just recreated the exact problem you were trying to solve. The contractor's information stays trapped outside the system, and the system you paid for only sees half the job site.

It's structural sabotage: the per-seat model punishes you for doing the right thing — for bringing everyone inside. It pushes you to leave people out, and it's precisely the people left out who cause the delay. You pay for a coordination system and you're incentivized not to coordinate.

Everyone inside: the per-module model

That's why we charge per module, with unlimited users. And this isn't a pricing-table detail — it's a product decision that exists precisely because of the job site with many subcontractors.

Charging per module means paying for the capability you contract (procurement, quality, management, finance), not the number of people. You bring the whole job site inside without thinking about licenses: the developer follows along, your engineers coordinate, the electrical contractor sees the drawing and reports their own work front's status, the window/door subcontractor gets the dimension change the moment it's decided. No per-seat toll, no "who do we cut from the system to fit the budget" meeting.

In practice: when the opening's dimensions change, the change enters the job site and everyone who needs to see it, sees it — including the contractor who's going to install it. Windows no longer show up Monday to find out on site. Electrical's conduit doesn't get run before masonry is up, because electrical can see the work front's status without calling and waiting. Coordination stops depending on someone remembering to forward the information to the right group — because there's no more "right group." There's the job site, and everyone is on it.

Status and follow-up on outsourced work fronts without spending your day on the phone

Bringing everyone inside solves access to information. But there's still the other half of the contractor management problem: knowing where every work front stands, every day, without spending the whole day on the phone chasing people.

That's the routine that wears the coordinator down. "Is the slab done?" "Where's painting today?" "Did plumbing clear the floor?" A whole day of asking, and you still arrive at the meeting without the full picture — one person answered, two didn't, and one answered wrong. Manual follow-up always fails: it depends on you remembering to chase each person, and on each person remembering to answer.

This is where the logic changes with an agent that acts, instead of one more system to fill in. The AI Project Manager knows the schedule and knows which work fronts should have reported today. It chases the daily status of every outsourced work front — asks for status directly from the contractor, accepts the answer over the phone, by voice — and, if someone hasn't answered, chases again, on your behalf. You don't become the annoying person calling five times: the agent pulls together what each work front reported and hands you the consolidated picture. When a blocker shows up — electrical stuck waiting on masonry — it logs it and chases the mitigation from whoever needs to clear it.

The effect on the routine is concrete and measured: our Communication Hub, which answers any question about the job site and takes manual searching out of the loop, gives back roughly 10 hours a week to every project manager — more than a full business day that stops being spent asking "what's the status?" and goes back to running the job site. To understand why an agent does this and a pretty dashboard doesn't, it's worth reading AI in construction management: what AI agents do that dashboards don't.

A record that protects the construction company and the contractor

There's a last dimension of contractor management that usually goes unnoticed until the day it turns into an ugly argument: the record of who told whom what, and when.

Every job site with subcontractors has its finger-pointing moment. The work front fell behind — was it the contractor being slow, or the construction company releasing the area late? Windows came in wrong — did they mismeasure, or did the change never reach them? Without a record, it becomes memory against memory, and whoever has more bargaining power wins. That wears down the relationship with good contractors, and when it escalates into a change order or a dispute, it gets expensive.

When everyone works on the same job site, every decision, area release, design change, and reported status gets logged, with date and author — and that record protects both sides. It protects the construction company when the contractor moved slowly and there's evidence the area was released on time. And it protects the contractor when the delay wasn't their fault — when the record shows the information arrived late or the previous work front was stuck. It's not surveillance; it's fairness. A good contractor wants to work this way, because the record proves they did their part when the problem came from outside. This same principle of owned, traceable data applies to whoever hires the construction company, and I explored it in Controlling outsourced construction: stop depending on the report the construction company chooses to send you.

Frequently asked questions

1. My contractor won't want to use yet another system. They'll stay on WhatsApp. That's the right objection, and the honest answer is: if the system depends on the contractor stopping, opening an app, and filling out a form, they really won't use it. That's why the key is having the agent ask instead of waiting for data entry. The contractor answers the status over the phone, by voice — the same effort as sending a voice message on WhatsApp, except now it's logged and visible to the whole job site. And we bring engineers into onboarding specifically to design this routine with the work fronts, not to drop off a login and hope for the best.

2. I already have Sienge/TOTVS. Doesn't that control contractors? The ERP records the contractual and financial side of the contractor — measurement, contract, payment. It's a good record, and you should keep it. But it's passive: it doesn't chase daily work-front status, doesn't notify windows that the dimension changed, doesn't cross-reference one work front's progress against another's dependency. That's active coordination, a different layer. That's why we integrate with the ERP, we don't replace it — TrackBuild acts on what's happening on site, the ERP archives what already happened.

3. Truly unlimited users? Where's the hidden toll? There's no per-seat toll. Pricing is per module — the capability you contract — and the number of people inside the job site is unlimited on every plan. It's intentional: bringing the contractor and subcontractor inside at no extra cost is what makes coordination work.

4. Doesn't bringing the contractor inside expose data that's mine? No, because access is role-based and site-based. Each company sees only what it needs to run its own part — the electrical contractor sees their work front and their drawings, not your cost spreadsheet or the job's margin. Governance, permission levels, and per-site isolation are part of the product, not an add-on: you bring everyone inside without opening what shouldn't be opened.

5. Is R$10,000 a month expensive just to coordinate contractors? Compare it to what miscoordination costs today, not to zero. A work front idle for a day because information didn't arrive, windows redone because of a wrong measurement, an emergency purchase triggered because two work fronts collided — any single one of these events, on its own, already costs a chunk of that monthly fee. It's half the salary of a mid-level engineer for a manager who chases every work front all the time and never forgets to pass along a change — something around 1% of the job's cost to recover the 3.6% to 7.6% that today leaks out through uncoordinated work fronts (that range is our estimation model, conservative and bottom-up, not a measured client result — our pilot is less than a month old).

How TrackBuild tackles contractor management in practice

Everything this article described — the change trapped in the wrong group, the status that only arrives when you call, the argument over who told whom — comes from the job site's companies being separated. TrackBuild was built to put them all on the same job site and make information flow:

• AI Project Manager — knows the schedule, chases the daily status of every outsourced work front, pulls together status that arrives by voice or phone, and logs blockers, chasing the mitigation from whoever needs to clear them. You stop being the job site's telephone.
• AI Communication Hub — the job site's living memory, answering anyone — yours or the contractor's — which drawing is valid and what was decided, citing the source. This is where the hours of schedule time given back to the project manager every week come from.
• Per-site record and audit trail — every work-front release, design change, and status report gets logged with date and author, protecting the construction company and the contractor when a delay turns into an argument.
• Engineers in onboarding — software dropped in the contractor's lap doesn't change site routines. Rollout comes with method and engineering people, designing the work-front follow-up together with your team and the subcontractors.

And what makes all of this actually work: unlimited users, per-module pricing. You bring everyone onto the same job site with no per-seat toll — because coordination only exists when everyone is inside. Already have an ERP? Even better: we integrate, we don't replace.

Find out how much uncoordinated work fronts cost on your job site

A contractor stuck waiting on information is just one leak — alongside it come the emergency purchase when two work fronts collide, the rework from a change that never arrived, and the hours on the phone chasing status. Each one disappears into the overall numbers on its own; added up, they're worth more than any visible delay. The Leak Diagnosis is a free 30-minute call where we calculate, using your own data, how much your job site loses per month to uncoordinated work fronts and information trapped between companies — no commitment.

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 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 job site's daily routine, with unlimited users, so information stops getting trapped and margin stops leaking away.