Can subs be in the system without a paid seat

It is the same question in every contractor forum, worded a hundred ways. You run a small shop. You bring in a drywall sub for six weeks in the spring, a grading guy for a couple of jobs a year, an electrician you sub out to twice a quarter. You would love for them to see the job the way your crew does: the scope, the address, the photos, the punch list. But you are not about to pay a monthly seat for someone who is on one job and then gone until fall. So you ask the room: can I get a sub into the system without buying them a license?

The question is fair, and the reason it keeps getting asked is that most tools answer it badly. This is a buyer’s question, so let us treat it like one. Here is how the incumbents actually handle a sub, what each way costs you in money and in dropped handoffs, and then the straight answer for how our setup does it. If you are weighing the whole category, the choosing software guide is the wider map; this article is just the sub-access corner of it.

The three ways the tools handle it

Survey the field-management apps small shops actually shortlist and you find three patterns. Every product is some mix of these.

Pay for the seat. Jobber, Housecall Pro, Buildertrend, and most of the crew-management tools price per user, per month. To put a sub inside the job they become a user, and you pay for that user for as long as they exist on the account, whether they worked this month or not. Some let you deactivate between jobs, which means someone in the office remembers to turn the seat off in April and back on in September, and forgets half the time. The tool is not wrong to work this way. It is built for your permanent roster, and a sub is not that.

Give them a limited portal. Buildertrend and the heavier project tools give subs a separate, cut-down login: a portal where they see their tasks and schedule but not the full job. It is free or cheap, and on paper it solves the problem. In practice it is a second place, with a second password, that the sub uses for one job and never signs into again. Getting a busy sub to adopt a portal for a six-week job is most of the battle, and losing that battle means he goes back to texting you.

Skip the software entirely. The most common answer in the real world is the oldest one: you keep the sub out of the system and send him what he needs by text and email. A PDF of the scope, a few photos, an address, a “you still good for Thursday.” CompanyCam and the photo-documentation apps sit next to this, the sub takes his own pictures on his own phone and you never see them unless he sends them. It costs nothing in software. It costs everywhere else.

What each workaround actually costs

Put plain numbers on it, because the cheap-looking option is usually the expensive one.

Take the paid seat first. Say a tool runs $30 a user each month and you carry two subs as users year-round so you do not have to keep toggling them. That is $720 a year for two people who worked maybe ten weeks between them. Per-seat pricing is built to grow with your headcount, and a sub is headcount you do not actually carry. That is the same trap that makes the tool punish you for hiring: every person you add, even a part-timer, is another monthly line.

The limited portal looks free, and the license is. The cost is the handoff that does not happen. The sub never logs in, so the scope you carefully entered lives in a portal he has not opened, and you end up texting him the address anyway. Now the job runs in two places: your crew sees it in the app, the sub sees it in your texts, and the two never reconcile. When he finishes and you cannot tell without calling, you have paid nothing and gained nothing.

The text-and-PDF route is the one that hides its bill best. It is free, and it works right up until it does not. The sub finishes the rough-in, texts you a thumbs-up, and moves on. Three weeks later the inspector flags it and you have no photo of what he actually did, no record of the scope you sent, and a sub who remembers the job differently than you do. That is a re-visit: his time, your time, a slipped day on the trades behind him. One missed handoff on a subbed task is the same two-thousand-dollar callback as any other lost message, except now it is a sub’s word against yours with nothing written down.

So the scorecard reads: the paid seat costs real money for idle capacity. The portal costs a handoff the sub will not adopt. The text route costs the record you needed exactly when a job goes sideways. None of the three is fine. Each one is a small shop paying, in cash or in risk, for a gap the tool left open.

The verdict, and the full version of the answer

Yes, in our setup a sub can be in the system without a paid seat.

Here is how it works. A subcontractor joins the work-order thread as a free guest. He sees the same job your crew sees: the scope at the top, the address, the photos on the tasks, the punch list. He does not get a stripped-down portal and he does not get a bill. He is a guest on one active job at a time, and you pay only for your own roster, one price a head, no per-job fees. When the job is done, he is done, nothing to toggle off, nothing quietly billing you until you remember to cancel it.

The reason that matters is not the free part, though the free part is real. It is that the sub is inside the same thread as the work, not off in a portal or buried in your texts. His photo lands on the task it proves. His “done” is a state you can see, not a thumbs-up you have to interpret. If you want the fuller picture on keeping subs in the loop without forcing a purchase on them, the guide on managing subcontractors without making them buy software covers the day-to-day of it.

There is a fair question underneath all this, which is what the whole system costs you before you ever add a sub. That is worth its own look; the full math is in what field apps really cost. But on the narrow question you came here to answer, the one the forum keeps asking, the answer is clean: the sub does not need a license to be in the job, because in this setup a guest on the thread is the whole point, not an upsell.

We are new, so take that at the size it deserves. Put one subbed job on it, the next drywall crew or grading guy you bring in, and watch what happens to the handoff. A thread per job means the sub sees the scope without you retyping it. Proof on the task means his work is documented whether or not he thinks to send you a picture. Sign-off by rank means the job ends with someone saying it is finished, on the record, instead of a text you hope you can find in November. That is the answer to the question you actually asked: not a cheaper seat, but no seat at all, and the record kept anyway.