How to manage subcontractors without making them buy software

You do not get to make a plumber buy anything. He runs his own shop, he works for four other GCs besides you, and the last thing he is going to do is pay a monthly fee to sit inside your system for the six weeks he is on your job. Ask him to and he will nod, never sign up, and keep answering you by text. So most small shops give up on the idea of having subs in the system at all, and go back to running them out of a phone and a memory.

That is the real problem with subcontractor coordination on a small crew. Not that the tools are bad. It is that the tool only covers the people you pay for, and the sub is on the outside of it, reachable only through the same scattered channels that lose things on your own crew. So you end up managing your framer in a text thread, your electrician in an email chain, and the tile guy in a string of voicemails, and none of those three places talks to the job.

The workarounds, and where each one loses the record

Before naming the shape that works, walk through the ones most shops already run, because each of them does something right before it fails.

The email chain. You send the scope, he replies, you reply, and for a week it holds. Then the reschedule comes in on a text instead because email is slow, the change never makes it back into the chain, and now the written record and the real plan have split. Six weeks later you are searching your inbox for a decision that was actually made by phone.

The one-off text. Fast, and the sub will always answer a text. But every job he is on lives in the same thread, the confirm-for-Tuesday and the where-is-the- gate-code and the two-months-ago address all stacked together, and when the dispute comes you are scrolling a wall of messages trying to prove what he agreed to. A text is a place to talk. It is not a record you can hand anyone.

The portal he never opens. Some office suites let you invite a sub in as a guest, which sounds right until you watch it happen. He gets an email, it asks him to make an account and a password, he is standing in the sun with gloves on, and he closes it. By Thursday he is back on WhatsApp and you are relaying his answers into the system by hand, which is the exact work you were trying to stop.

Every one of these is a way of keeping the sub reachable while keeping the record somewhere else. That split is the whole failure. The scope is in email, the change is in a text, the photo is on his phone, and the job itself has none of it.

Put a number on the split

Say the tile sub confirms Tuesday over the phone on Thursday. You write it on a legal pad, or you trust your memory, and Monday you build the rest of the week around him. Tuesday he does not show. You call and he says he told you Wednesday.

Maybe he did. The point is you cannot prove otherwise, so you eat it. The crew you staged around the tile has half a day of nothing to do: two men, four labor-hours gone. The finish carpenter you lined up behind the tile slides, which ripples into the back half of the week. And the customer, who you told would be done Friday, now hears next Monday. None of that is a catastrophe on its own. It is a few hundred dollars and a bruised customer, and it happens because the confirm lived in your head instead of somewhere both of you could see.

That is the pattern across all three workarounds. The cost is never one big bill. It is small leaks, a slipped day here, a re-asked address there, a scope fight you lose because you cannot scroll back to the agreement. They add up to a real number over a year, and they all trace back to the sub being managed outside the job.

The only shape that works

The fix is not a better portal or a stricter texting rule. It is to stop treating the sub as someone you manage from the outside, and let him join the job the same way he already joins a group text: you send an invite, he taps it, and he is in the thread for that one job. No account to build, no fee on his end, no software he had to buy. He sees the tasks that are his, he can answer the confirm in one word, and when the work is done he posts the photo right on the task instead of into a text you have to go find later.

This is exactly what a subcontractor guest is on Crewmigo. The sub joins the work-order thread for the job he is on, free, one active job at a time. You do not pay for him and he does not pay for anything. The seat you pay for is your own crew, one plain price a head, and the subs ride along as guests. So the question the title asks, how do you manage subs without making them buy software, has a literal answer: you do not put them in your paid system at all. You invite them into the job, and the job is free for them to be in.

Getting that first invite to stick is its own small skill, and it is worth doing right the first day. If you have not set the ground rules with a new sub yet, onboarding a new sub in one day covers what to settle before he parks, with the thread invite as the last line on the sheet. Once he is in, the day-before confirm-for-tomorrow ritual runs on one message with the yes on the record. And when a sub goes quiet on you, it is usually because answering costs him too much; getting subs to respond walks the changes that get replies inside a day, most of which get easier once the ask lives in the job instead of in your phone. All three sit in the subcontractors hub if you want the full run.

Why this holds where the others leak

Walk the same three failures back through the guest-in-the-thread shape and they close on their own.

The scope does not split off into email, because the scope is a task in the thread the sub is already looking at, and a change typed there the day it is agreed sits with a date on it. The confirm is not stuck in your memory, because the sub answered it in the thread and the yes is on the record. And the closeout photo is not stranded on his personal phone, because he posted it on the task, and the record belongs to the company, not to him. When he rolls off to the next GC’s job, none of it walks off with him.

That last part matters more than it looks. A sub who lives in a text thread takes the whole history with him when he is done. A sub who worked the job as a guest leaves the job intact: the scope, the confirms, the change notes, the proof photos, all still sitting on the tasks where the work happened. You can hand that to a customer, to an inspector, or to the next sub who has to pick up where this one left off.

You do not have to reorganize your whole business to try this, and we are not going to pretend the software has been around forever. Put your next job on it, invite the one sub you use most, and see if the confirm and the closeout photo being on the job instead of in your phone changes how the week goes. The sub pays nothing, marks his own work done when he finishes, and you approve it from wherever you are standing. That is the whole idea: the people you pay for are your crew, and everyone else joins the job for free.