Subcontractors connect construction bidding software to HubSpot by identifying each job with a matching key, creating one HubSpot deal per job, and attaching every general contractor's invitation to that deal as a labeled company association. The bidding tool stays the source for plans, specs, and addenda, and HubSpot holds the job, the GC relationships, and the result.
That structure keeps the win rate honest. One job often reaches a sub as several invitations to bid (ITBs) from several GCs, and the channels add up fast. In an Autodesk survey of over 1,000 preconstruction professionals, 42% of subcontractors said they receive bid invites from three to five channels, 18% from five to seven, and 17% from over seven. When each invitation becomes its own record, the pipeline shows five jobs where one exists.
Subcontractors connect construction bidding software to HubSpot in three moves: match each incoming bid invitation to a job, write the job's details to one deal, and associate the inviting GC to that deal. The connection route can be an import, an email workflow, middleware, or a custom integration, and the matching rule stays the same across all of them.
Here's an illustrative example of three invitations for one job:
| Invitation | GC | Project name as sent | Job-site address | Bid due date |
|---|---|---|---|---|
| ITB 1 | Ridgeline Builders | Eastside Medical Office | 1400 E 7th St, Austin, TX 78702 | March 12 |
| ITB 2 | Calder Construction | Eastside MOB, Phase 1 | 1400 East 7th Street, Austin, TX 78702 | March 12 |
| ITB 3 | Northgate GC | E 7th Medical Office Bldg | 1400 E. 7th St., Austin, TX 78702 | March 14 |
All three share one job-site address once it's normalized, so they become one deal with three Invited by associations.
Construction bidding software receives bid invitations, hosts plans and specs, tracks addenda, and helps subs decide which jobs to bid and when bids are due. Some tools also let subs submit proposals directly to the GC.
Subs usually work across three kinds of tools:
| Tool category | What it does for a sub |
|---|---|
| ITB platforms | GCs send invitations, plans, and addenda through the platform, and subs respond there |
| Bid boards | Collect invitations from several sources into one list with due dates and bid/no-bid status |
| Estimating suites | Handle takeoffs and pricing, sometimes with bid tracking built in |
Email still carries a share of every sub's invitations. The same Autodesk survey found 33% of subcontractors were tracking bid invites in email and 22% in spreadsheets.
Every invitation for the same job should land on one deal because the deal represents the work your firm might win, and each GC is a path to that work. One deal per job gives you an honest count of jobs bid and jobs won.
When each invitation becomes its own deal, three things go wrong at once. The pipeline counts the same job several times, the win rate drops because you can only win the job through one GC, and estimators lose track of which GC sent the latest addendum. Our article on bid management software for subcontractors covers the counting rules in detail.
Your bidding software owns the documents and the bid workflow, and HubSpot owns the job record, the GC relationships, and the reporting. Each system keeps the data it handles best, and the connection passes only what the other needs.
| Data | System of record | Why |
|---|---|---|
| Plans, specs, and addenda files | Bidding software | Files change often and live where GCs post them |
| Takeoffs and pricing detail | Estimating or bidding software | Estimators work there every day |
| Proposal and bid forms | Bidding software | Submission happens on the GC's platform |
| Job record and job-site address | HubSpot | One deal per job connects every invitation |
| GC relationships and contacts | HubSpot | Companies and contacts carry history across jobs |
| Bid decision, bid amount, and result | HubSpot | These drive pipeline and win rate reporting |
| Win rate and bid value by GC | HubSpot | Reports roll up across every job and GC |
Our bid tracker article walks through building the deal pipeline, properties, and associations that hold this data.
A job matching key is a single value that identifies one job, built from the normalized job-site address, project name, and bid timing. Every connection route checks the key before it creates anything, so a second invitation finds the existing deal.
Start with the job-site address, since GCs rename projects but rarely move them. A practical format combines the ZIP code, the normalized street address, and the bid month.
| Part | Normalization rule | Example |
|---|---|---|
| ZIP code | First five digits | 78702 |
| Street address | Uppercase, no punctuation, standard abbreviations (STREET to ST, EAST to E) | 1400E7THST |
| Bid month | Year and month of the earliest bid due date | 2026-03 |
| Job key | Join with a separator | 78702-1400E7THST-2026-03 |
When your bidding platform assigns one project ID that every GC's invitation shares, store that ID too and use it as the first match. Confirm with your vendor that the ID stays the same across GCs before you rely on it.
Create a single-line text deal property called Job key and set it to require unique values. Per HubSpot's guide to setting validation rules for properties, each object can hold up to ten unique value properties, and the setting is configured when the property is created. A unique Job key blocks a second deal for the same job at the moment someone tries to create it.
Keep the job-site address in its own deal properties as well: street, city, state, and ZIP. Separate fields make the key easy to rebuild, and they support maps and reports by region.
Exact matches attach automatically. Near matches go to a person.
| Situation | Rule |
|---|---|
| Job key matches an open deal | Attach the invitation to that deal |
| Same ZIP and street number, different street spelling | Send to the review queue |
| Same normalized project name and city, bid dates within 30 days | Send to the review queue |
| No match | Create a new deal with the Job key |
Run the review queue from a Match status deal property with the values Matched, Needs review, and New job, and give one estimator the job of clearing it each day.
Map the invitation fields your team uses to decide, bid, and report, and leave files and pricing detail in the bidding tool. The field map below is a starting point you can adapt.
| Invitation field | Source | HubSpot object and property | Sync direction |
|---|---|---|---|
| GC company | ITB sender | Company record, associated to the deal with an Invited by label | Bidding tool to HubSpot |
| GC estimator name and email | ITB sender | Contact record, associated to the GC company and the deal | Bidding tool to HubSpot |
| Project name | ITB | Deal name and Project name property | Bidding tool to HubSpot, first invitation sets it |
| Job-site address | ITB | Deal properties for street, city, state, and ZIP | Bidding tool to HubSpot |
| Bid due date | ITB | Bid due date deal property, earliest active date | Bidding tool to HubSpot, updates on change |
| Invitation date | ITB | First invitation date deal property | Bidding tool to HubSpot |
| Trade or scope | ITB | Trade or scope deal property | Bidding tool to HubSpot |
| Project type | ITB | Project type deal property | Bidding tool to HubSpot |
| Estimated value, if given | ITB | Estimated project value deal property | Bidding tool to HubSpot |
| Plan link | Bidding tool | Plan room link deal property | Bidding tool to HubSpot |
| Addenda count | Bidding tool | Addenda count and Last addendum date deal properties | Bidding tool to HubSpot |
| Bid/no-bid decision | Estimator | Bid decision deal property | Set in HubSpot, or synced from the bid board |
| Bid amount | Estimating or bidding tool | Deal amount | Bidding tool to HubSpot |
| Result | GC award notice | Deal stage, plus an Awarded GC label on the winning GC | Set in HubSpot |
| Platform project ID | Bidding tool | Platform project ID deal property | Bidding tool to HubSpot |
Plans, specs, addenda files, takeoffs, bid forms, and proposal documents stay where the GC posted them. The Plan room link property gives estimators one click from the deal to the files.
Association labels name each GC's role on the job. Per HubSpot's guide to creating and using association labels, custom labels need a Professional or Enterprise subscription, and each object pair holds up to 50 labels. A deal-to-company set of Invited by, Awarded GC, and Invitation withdrawn covers the common cases.
Want a second look at your bid data model? The Architecture Blueprint maps your current HubSpot setup against where it needs to be, including the deal properties and labels behind a clean bid pipeline.
Choose the simplest route that matches how your invitations arrive and what your bidding tool exposes. Each route below uses the same job key and field map.
| Route | How it works | Effort | Best fit | Limits |
|---|---|---|---|---|
| Marketplace app or native connector | Install a listed app and map fields to deals and companies | Low | Your bidding tool has a confirmed HubSpot listing | Exists only for some tools, and its matching rules may create one deal per invitation |
| Import from an export file | Export invitations from the bidding tool and import them into deals, using Job key as the unique identifier | Low to medium | Tools with a reliable spreadsheet export and a weekly review rhythm | Runs on a schedule, and labels on imported associations need Professional or Enterprise |
| Email forwarding plus workflows | Forward each ITB email to HubSpot's forwarding address, then an estimator creates or links the deal | Low | Teams whose invitations arrive mostly by email | Forwarding logs the email to the GC contact, and deal creation stays a manual step |
| Middleware or iPaaS | A connector watches the inbox or the tool, parses fields, finds the deal by Job key, and creates or updates it through HubSpot's APIs | Medium | Several sources and no listed app | Parsing rules need upkeep, and usage costs grow with volume |
| Custom API integration | Code connects the bidding tool's API or webhooks to HubSpot's APIs, including matching logic and sync back | High | Multiple platforms, complex matching, or a custom interface for estimators | Needs a technical owner and depends on the vendor's API access |
According to HubSpot's guide to logging email with the BCC or forwarding address, a forwarded email logs to the original sender's contact record with its attachments, and HubSpot creates a contact for a new sender unless their address or domain sits on your Never Log list. Confirm any marketplace app or native connector on the HubSpot App Marketplace and in your vendor's documentation before you plan around it.
| Route | Needs from the bidding tool | Common gap | Sign it's working |
|---|---|---|---|
| Marketplace app or native connector | A HubSpot listing with deal and company mapping | One deal per invitation | Second GC invitations attach to existing deals |
| Import from an export file | A spreadsheet export with GC, project, address, and due date | Inconsistent address formats in the export | The import updates existing deals by Job key with no new duplicates |
| Email forwarding plus workflows | Invitations that arrive as email | Forwarded emails log to a contact, so someone still links the deal | Every ITB email appears on the GC contact within a day |
| Middleware or iPaaS | Email access or an API with project fields | Parsing breaks when a GC changes its email template | The review queue stays small and clears daily |
| Custom API integration | An API or webhooks with stable project IDs | Rate limits during busy bid weeks | Deals update within minutes of a new invitation or addendum |
An import, email forwarding, or a listed app covers firms with one or two invitation sources and a manageable weekly volume. Our HubSpot integration development services cover standard connectors, workflows, imports, and configuration. When matching logic needs unusual transformations, email parsing runs across several platforms, or estimators want a custom interface, Brainstem Ventures by Campaign Creators adds custom capabilities that connect to your existing systems. It's a specialized software engineering capability within Campaign Creators, built to keep the systems that work and engineer what's missing.
Handle every follow-up event on the existing deal: a second GC adds an association, a date change updates a property, and an addendum updates a count. New deals only appear for new jobs.
| Event | What happens in HubSpot |
|---|---|
| A second GC sends the same job | The Job key matches, the GC company is associated with an Invited by label, and a GC invitation count property goes up by one |
| A GC moves the bid due date | The Bid due date property updates if it's the earliest active date, and the estimator gets a task |
| An addendum arrives | Addenda count goes up, Last addendum date updates, and a task goes to the estimator when the bid is due within five business days |
| One GC withdraws its invitation | That GC's label changes to Invitation withdrawn, and the deal stays open for the other GCs |
| Every GC withdraws | The deal moves to a No bid, withdrawn stage |
| The job is rebid after a cancelled award | A new deal opens with the Job key plus a round suffix, such as 78702-1400E7THST-2026-03-R2 |
Workflows can create the tasks and update the counts. Per HubSpot's guide to setting up and managing pipelines, custom pipelines need a Starter, Professional, or Enterprise subscription, so the bid pipeline and its No bid, withdrawn stage fit any paid tier.
Sync bid status and results from the bidding tool into HubSpot, and send GC relationship context from HubSpot back to estimators where it helps the bid decision. Results feed the win rate, and relationship context sharpens the next bid/no-bid call.
Sync the submitted date, bid amount, and any award or loss notice the platform records. When the result arrives outside the platform, the estimator updates the deal stage and sets the Awarded GC label on the winning GC.
Estimators make better bid/no-bid calls when they can see a GC's history: past awards, jobs bid with that GC, and win rate. Show that context on the GC company record and in a report estimators open before each decision. When your bidding tool's API accepts custom fields, a workflow can send the values over. Per HubSpot's guide to using webhooks in workflows, the webhook action needs a Data Hub Professional or Enterprise subscription.
Ask how your invitation data leaves the platform, how often, and with which identifiers. The answers decide which connection route you can use.
One deal per job unlocks an honest win rate: jobs won divided by jobs bid, with bid value and results broken out by GC. Without the matching key, every extra invitation inflates the denominator.
| Report | Built from | Question it answers |
|---|---|---|
| Jobs bid and jobs won | Deals in the bid pipeline by stage | What's our real win rate across jobs? |
| Win rate by GC | Awarded GC and Invited by labels | Which GCs award us work most often? |
| Bid value by GC | Deal amount and Invited by labels | Where does our bid volume go? |
| Invitations per job | GC invitation count property | How many GCs carry each job to us? |
| No-bid reasons | Bid decision and reason properties | Which jobs do we pass on, and why? |
Our article on bid management software for subcontractors covers how to count jobs, invitations, and awards so these reports hold up.
Subcontractors connect construction bidding software to HubSpot by matching each bid invitation to a job with a Job key, writing the job to one deal, and associating every inviting GC with a labeled association. The bidding tool keeps plans, specs, addenda, and pricing, and HubSpot keeps the job, the GC relationships, and the result. Pick the simplest connection route your vendor's data access supports, handle duplicates and addenda on the existing deal, and the win rate by GC becomes a number your team can trust.
Campaign Creators scopes and builds the connection between your bidding tools and HubSpot, from the Job key and field map to the route that fits your vendors. As a HubSpot Elite Solutions Partner, we apply CRM and integration architecture expertise to the way subcontractors receive and win work.
We map your invitation channels, set up the deal properties and labels, build the import, workflow, or integration, and deliver the win rate reports your preconstruction team uses every week.