Where a sub's work comes from
Your subs do not work for you in the abstract; they work on jobs, and every job has a payer behind it, a carrier, a TPA, or a private client. Verinode reads that connection in both directions. Per…
On this page
Two views of the same question
Your subs do not work for you in the abstract; they work on jobs, and every job has a payer behind it, a carrier, a TPA, or a private client. Verinode reads that connection in both directions. Per sub, the Clients tab on a subcontractor's card shows whose work that one sub is doing. Book-level, the By client tab in the analysis deck flips it around and shows which payers drive your sub spend as a whole, and which sub each payer's work leans on most. Together they answer a question that rarely gets asked until it hurts: if this sub stumbled tomorrow, whose work would feel it?
Both views are built the same way, from your own data: your subcontractor cost lines, grouped by the job they were billed on, rolled up to the job's paying client. A job with no client on file yet lands in an "Unassigned" bucket rather than being dropped, so the totals stay honest.
The Clients tab on one sub
Open a sub from the Subcontractors page and swipe to Clients. The tab leads with its own warning, stated as the reason the view exists: "Where this sub's work comes from. Concentration on one client means their coverage or reliability slipping puts that revenue at risk."
Below that, each paying client appears as a ranked bar, largest first: the client's name, the sub's total cost across that client's jobs on the right, and a job count underneath ("3 jobs"). The bar lengths make concentration visible at a glance. A sub whose bars step down evenly across four carriers is a general resource; a sub with one long bar and a stub is, in practice, a dependency of that one relationship.
That is worth sitting with for a second, because the risk runs through the sub, not around them. If one carrier's jobs account for most of what a sub does for you, then that carrier's revenue is quietly resting on this sub's certificate of insurance staying current and their work staying clean. A lapsed COI or a run of callbacks does not just cost you a sub; it wobbles a specific client relationship. When the tab has nothing to show, it says so plainly: "No paying client tied to this sub's work yet." The artifact that fills it is the same one that fills the Jobs & margin tab: subcontractor invoices tied to your jobs.
The By client tab across your whole book
The book-level view lives in the analysis deck: on the Subcontractors page, open Analyze your subs in the Apps row and swipe to By client. Its intro frames the stakes from the other side: "Which payers drive your sub spend. A lot riding on one carrier or TPA is a concentration to watch, and a place to renegotiate if a sub's cost is high."
Here each bar is a payer, ranked by the total sub cost you have incurred on their jobs. The line under each name reads the shape of the relationship: how many subs worked that payer's jobs, across how many jobs, and, where one sub dominates, who: "4 subs · 11 jobs · mostly Rivera Drywall." That "mostly" is the load-bearing word. It names the sub each payer's work leans on most, which is exactly where a coverage lapse or a reliability slide would land first.
What this view is and is not
Everything here is your own data about your own book. It is not a benchmark, not a peer comparison, and not a judgment on any carrier or sub; it is arithmetic on your invoices, made visible. When it is empty, the empty state names the reason ("No paying client tied to your sub work yet"), and the way in is always the same: forward the sub invoices tied to your jobs, and make sure your jobs carry their client. The rest of the analysis deck, verdicts, trade rankings, cost, and capacity, is covered in the subcontractor analysis app.
Data sources
Data sources
- 1.Subcontractor cost lines from your forwarded invoices and job cost exports. Your business.
- 2.Your jobs and their paying clients (carriers, TPAs, and private payers). Your business.