How to Track Architecture and Engineering Pursuits Without a Spreadsheet: A Pipedrive Walk-Through

Pursuit tracking is the practice of recording an opportunity, its people, its stage, and its next action in one shared place. It matters when a principal’s inbox and a spreadsheet each hold part of the story. A team can then lose a deadline without anybody seeing the gap.

The moment: the public-school shortlist in two inboxes

This is an illustrative scenario. A 12-person architecture and engineering practice works on public schools, civic interiors, and private workplace renovations. A principal hears about a school modernization project from a former client. A marketing coordinator saves the solicitation link in a spreadsheet. An engineer keeps the scope questions in email. The shortlist interview date lives on a calendar.

The practice has a real opportunity, but no shared pursuit record. Nobody knows whether the team is qualified, who owns the next call, or whether the submission date changed. The failure this workflow prevents is not a bad design decision. It is a silent handoff between relationship, deadline, and action.

How Pipedrive handles it

Pipedrive brings leads, deals, customizable pipelines, activities, workflow automation, and reporting into one CRM. Its official feature overview is available at Pipedrive’s CRM features.

1. Create the pursuit. Create a lead or deal for the school modernization opportunity. Record the client, known contact, opportunity source, service fit, estimated value, submission date, and follow-up date. A sample record is School modernization | City school district | public notice | principal owner | submission 2026-09-18, with the notice link in its note.

2. Map the stages. Create a pipeline that uses the practice’s language. A useful starting set is New lead, Qualifying, Pursuing, Submitted, Interview, Won, and Lost. Define what evidence moves a pursuit from one stage to the next. Add custom fields such as Sector, Geography, Lead source, Scope, Procurement path, and Reason lost.

3. Assign activities and owners. Give the pursuit one accountable owner. Create activities for confirming eligibility, collecting consultant interest, asking a scope question, and preparing the submission. Set dates while the information is fresh. A copyable activity is Ask civil consultant to confirm stormwater scope, assigned to the engineer, with a due date before the submission date.

4. Review the pipeline. Review active pursuits by stage, owner, next activity, deadline, and estimated value. Ask which pursuits have no next activity, which submissions have no internal review, and which opportunities have remained in qualification without a decision. A useful review condition is Stage = Qualifying with no activity due date, so the team can discuss whether the pursuit has a real next move. Treat the report as a prompt for a conversation. It is not a probability-of-award oracle.

Learn more about Pipedrive CRM →

The trick to using it well

The non-obvious discipline is to make stage changes evidence-based. “Pursuing” should mean the practice has decided to invest time. “Submitted” should mean the submission was sent and its receipt is recorded. “Lost” should include a reason that will help the next review. Without those definitions, a pipeline becomes a second spreadsheet with prettier cards.

Start with the smallest useful data dictionary. Decide who can create a deal, who owns the record, and who closes it. Use one field for one idea. Do not place deadline, sector, and qualification notes in a single paragraph. Import existing records only after cleaning duplicate organizations and assigning owners. A clean handoff is more valuable than a large database.

Make each update part of the work already happening. When the principal receives a clarification, update the pursuit before forwarding the message. When the coordinator sends the submission, move the stage and attach the next review activity. When a consultant declines, record that response in the pursuit so the next reviewer sees the gap. The record stays useful when every change answers a practical question: what happened, what changed, and who acts next?

What it delivers

For the illustrative practice, the workflow creates a visible pursuit pipeline. The school modernization opportunity has a client, contact, source, scope, stage, owner, and next activity. A principal can see whether the team is still qualifying or has committed to submit.

It also creates assigned next actions. The marketing coordinator can own the submission checklist. The engineer can own a scope question. The principal can own the relationship call. Those actions remain connected to the pursuit instead of disappearing into separate inboxes.

The third output is a stage and value report. It lets the team discuss what is active, what is waiting for a decision, and what has been closed. The record makes the work reviewable. It does not promise that a pursuit will be won.

Where it fits, and where it doesn’t

Pipedrive fits a practice that needs a general CRM for opportunities, people, activities, custom fields, and reports. It can organize business-development work that currently sits in email and spreadsheets. Surrounding options include web forms, Google Workspace, Microsoft 365, workflow rules, API access, and webhooks.

The limitation is central. The firm must define its pursuit stages and data governance. Pipedrive does not validate a public opportunity, judge proposal quality, or determine the probability of award. It does not replace the solicitation, proposal file, contract repository, project-management system, or professional judgment. The practice should also decide how a pursuit is archived. Keep the final outcome, decision reason, and useful handoff context. Close stale records rather than leaving them in an active stage.

Use permissions for sensitive client information. Decide which source links and notes belong in the CRM. Review duplicate records after imports. If a won pursuit moves to project setup, map that handoff separately. A downstream project record depends on the connected system and its field mapping.

The takeaway

The useful Pipedrive pattern is simple: create the pursuit, define its evidence-based stage, assign its next activity, and review the pipeline. For a 12-person practice, that closes the gap between a principal’s relationship and the coordinator’s deadline. The CRM supplies structure; the firm supplies qualification judgment and data discipline.

Common questions

Should every lead become a deal?

No. Keep an early lead separate until the firm has enough information to decide whether it deserves active pursuit time. Define that threshold in the data dictionary.

What fields matter first?

Client, contact, source, sector, location, service fit, owner, stage, submission date, next activity, and estimated value are a practical start. Add fields only when somebody will use them.

Can Pipedrive decide whether to pursue?

No. Rules can surface missing information or assign a task. Check the opportunity against the practice’s qualifications, capacity, relationship, and strategy.

How often should the team review the pipeline?

Choose a recurring review that matches the practice’s pursuit volume. The important habit is checking stale stages, missing activities, and approaching deadlines together.

Does a report replace a pursuit meeting?

No. A report makes the questions visible. People still need to resolve ownership, scope, procurement, and relationship decisions.

What happens after a win?

Record the outcome and agree on the handoff fields. If another system receives the project record through an API, webhook, or integration, test the mapping and keep a human review step.

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