How to Build an Architecture Business-Development Pipeline with HubSpot: A HubSpot Walk-Through

An architecture business-development pipeline is a shared way to turn firm relationships and pursuits into records, stages, next actions, and a reviewable picture of work in motion. It matters when opportunity knowledge sits in a principal’s inbox or a spreadsheet: the firm can have a good conversation and still lose the next follow-up because nobody owns it.

Most small architecture and engineering practices grow on repeat clients and referrals, and for years that is enough. It is also why they plateau. When three or four clients account for most of the fees, the firm grows at the pace of those clients’ own cycles, and one client pausing a programme becomes the whole firm’s slowdown. Business development is not cold-calling. It is treating relationships and pursuits as a system that is recorded, staged, owned, and reviewed, so the next project is being worked before the current one ends. Firms that run it this way are not luckier. They are earlier.

HubSpot’s CRM features organize that work around connected records, stages, tasks, and reports.

The moment: the shortlist follow-up that never happened

This is an illustrative scenario. A small architecture practice pursues a mix of public school work and repeat private-developer clients. A principal keeps relationship context in email. A shared spreadsheet holds pursuit names, rough status, and a few dates. The team reaches a shortlist interview for a public school project, then the follow-up email never happens. The practice loses the opportunity without a single place showing who owned the next contact.

The failure is not simply that someone forgot. The spreadsheet describes an opportunity, while the inbox contains the relationship and the calendar contains the meeting. Those pieces do not form a dependable handoff. The useful workflow is to import the firms and people, give each pursuit a defined stage, put a named next action on the record, and review the pipeline often enough to catch stalled work.

How HubSpot handles it

HubSpot’s documentation describes company records, contact records, and deals as connected CRM objects. A company can be associated with contacts and deals, and activities can be kept with associated records. Deals track potential revenue through a sales process and can be associated with the companies and contacts involved. The CRM product page is the starting point for the platform overview: see HubSpot CRM.

1. Import relationships. Start with company and contact records, then bring in the firm’s existing relationship data rather than asking principals to recreate it from memory. HubSpot’s company documentation says companies can be imported when moving from another CRM, and the record can be associated with contacts and deals. Use those standard objects for the developer, school district, consultant, or other organization; use contacts for the people the practice actually knows. The official guide is Create companies.

   Give the relationship a small, agreed set of fields: organization name, contact role, market or client type, relationship owner, last meaningful touch, and context worth carrying forward. If the team needs AEC-specific information, create custom properties deliberately. HubSpot defines properties as fields that store information on records and documents that custom properties can hold data unique to the business. Read Create and edit properties before designing the import.

   Example company record: Name: Northside School District; Client type: Public school; Relationship owner: Maya Chen; Last meaningful touch: Shortlist interview.

2. Define pursuit stages. Represent each active pursuit as a deal, associate it with the relevant company and contacts, and use a pipeline to show its current position. HubSpot’s deal documentation says deals track potential revenue through a sales process and can be associated with contacts and companies. Its board-view documentation describes records moving through stages in a pipeline. For this practice, a deliberately plain stage set might be Lead identified, Qualified, Pursuing, Shortlisted, Interview complete, Won, or Lost. The exact labels are the firm’s governance decision; the value is that “shortlisted” means the same thing to everyone.

   Add properties that make a pursuit reviewable: project or procurement name, client type, anticipated decision date, pursuit owner, next milestone, and reason lost. Do not hide procurement nuance in a long notes field. A custom property should have one clear meaning and an owner who keeps its values clean. See Create and edit properties and Manage records in board view.

   Example deal record: Project or procurement name: Northside High School; Client type: Public school; Pursuit owner: Maya Chen; Deal stage: Shortlisted; Next milestone: Interview follow-up.

3. Assign follow-ups. Put the next action on the person and pursuit while the meeting or interview is still fresh. HubSpot’s sequence documentation describes automatic task reminders alongside email steps, and its deal documentation describes activities being associated with related records. For a shortlist interview, the task might be “send thank-you and confirm procurement questions,” assigned to the principal who owns the relationship, with the deal and contact attached.

   Sequences may fit repeat, permissioned outreach, but they should not turn a high-trust client relationship into a generic campaign. HubSpot’s documentation says sequences can create email, call, or general task reminders and can unenroll contacts when they reply or book a meeting. For a public-sector pursuit, follow the firm’s procurement rules and communication permissions before automating anything. See Create and edit sequences.

   Sample task: Send thank-you and confirm procurement questions, associated with the Northside High School deal and its contact, assigned to Maya Chen.

