Project Stage Tracking in HubSpot: DA → Tender → Contract Let Workflow

HubSpot ships with a default deal pipeline: Appointment Scheduled → Qualified to Buy → Presentation Scheduled → Decision Maker Bought-In → Contract Sent → Closed Won/Lost. It works for SaaS sales. It is the wrong model for construction.

Construction sales does not follow the buyer's purchasing decision. It follows the project's lifecycle — and the project moves through stages whether or not you are involved. The teams that win consistently track their pipeline by where the project is, not by where the conversation is.

This is how to map the construction project lifecycle into a HubSpot deal pipeline that actually drives BD action.

The construction project lifecycle

For a commercial construction project in AU or NZ, the practical lifecycle stages are:

• DA (Development Application). The application is lodged with the local council. The architect is appointed. The developer is committed. Design is in motion. This is the earliest reliable signal that a project is real.
• Design Development. The architect is finalising drawings. The structural and services engineers are appointed. Material systems are being specified. This is the window where suppliers and specialist trades get spec'd in.
• Tender (or Pre-Tender). Tender documents go out. EOIs, RFTs, formal procurement. Trade packages are shortlisted. This is where most BD teams traditionally engage — and where competition is highest.
• Contract Let. A head contractor is appointed. Trade packages are awarded. The construction team is being assembled. This is where subcontractors, scaffolding, formwork, and other specialist trades need to be in conversations.
• Construction (or Programmed). The project is on site. Stage progress runs from earthworks through to practical completion. This is where ongoing supply, variation, and defect-period work happens.
• Practical Completion. Project hands over. Defect period starts. Specific specialist trades (e.g. defect-period work, ongoing maintenance) have one last window.

Not every project moves cleanly through every stage. Projects stall at DA. Tenders get withdrawn. Contracts get re-let. But the lifecycle is the structure your pipeline should reflect, because it is what determines which stage of conversation you should be having.

Mapping the lifecycle to HubSpot deal stages

The construction-native HubSpot pipeline most AU/NZ teams settle on looks like this:

1. Identified — the project exists in your construction data source, matches your search profile, but no conversation has started.
2. DA Stage — DA lodged. First-touch outreach has begun (CPDs, intro emails, relationship calls).
3. Design Development — drawings in motion. You are in spec conversations with the architect or engineer.
4. Specified / On Shortlist — your product or service is named in the spec or your firm is on the shortlist.
5. Tender Submitted — you have formally quoted or responded to an EOI/RFT.
6. Contract Let / Awarded — the head contractor is appointed and trade packages are being awarded. (For suppliers, this is where you confirm spec wins. For subcontractors and trades, this is where the BD work happens.)
7. Closed Won — you won the package.
8. Closed Lost — you lost the package.
9. Closed Stalled — the project paused or was cancelled before a decision. Different from lost; it may come back.

This pipeline does two things a generic SaaS pipeline does not:

First, it maps to the project, not the conversation. When a project moves from DA to Design Development, your HubSpot deal should move with it — even if you have not had a meeting yet. The data tells you what stage of pursuit to be in.

Second, "Closed Stalled" is a real stage. Construction projects stall for months and come back to life. If they sit in "Lost" they get forgotten. Stalled is its own category, with its own follow-up cadence.

The custom properties this requires

Mapping stages is the easy part. Making the pipeline useful requires custom properties on the deal record. The minimum set:

• Project value (currency). Estimated value of the construction project, not your potential revenue from it. Used for filtering and prioritising.
• Project type (dropdown). Commercial high-rise, fitout, industrial, civil, residential. Match your search profile categories.
• Project stage (dropdown). Mirrors the lifecycle: DA, Design Development, Tender, Contract Let, Construction, Practical Completion. Different from your deal stage — this is the project's stage, regardless of where you are in the pursuit.
• State / region (dropdown). NSW, VIC, QLD, WA, SA, NT, TAS, ACT, NZ. Drives owner assignment and reporting.
• Suburb (text). Free text for the project location.
• Appointed architect (HubSpot Company association). Links the architectural practice to the deal.
• Appointed builder (HubSpot Company association). Links the head contractor (when appointed) to the deal.
• Source project ID (text). The unique ID from your data source (Cordell project ID, for example). Used for de-duplication and re-sync.

For suppliers and trades that win at design stage, add: Appointed structural engineer and Appointed services engineer as Company associations.

For subcontractors and trades that engage post-Contract Let, add: Appointed PM and Appointed estimator as Contact associations on the appointed builder company.

The workflows that make this run

Custom properties + custom stages create the structure. Workflows make it operate without manual intervention:

• Auto-create deal on new project. When a new project matching your search profile lands in HubSpot, create a deal at "Identified" stage with the project metadata, owner assigned by region, and the appointed stakeholders linked as Companies.
• Move deal stage when project stage changes. When the project moves from DA to Design Development externally, the HubSpot deal stage updates automatically (with rep notification, so they know it is time for the next conversation).
• Closed Stalled re-activation. When a project that was Closed Stalled shows new activity (stage change, new contractor appointed), move it back to its current stage and notify the owner.
• Owner notifications. Reps get a HubSpot task or email when a deal in their pipeline reaches a stage that needs action (e.g. project hits Tender Released).

This is where a construction project data integration earns its keep. Manually maintaining this workflow across 60+ active projects is a job. Connecting your project data source to HubSpot so the data flows automatically takes the work to almost zero.

Pipeline reporting that drives action

Once the pipeline is mapped correctly, the reporting that drives BD action becomes obvious:

• How many projects in your patch are at DA stage right now (vs last quarter)?
• Of your wins last quarter, at what stage did you first engage? (Identified → DA → Design Development → Tender — track the average.)
• What is your spec-to-quote rate? Of projects where you got specified, how many resulted in a quote? Where are the leaks?
• Which architects, engineers, or builders are appearing on your wins? (Build a tier-one list of relationships from this report.)

None of this works without the underlying pipeline structure. But with the right structure in place, the reporting flows out automatically — you do not have to ask anyone to fill in a spreadsheet.

If you want help mapping the construction project lifecycle into your specific HubSpot setup — or setting up the workflows that keep deal stages in sync with project stages — book a 15-minute call. We will look at your current pipeline and what would change.