HubSpot for Contractors: What Works and What Does Not

Why the default setup fights you

HubSpot's defaults encode a software sales motion: an individual buyer, a short cycle, a single decision, and a product that ships the moment the deal closes. Construction is the opposite on all four counts. The buyer is an organisation with a GC, an owner, an architect and three subs attached. The cycle runs months and includes a bid that may lose on price alone. And closing the deal is where the actual work starts, not where it ends.

None of this makes HubSpot the wrong tool. It means the out-of-the-box configuration describes someone else's business.

The four changes worth making first

In rough order of how much pain each one removes.

1. Centre the company, not the contact. Your relationship is with a general contractor or a property owner, and the people rotate. Reporting, associations and lifecycle should hang off the company record so a project manager changing jobs does not orphan the history.
2. Separate the bid from the project. The bid is a deal with a pipeline and a close date. The project that follows has phases, a schedule, RFIs and a budget, and forcing it into deal stages produces a pipeline full of things that are already sold.
3. Give the site its own record. Billing address and job site are routinely different, and a company can have dozens of sites. Modelling the site as a property on the company guarantees that the wrong address reaches a technician eventually.
4. Track bid-hit rate, not just pipeline value. For contractors, the question is which kinds of work you win and at what margin. Deal properties for project type, delivery method and estimator make that answerable; a generic pipeline does not.

What to keep HubSpot out of

Resist the temptation to model the job. Field execution — scheduling, dispatch, technician time, materials, RFIs, submittals, punch lists, job costing — has no native home in HubSpot, and every attempt to build it there rebuilds a scheduling engine badly.

The clean division of labour: HubSpot owns the customer, the opportunity, the quote and the commercial relationship. A field service platform owns the project, the schedule, the field and the cost. The two stay in agreement through a bi-directional sync rather than through a person retyping.

Reporting that a contractor actually uses

Once the model is right, a handful of reports do most of the work: bid-hit rate by project type, average days from bid to award, pipeline by delivery method, revenue by estimator, and — only if execution data flows back — sold value versus delivered value. That last one is the one owners ask for and the one that requires the field system to write back into HubSpot.

The honest limits

HubSpot will not schedule a crew, will not work offline in a basement, will not tell you a job is over budget, and will not produce a lien waiver. Anyone who tells you it will is selling an implementation. Configure it for what it is genuinely best at — the commercial system of record — and connect it to something built for the field.