4. Report pipeline. Review the deal pipeline as a management conversation, not as a decorative dashboard. Filter for stage, owner, client type, decision timing, and next-action status. HubSpot’s CRM product page describes dashboards and reporting as part of its CRM capabilities; the record itself should remain the source for the current stage, owner, and next action. A weekly review can ask: which pursuits have no next task, which shortlisted work has no post-interview action, and which relationships are attached to an opportunity but have no recent activity?

   Build views that answer those questions without inventing a probability model the practice cannot maintain. If a dashboard depends on a property, define who updates it and when. The report is only as trustworthy as the record discipline beneath it.

   Example review view: Deal stage: Shortlisted; Pursuit owner: Maya Chen; Next milestone: Interview follow-up.

Learn more about HubSpot CRM →

The trick to using it well

The non-obvious discipline is to separate the relationship, the pursuit, and the next action without separating them from one another. The company record is the durable organizational relationship. The contact record identifies the person and their role. The deal is the specific opportunity. The task is the promise the team makes to itself about what happens next. Association is what lets a later reviewer move between those pieces instead of reconstructing the story from email.

Start with a small schema and write a short data dictionary. Define what qualifies an opportunity for the pipeline, what each stage means, when a deal is marked lost, and who can change an owner or stage. Agree that a meeting is an activity, not automatically a follow-up. After every meaningful touchpoint, someone records the useful context and creates the next action. At review time, stale records are corrected rather than explained away.

That operating agreement matters more than a clever dashboard. The CRM makes the handoff visible.

What it delivers

For the illustrative practice, the workflow produces three concrete things.

First, a relationship record: the private developer or school-district organization is represented as a company, its known people are contacts, and the important interactions are connected to those records. A new BD lead can see the relationship without searching a personal inbox.

Second, a pursuit pipeline: the public school project is a deal with a named stage, owner, relevant company and contacts, milestone fields, and a visible outcome. “Interview complete” can mean something different from “Won,” and the distinction remains available when principals review the board.

Third, follow-up tasks: the post-interview thank-you, clarification call, or next meeting request is assigned to a person. If the task is overdue, that is a management signal to resolve, not an invisible gap in a spreadsheet.

The result is not a guaranteed win. It is a shared record of what the firm knows, what it is pursuing, and what it has promised to do next.

Where it fits, and where it doesn’t

HubSpot fits a practice that needs a general CRM for relationships, opportunities, activities, tasks, and reporting. It can connect contacts, companies, and deals; support imported records; provide pipeline stages; and give a team a common place to review pursuit work. Email and calendar activity can be part of the surrounding operating model, while n8n or Make can sit alongside it when the practice needs a carefully designed integration.

The limitation in the workflow record is the important one: AEC-specific relationship and procurement data requires a deliberate schema and governance. HubSpot does not decide what “shortlisted” means for a qualifications-based selection, how a public procurement rule affects outreach, which consultant relationship is conflicted, or who should own a sensitive client record. Those decisions belong to the practice.

Keep the system bounded. It is not a substitute for the solicitation documents, proposal files, contract repository, or project financial system. Design permissions around sensitive pursuits. Confirm consent and access before capturing activity or enrolling people in automated outreach. Test imports for duplicates and missing owners. Decide what information is appropriate to retain, and document the handoff when a pursuit is won or lost.

The takeaway

For an architecture practice living in a spreadsheet and an inbox, the useful HubSpot pattern is simple: connect the organization, person, pursuit, stage, and next action. The shortlist failure in the illustrative scenario is exactly the kind of gap a shared record and an assigned task are meant to expose. HubSpot can provide the CRM structure, while the practice supplies the AEC schema, permissions, and review habit.

Common questions

Should every relationship become a pursuit?

No. Keep a company or contact record for a relationship even when there is no active opportunity. Create a deal when the firm has a defined pursuit that needs a stage, owner, and review. This keeps the relationship history useful without filling the pipeline with vague prospects.

Should an architecture pursuit be a deal?

It can be a practical adaptation of HubSpot’s deal object. HubSpot documents deals as records for tracking potential revenue through a sales process, so the practice should decide whether that meaning fits its own pursuits. If some work is exploratory, use a clear qualification rule before it enters the active pipeline.

What stages should an AEC firm use?

Use stages that describe decisions the firm can observe: qualified, pursuing, shortlisted, interview complete, won, and lost are examples. Do not copy a generic sales funnel without defining its terms. A stage should tell a reviewer what has happened and what evidence permits the next move.

Can HubSpot replace the pursuit spreadsheet immediately?

It can replace the spreadsheet as the shared pipeline view, but migration should be deliberate. Clean company names, contacts, owners, stages, and duplicates first. Keep the data dictionary beside the import plan, and reconcile the first review against the old sheet so missing pursuits are found early.

Should follow-up sequences send messages automatically?

Not by default. A sequence can create reminders and automate some email steps. For a shortlist interview, a personalized task is often the safer first pattern.

What does HubSpot not know about an AEC pursuit?

It does not know the firm’s strategy, procurement constraints, relationship history that nobody recorded, or whether a project is worth pursuing.

Disclosure: DataDrivenAEC may earn a commission if you subscribe through links in this walk-through. Product behaviour is described from HubSpot’s documentation; the scenario is illustrative.