CRM for General Contractors: What to Track From Bid to Closeout

How we wrote this. Conduit is platform-agnostic. We set up and optimize the tools in this article for clients, so this comparison is not tied to a vendor.

The short answer

A CRM for general contractors has to track bids, not leads. That means every bid invitation and due date, the go or no-go call and why, the owners and architects who send you work, the subs you count on for coverage, and a clean handoff to the PM at award. For most 5 to 50 person GCs, a general CRM such as Zoho, HubSpot, Salesforce or Pipedrive, set up around a bid record, does the job. A construction-specific CRM makes sense when every job already runs on that vendor's platform.

Why a GC's CRM looks different

Most CRM setups assume a simple funnel: a lead comes in, a salesperson works it, it closes or dies. A general contractor does not work that way.

Bids, not leads. Work shows up as an invitation with a hard due date. It comes from an owner, an architect, a developer or a plan room, often all four for the same project. Miss the date and nothing else matters.

Two customers per job. The owner signs the contract. The architect often decides who gets invited. If your CRM only tracks the owner, you lose sight of the relationship that sends you the next five bids.

Selling and buying at once. While you price the job for the owner, your estimators solicit bids from 20 or more trades. Win or lose, those sub relationships carry into the next bid.

In five years running a GC's CRM, the setups that worked all started from one object: the bid. Everything else (owners, architects, subs, the PM handoff) hangs off that record.

What a CRM for general contractors should track, from bid invite to closeout

Here is the cycle, stage by stage, and what the record needs at each one.

Bid invitations and due dates

Every invite becomes a bid record the day it arrives, whether it came by email, a phone call or the plan room inbox. The record holds the project name, location, owner, architect, delivery method, bid due date and time, and the walk date if there is one.

Due date is the field that matters most. Put it on the board, put it on the estimator's calendar, and build a view of every bid due in the next 14 days. If your team still learns about a due date by scrolling an inbox, this alone pays for the setup.

Bid or no-bid

Most GCs make this call in a hallway and never write it down. Write it down. A required go or no-go field, plus a short pick-list of reasons (wrong size, wrong owner, no capacity, too many bidders, scope outside our work), turns a gut call into data.

After a year you can see which no-bid reasons repeat and which "go" bids you never had a shot at. That list is worth more than any feature on a vendor's comparison page.

Owners and architects

Treat owners and architects as accounts with their own history, not as fields on a bid. Link every bid to both. Then you can answer the questions an owner actually asks: How many times has this architect invited us? How many did we win? When did we last talk to them outside a bid?

For a 5 to 50 person GC, repeat architects and owners are usually the cheapest work you will ever win. The CRM should make it obvious when one goes quiet.

Sub records

Subs are a second relationship database that most GCs keep in a spreadsheet or in each estimator's head. Put them in the CRM as companies with a trade, service area, union or open shop, prequal status, bonding capacity if you track it, and a link to every bid they priced for you.

The payoff shows up at bid time. Sub coverage by trade sits right on the bid record, so you see the three trades with no numbers two days before the due date, not two hours before.

Award and handoff to the PM

When you win a bid, the record should flip to a job and land on the assigned PM with everything the estimator knew: final number, scope notes, exclusions, the owner and architect contacts, and the subs carried in the number.

This is where most GC CRMs break. The estimator moves on to the next bid, the PM starts from the contract and an email chain, and the context is gone. If you run projects in Procore or another project tool, this is also the moment to create the project there, so nobody types the same job twice.

Closeout and the next pursuit

At closeout, log the final contract value, change order total and a short note on how the owner and architect were to work with. That note is what your team reads before the next invite from the same people.

The reports an owner actually reads

Owners don't read dashboards with 20 tiles. In my experience they read four things, usually on Monday morning.

Bids due in the next 14 days. Project, due date, estimator, and sub coverage.

Hit rate by owner and architect. Not one company-wide percentage. The split by relationship tells you where to spend preconstruction time.

Backlog and pipeline. Awarded work not yet started, plus submitted bids still waiting on a decision, by month.

No-bid and loss reasons. What you passed on and why, and what you lost and to whom, when you know.

