CRM for specialty trade subcontractors
A subcontractor's customer is not the building owner; it is the general contractor, and the relationship runs on a rhythm no sales CRM understands: get prequalified, get invited to bid, win some share of the invitations, then survive the project financially. The pipeline vocabulary of leads and closing describes almost none of it. What actually needs managing is a short roster of GC accounts, the prequalification documents that expire and quietly stop the invitations, and the awarded projects whose billing behaviour determines whether the GC deserves the next bid at all.
Where the generic CRM breaks:
GCs are accounts, not leads. Revenue comes from a dozen general contractors, each with multiple project managers and estimators who move between firms. A lead-and-convert model has no shape for a standing relationship whose health is measured in invitations per quarter.
Prequalification is nowhere. Insurance certificates, bonding letters and workers' compensation clearances expire on their own schedules, and a lapsed document silently removes you from bid lists. No generic CRM tracks the paperwork that keeps the phone ringing.
Won is where the risk starts. For a sub, the award begins the dangerous part: contract terms to review, a schedule of values to negotiate, holdback to track. A CRM that archives the record at closed-won goes dark exactly when the money goes at risk.
Payment behaviour never reaches the bid decision. The GC who pays in ninety days and disputes every invoice gets the same eager bid as the one who pays in thirty, because the estimating desk cannot see the receivables history. That disconnect prices risk at zero.
The data model that actually fits:
GC account. The firm, its people and their movement between firms, invitation and award history, and payment behaviour from your own ledger — one record answering the question every bid starts with: do we want this client.
Prequalification package. Per GC where required: the documents submitted, their expiry dates, and renewal work generated before lapse — insurance, bonding capacity, compliance clearances — so eligibility never silently expires.
Bid invitation. Scope, due date, documents and outcome per GC, making win rate and invitation flow per account visible — the two signals that show a relationship strengthening or dying.
Awarded project. Contract value, schedule of values, billing dates and holdback with its release date — the record that persists after the win and carries the money the sale actually produced.
Payment experience. Days to payment, disputes and backcharges per GC, summarised from real invoices, feeding back into the account record where the next bid decision can see it.
Our verdict: Do not buy a construction project-management suite to solve a relationship problem — the field and document tools you use with each GC are usually dictated by the GC anyway. The gap is commercial and it is specific: GC accounts with payment history, expiring prequalification documents, and a bid table per client. That is a small build, and for most subs the prequalification tracker alone pays for it the first time a certificate would have lapsed unnoticed.
What does a healthy GC relationship look like in numbers?
Steady or growing invitations per quarter, a stable win rate, and payment days that match the contract. Any one of those slipping is a signal: fewer invitations means a competitor is winning the relationship; a falling win rate with steady invitations often means you have become price coverage.
Why do prequalification documents cause so much silent damage?
Because nothing announces the failure. A lapsed insurance certificate does not generate a phone call — the GC's system just stops including you, and you experience it months later as a slow quarter. Expiry-driven renewal work is boring and it is the single most protective automation a sub can run.
Should the CRM hold the schedule of values and billing?
Hold, yes; replace accounting, no. The awarded project record should know the SOV, the billing dates and the holdback release date so that commercial questions have one home. The invoices themselves stay in accounting — the point is that bid decisions and billing reality finally share a record.
Does this apply to subs who work mostly for one or two GCs?
Concentration makes it more important, not less. With two clients, an invitation slowdown is an existential event, and the account-health signals — invitations, win rate, payment days — are your early warning. It also makes the case for deliberately building a third relationship measurable instead of aspirational.
Last reviewed 27 August 2026