CRM for Contractors: How to Choose and Configure One for a Contracting Business
CRM for contractors explained: which facts belong in the CRM and which in the field tool, and how to forecast a project priced through several contractors.
Paul Maxwell, PhD
AUTHOR
GET WEEKLY REVOPS INSIGHTS
No spam. Unsubscribe anytime.
A mechanical subcontractor prices a hospital wing for three general contractors, each bidding the same project to the owner. A CRM for contractors built on the standard deal model now holds three deals at one amount, and its pipeline report adds them together. When one general contractor wins and awards the package to the subcontractor, the CRM records one win and two losses on a job the firm has won. Any reason picked from a standard lost-reason list misdescribes both losses. After award, superintendents update the field tool while the office moves the deal to In Progress, and the two systems diverge.
This article explains how a contracting business uses a CRM beside the field tool that runs its jobs. It starts with the bid and estimate flow, then the counting problem created when one project is priced through several general contractors, worked through on sample data. It then draws the award handoff, sets out which facts belong in which system, and gives a HubSpot configuration procedure. It closes with where a field tool alone wins, costs and returns, symptoms, limits and common questions.
A pursuit is one attempt to win one project through one route: an invitation from a general contractor, or a request direct from an owner. A project is the building or scope being priced, and one project can carry several pursuits. The route ratio is the number of pursuits divided by the number of distinct projects over the same period. The field tool is the construction management or field service software that runs an awarded job. The award boundary is the moment a pursuit becomes a job, where the CRM stops owning the record.
The Bid and Estimate Flow Before Award
Stage design is covered under bid pipeline stages; the question here is what each step writes, and to which system. An invitation creates the pursuit as a deal, associated with the inviting company and carrying the due date that company set. Each general contractor sets its own date, so the date belongs to the route rather than to the project. A declined invitation is closed with its reason rather than deleted.
Takeoff quantities and unit prices belong in estimating software. Procore documents its Bid Board as the place to view the bids a company has been invited to, manage its intention to bid, and begin takeoff and estimating. The CRM holds the facts that decisions across pursuits rest on: the estimator, the bid due date and the estimating hours spent.
Submission writes the price to Amount, which HubSpot's default deal properties define as the total value of the deal, and the expected decision to Close date. For a subcontractor one fact outweighs the rest: the estimate is produced once per project, while the price is submitted once per route, so the CRM receives one deal for every route.
One Project Priced Through Several General Contractors
The owner selects one general contractor, and that contractor selects one subcontractor for each trade package. A subcontractor that priced the project through three general contractors can be awarded through only one of them, and its other routes end when the owner decides, whatever its price. The routes are not duplicates in the sense treated under HubSpot duplicate management: each has its own company, due date and outcome, and merging them would discard that history. Adding them together is the opposite error.
HubSpot calculates each deal's Weighted amount as its Amount multiplied by its Deal probability, and sets Deal probability automatically from the win probability of the deal's stage, per the deal property definitions. Nothing in that calculation knows that three deals share one project.
The finding can be checked against any contractor's own export. Where projects are priced through several routes, the win rate a deal report produces over submitted deals is lower than the firm's project win rate by a factor of exactly the route ratio. A forecast that applies the project rate to every deal overstates the pipeline by the ratio of open deal value to open project value.
Both errors come from three rates reported under one name. The project award rate divides projects awarded by projects priced, and estimators quote it. The pursuit award rate divides awarded deals by submitted deals, and a deal report produces it. The route conversion rate divides awards by the pursuits whose general contractor won the project; it sets aside projects decided between the owner and the general contractors, so it comes closest to the subcontractor's own competitiveness. The same two-event structure appears in an illustrative case study separating an award from a win at an aggregate supplier.
Sample Pipeline Arithmetic for a Specialty Subcontractor
The figures below are sample data for an invented electrical subcontractor and describe no client. Over twelve months the firm priced 60 projects through 150 submitted pursuits and was awarded 15 projects, each going ahead with one general contractor and one electrical package.
| How the pursuit ended | Pursuits | Outcome reason to record |
|---|---|---|
| How the pursuit endedAwarded to the firm | Pursuits15 | Outcome reason to recordClosed won |
| How the pursuit endedProject awarded to the firm through another route | Pursuits24 | Outcome reason to recordAwarded through another route |
| How the pursuit endedGeneral contractor won, another subcontractor chosen | Pursuits30 | Outcome reason to recordSubcontractor not selected |
| How the pursuit endedGeneral contractor did not win the project | Pursuits81 | Outcome reason to recordGeneral contractor not awarded |
| How the pursuit endedTotal | Pursuits150 | Outcome reason to record |
The project award rate is 15 of 60 projects, or 25%. The pursuit award rate is 15 of 150 deals, or 10%, lower by a factor of 2.5, the route ratio. The route conversion rate is 15 of the 45 pursuits whose general contractor won, or 33%. A portal closing all 135 unawarded deals as lost on price records 24 of those losses on projects the firm won.
At the end of the period, eight projects sit open at the Submitted stage. Each is priced at $200,000, and every route carries that price, so each three-route project is the one drawn above: $600,000 in deals against $200,000 that can be awarded.
| Routes per project | Projects | Sum of prices | Sum of deals |
|---|---|---|---|
| Routes per project3 | Projects5 | Sum of prices$1,000,000 | Sum of deals$3,000,000 |
| Routes per project2 | Projects2 | Sum of prices$400,000 | Sum of deals$800,000 |
| Routes per project1 | Projects1 | Sum of prices$200,000 | Sum of deals$200,000 |
| Routes per projectTotal | Projects8 | Sum of prices$1,600,000 | Sum of deals$4,000,000 |
| Method | Calculation | Forecast |
|---|---|---|
| MethodEvery deal, at the project award rate | Calculation$4,000,000 × 25% | Forecast$1,000,000 |
| MethodEvery deal, at the pursuit award rate | Calculation$4,000,000 × 10% | Forecast$400,000 |
| MethodOne deal per project, at the project award rate | Calculation$1,600,000 × 25% | Forecast$400,000 |
The first row is what a portal produces when the estimators' 25% becomes the Submitted stage's win probability and every route is a deal: 2.5 times the other two, the same multiple as $4,000,000 over $1,600,000. The second and third rows agree only because the open value ratio, 2.5, matches last year's route ratio. When a quarter brings more multi-route invitations, the second method rises with the ratio while the third does not, so the procedure below counts one deal per project.
The Award Handoff Between the CRM and the Field Tool
At award the job begins, and ownership of the record changes hands once. Four facts cross to the field tool: the customer and its contacts, a shared project identifier, the awarded price as the original contract value, and a scope summary. Procore's RFIs tool and Daily Log hold a project's information requests and daily activities, and neither informs whether to bid the next project.
Where estimating runs in the field tool, the project can start there: Procore's Bid Board documentation states that an awarded bid can be added to the Portfolio, which adds a new project in Procore. The identifier then flows from the field tool to the CRM, which works if it is written once and never matched on a job name.
Four summaries return: the approved change-order total, covered under change orders between HubSpot and a construction management system, then the completion date, final contract value and final margin at closeout. Job status stays in the field tool, since a deal stage named In Progress creates a second status that nobody on site updates.
CRM Records and Field Tool Records, Fact by Fact
A fact read to decide whether to bid the next project, or to compare customers across jobs, belongs in the CRM. A fact written and read within one job belongs in the field tool, and a field fact read across jobs returns once, as a summary.
| Fact | Where it belongs | At award and after |
|---|---|---|
| FactGeneral contractors, owners, architects and their people | Where it belongsCRM company and contact records | At award and afterCustomer copied to the job |
| FactRoute, due date, bid decision, outcome and reason | Where it belongsCRM, on each pursuit | At award and afterStays in the CRM |
| FactTakeoff quantities and unit prices | Where it belongsEstimating software | At award and afterStays with the estimate |
| FactEstimator and estimating hours | Where it belongsCRM, once per project | At award and afterStays in the CRM |
| FactPrice submitted | Where it belongsCRM, on each pursuit | At award and afterAwarded price becomes the original contract value |
| FactProject identifier | Where it belongsBoth systems | At award and afterWritten once, and every later write matches on it |
| FactSchedule, daily logs, RFIs and submittals | Where it belongsField tool | At award and afterNever enters the CRM |
| FactJob cost and itemised change orders | Where it belongsField tool and accounting | At award and afterApproved change total and final margin return |
| FactJob status, completion date and final contract value | Where it belongsField tool | At award and afterStatus stays; both values return at closeout |
Configuration Procedure for a HubSpot Contractor Pipeline
The firm publishing this article is a HubSpot Solutions Partner, an interest to keep in view; the model transfers to any CRM with custom properties. Association labels require a Professional or Enterprise subscription, which sets the floor.
- Measure the route ratio. Export twelve months of submitted bids with the inviting company and project address, give each distinct project one identifier, and divide bids by projects. Near 1.0, the standard deal model already counts correctly, and only the outcome reasons in step 2 and the handoff in step 7 apply.
- In Settings, open Properties and select Deal properties. Following HubSpot's property documentation and its field types, create Project ID as single-line text, Primary pursuit as a single checkbox, Route due date as a date picker and Estimating hours as a number. Add Pursuit outcome reason as a dropdown select holding the four outcomes in the first sample table, plus Declined to bid and No decision.
- Under Data Management, open Data Model and create deal-to-company labels for Bidding general contractor, Owner and Architect; HubSpot allows up to 50 labels per object pair.
- In Settings, under Data Management, open Objects, select Deals and open the Pipelines tab, as the pipeline documentation describes, and set the Submitted stage's win probability to the project award rate.
- Enter every route as its own deal with the same Project ID and its own price. Tick Primary pursuit on the first deal for each project, and record the project's estimating hours on that deal only.
- In the custom report builder, report on open deals with Primary pursuit ticked, summing Weighted amount.
- At each decision, close the awarded route as won and every other route with its outcome reason, then create the job in the field tool carrying the Project ID. The owner's decision can close the primary route while another route stays open for the subcontract award. Move the Primary pursuit tick to that open route, or the project drops out of the forecast while it can still be won.
- Verify the configuration. In an export of open deals, the count of deals with Primary pursuit ticked must equal the count of distinct Project IDs. A higher count means a project is counted twice; a lower count means an open project has lost its primary deal. Recompute the forecast by hand from the primary deals and compare it with the report, then confirm the latest awarded project has exactly one closed-won deal and no route closed on price.
On Enterprise subscriptions a custom object named Project can hold the project-level facts, with every pursuit associated to it, replacing a typed identifier with an association.
The Case for a Field Tool Without a CRM
Two axes favour the field tool outright. The first is users. Procore charges an annual fee by product based on Annual Construction Volume, and states that it will never charge for adding users. HubSpot states that its paid Sales Hub plans are priced per seat, so every superintendent or foreman added is a licence decision for job facts that belong in the field tool.
The second is continuity where each job arrives through one route. Housecall Pro documents a Copy to Job action on an approved estimate, which fills the job's fields from the estimate and keeps a copy of the estimate on file. At a route ratio of 1.0, one record from estimate to job needs no integration, and a CRM beside it is a second place to type every customer.
A CRM earns its place under the opposite conditions, a high route ratio and customers who return, and products are compared in the guide to the best CRM for construction.
Costs and Returns of the Pursuit and Project Model
The model buys a forecast whose rate and unit match. Route conversion by general contractor shows which contractors carry the firm when they win, the question on which a subcontractor's business development turns. Estimating hours held once per project give a true cost of sale per award.
It costs a Project ID and a Primary pursuit decision at every invitation, an outcome reason at every close, and an integration or a manual copy at award. The flag is the weak point: a second ticked deal doubles a project, a tick left on a closed route drops one, and neither shows as an error until the count in step 8 is run.
The case is strongest for specialty subcontractors pricing commercial work through several general contractors, where a ratio of 2.5 turns an accurate 25% rate into a forecast 2.5 times too high. It is weakest near 1.0, for a general contractor pricing owners directly, a remodeler or a service contractor, where each project is one deal and the extra properties describe nothing.
Symptoms in a Contractor Pipeline and Their Sources
The weighted pipeline runs at a multiple of what the firm is awarded in a comparable period. Deals for one project are summed at a probability measured on projects, and the remedy is the Primary pursuit filter or a probability measured on deals.
Estimators quote a win rate far above the CRM's. Both are correct over different denominators, and the gap is the route ratio. The fix lives in the report titles: name each rate by its denominator, and count the project rate over distinct Project IDs rather than deals.
Price leads the loss-reason report, including on projects the firm won. Routes that ended when another route carried the award, or when their general contractor lost, were closed with a default reason instead of the outcome reasons in step 2.
A deal reads In Progress while the job is on hold, or jobs appear with no deal behind them. Both systems write status, or projects were created by hand without the shared identifier, and the remedy is a job created from the award with status owned by the field tool.
Scope, Sources and Limits of the Evidence
This article covers the record kept before award and its boundary with the field tool, and the page on HubSpot for construction and contracting firms gathers the related published work, and two head-to-head pages compare HubSpot with Buildertrend and with ServiceTitan. The search term crm for government contractors names a different business, selling to public agencies, and is not addressed. Every vendor fact cited is as documented in September 2026.
The finding is arithmetic rather than empirical: it follows from the award of each trade package to one subcontractor and from HubSpot's definition of weighted amount. It does not show how widespread multi-route pricing is or what ratio is typical in any trade, since no published study located for this article measures either, and the sample figures are invented. Where one subcontractor can win several packages on a project separately, the one-award rule and the Project ID apply per package.
Questions on CRM Software for Contractors
What is CRM software for contractors? CRM software for contractors holds pursuits: the companies inviting bids, each route, its price and its outcome, while the field tool holds the awarded job.
Is a CRM for construction companies or contractors different from a general sales CRM? The software can be identical, but the buyer sets the decision date, one project can carry several deals, and the record hands over at award.
Is a CRM for general contractors configured differently from one for subcontractors? A CRM for general contractors pricing owners directly has a route ratio near 1.0, so one deal per project counts correctly.
Does a CRM for electrical contractors need a different setup from a CRM for roofing contractors? The route decides, not the trade: electrical work priced through several general contractors needs the project model, roofing sold direct to owners does not, and a CRM for painting contractors follows the same test.
What should CRM software for electrical contractors track that estimating software does not? Each route with the general contractor behind it, that contractor's due date, the outcome reason, and estimating hours once per project; together they give route conversion by general contractor, which no single estimate shows.
Is there a free CRM for contractors? HubSpot's Sales Hub pricing page lists its free tools as free for up to two users, though labelling each company's role on a route needs association labels, which start at Professional.
What is the best CRM for field service contractors? Where each job arrives through one route, a field service platform that converts the quote into the job covers the sale, and a CRM for service contractors earns a place once past customers are marketed to.
What is the best CRM for home service contractors? The field service platform's customer list serves a firm selling to homeowners one job at a time, until marketing to past homeowners calls for a CRM to hold that list.
What is the best CRM for commercial service contractors? Property managers award work across sites and years, so a CRM holding that relationship, joined to the field service platform, earns its place.
In Summary
A contractor's CRM holds what is written before award: the companies, each pursuit with its route and due date, the bid decision, estimating hours, prices, and outcomes with reasons. The field tool holds the job and its status from award onward, joined to the CRM by one project identifier.
Where one project is priced through several general contractors, only one route can be awarded. A deal-level win rate therefore understates the project win rate by the route ratio, and a project rate applied to every deal overstated the sample forecast 2.5 times.
A single division, needing no software change, settles the model: last year's submitted bids over last year's distinct projects. Near 1.0, the standard deal model is right; well above it, the board view is adding together deals that cannot all be awarded.