If a report needs someone to update a spreadsheet first, it will be stale by the second week. Build these from the bid record so they fill themselves.

Procore's CRM, bid and prequal tools, and where they stop

Procore is project management software first. For years the honest answer to "is Procore a CRM" was no. That changed: Procore now markets a construction CRM alongside its preconstruction tools, so it is worth knowing what each piece does and where it stops.

Bid Management handles the buying side. Your team creates bid packages, invites subs, and levels the numbers that come back side by side. It does not track your own pursuit of the owner.

Prequalification sends qualification forms to trade partners and lets you approve or deny them. It sits on the sub side too.

Procore's CRM covers the selling side, and Procore sells it separately, not bundled with Bid Management or Prequalification. Procore describes it as tracking leads, bid hit rates and pipeline, and converting won bids into active projects with the history carried over. That handoff is the strongest reason to use it, and it only pays off if every job already runs in Procore.

Where it stops: owning Bid Management or Prequalification does not get you the CRM, Procore does not publish CRM pricing, and the module is built around Procore's own project data. If your company runs projects in Procore and has someone doing business development full time, put Procore's CRM on your demo list. If you run jobs in something else, or in spreadsheets, a general CRM that creates the Procore project at award through its API or Zapier gets you most of the same handoff.

The same logic applies to other construction-specific CRMs. A dedicated bid-board product can be worth it for a GC that hard-bids dozens of public jobs a month with a full estimating department. For most 5 to 50 person GCs, a general CRM set up around a bid record fits better and costs less to change later.

Where Zoho, HubSpot, Salesforce and Pipedrive fit

All four can run a GC's bid pipeline. They differ in how far you can bend them to hold bids and subs as their own records, and how much setup that takes. This section skips prices; for pricing, see Zoho CRM vs HubSpot for contractors.

No prices here. Plans and prices change often; see the Zoho CRM vs HubSpot comparison linked above.

Zoho CRM. Professional is the edition where the two pieces a GC needs come together. Custom modules let you build a real Bids module and a Subcontractors module instead of forcing both into Deals and Accounts, and Blueprint, which starts at Professional, can enforce the go or no-go step before a bid moves to estimating. It takes more setup and training than HubSpot, and that setup decides whether the team uses it.

HubSpot. The easiest of the four to get an office team using. On lower tiers, bids live as deals and subs as companies with a trade property, which works for a small GC. Custom objects for a true bid or sub record need an Enterprise subscription somewhere on the account.

Salesforce. The most flexible, and the most work. Custom objects, record types and approval steps can model almost any GC process. It fits multi-office GCs with a person who owns the admin work. Without that person, it drifts.

Pipedrive. The simplest. A bid pipeline with due-date fields and organizations tagged by trade gets a small GC off spreadsheets in a week. It has no custom objects, so bids stay as deals and the sub database stays thin.

How to start without a six-month rollout

You don't need every field on day one. You need the bid record and the habit of using it.

1. 01

   Pull 12 months of bids

   Export every invite from email and the plan room inbox into one list: project, owner, architect, due date, result.

2. 02

   Build one bid record

   Create the bid record with five stages: Invited, Go or no-go, Estimating, Submitted, Awarded or Lost.

3. 03

   Require the go or no-go call

   Make the decision and its reason required before a bid can move to Estimating.

4. 04

   Link owners, architects and subs

   Load your repeat owners and architects as accounts and your core subs by trade, then link them to open bids.

5. 05

   Build the four reports

   Bids due in 14 days, hit rate by owner and architect, backlog and pipeline, no-bid and loss reasons.

6. 06

   Automate the handoff

   On award, assign the PM and create the project in your project tool so nobody retypes the job.

“If the estimator has to open a second screen to log a bid, the bid never gets logged.”

The fastest test is simple: if the estimator has to open a second screen to log a bid, the bid never gets logged. Put the bid record where estimators already work, then add the owner, architect and sub links once the habit sticks.

Written by

Colin Singleton

Founder, Conduit Systems

Colin has spent five years building and running the CRM inside a major Dallas–Fort Worth general contracting firm. He started Conduit to bring the same systems to owner-operated trades and contractors.

More from Colin