Close or Pipedrive for a Commercial Architecture Studio's Pursuits
A design studio wins commercial work through RFQs, invited competitions, and relationships with developers and general contractors built over years of finished buildings, not through cold calling. That makes the shape of a studio's pipeline closer to a civil engineering firm's pursuit process than a typical B2B sales funnel.
Here's a walkthrough of a studio tracking one competitive pursuit end to end, since that's a more useful way to compare Close and Pipedrive for this kind of firm than a straight feature list ever would be.
Vendors Covered in this Article
Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.
The Pursuit Begins With an RFQ or Invitation
A developer's RFQ arrives, or your studio gets invited to submit qualifications for a shortlist. Log it immediately with its deadline, then make an early qualifications-and-capacity call: does this project fit the studio's portfolio story, and does the team have the bandwidth to do the submission justice. Pipedrive's board makes this first stage visible to every principal, not just whoever the RFQ landed with first.
Building the Team and the Story
Commercial pursuits often require assembling a team: structural and MEP engineers, a landscape architect, sometimes a specialty consultant for a particular building type. Track who's teamed on each pursuit as a note or field on the deal, since that team composition is frequently a deciding factor when a developer compares two similarly qualified studios, and knowing which consultants have worked well together on past projects speeds up the next team-building conversation considerably.
Where Close Could Fit a Studio Instead
A smaller number of studios do run active business development calling, staying in touch with developers, brokers, and general contractors to be top of mind before an RFQ is even issued. If that's a real, staffed function at your studio rather than an occasional principal phone call, Close's dialer and call logging support that relationship-building cadence better than a stage-based board built for tracking deadlines.
The Interview Stage Deserves Its Own Tracking
A shortlist interview is often the real deciding moment in a commercial pursuit, more than the written submission itself. Treat it as a distinct stage with its own preparation checklist, not just a line item inside proposal development, and after the interview log what the panel asked and how the studio answered so the next pursuit's team can prepare better rather than starting from nothing.
A Worked Example: Two Competing Pursuits, One Deadline Week
Say two RFQs land in the same week, both due in three weeks. A shared, visible board lets the studio's principals see both pursuits side by side and make a deliberate call about resourcing, rather than one pursuit quietly getting less attention because it wasn't top of anyone's inbox. This is precisely the kind of collision a spreadsheet updated inconsistently by different people tends to miss.
What the Pipeline Software Won't Do
Average B2B win rates across sales-led industries sit near 19 percent1, a figure worth knowing but not a great match for architecture, where a strong studio's real differentiator is portfolio fit, design quality, and reference projects a developer can visit in person. A cleaner pursuit board helps the studio not drop a deadline. It does not make the design work or the portfolio stronger.
Repeat Developer Relationships Are Worth Tracking Separately
A studio's best pipeline is often a short list of developers who come back project after project without a formal RFQ at all. Track these relationships on their own timeline, with periodic check-ins between active projects, since losing touch with a repeat developer between engagements is a much bigger risk to the studio's revenue than losing any single competitive pursuit, and it rarely shows up as a loss anywhere in a standard pipeline report.
Who Actually Keeps the Board Current, and What's Worth Chasing
Principals and project architects are billable, design-focused staff first, and updating a pipeline board competes with deadline-driven project work for their time. Keep the number of required fields on a pursuit small, and consider having a marketing coordinator maintain the detailed record from a principal's short verbal update rather than expecting every architect to log activity themselves in real time.
Not every RFQ that lands in a studio's inbox is worth a full submission, either. A studio stretched thin on staff capacity, or pursuing a project type well outside its portfolio strength, often loses more by chasing a long shot than it gains by occasionally winning one. Use the go or no-go decision stage honestly, and revisit last year's declined pursuits once a year to see whether the studio's instincts about which ones to chase are actually holding up against the pursuits it did win.
A studio's pursuit pipeline works best in this order:
- Log each RFQ or invitation immediately with its deadline, then make an early call on portfolio fit and team capacity.
- Record which engineers and consultants are teamed on the pursuit, since team composition often decides between two similarly qualified studios.
- Treat the shortlist interview as its own stage with a preparation checklist, and log what the panel asked afterward.
- Review competing pursuits side by side when deadlines collide, so principals can decide resourcing deliberately.
- Track repeat developer relationships on their own timeline, with periodic check-ins between active projects.
What Good Looks Like
A well-run studio pursuit process logs every RFQ or invitation immediately with its deadline, makes a deliberate resourcing decision when pursuits overlap, and debriefs every shortlist interview so the next pursuit team can prepare better.
Building The Capability (5-Stage Skill Ladder)
How to Get Started
Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.
Close fits a studio that staffs an active business development function making regular calls to developers, brokers, and general contractors between formal pursuits.
Pipedrive fits most commercial studios, where the core need is a visible board tracking RFQ deadlines, team composition, and interview stages.
Frequently Asked Questions
How many active pursuits should a mid-sized studio expect to track at once?
It varies widely by studio size and specialty, but many mid-sized commercial studios run somewhere between five and fifteen active pursuits at a given time, which is exactly the range where an informal tracking method starts to break down.
Should past project references be stored inside the CRM?
Keep the finished materials, project sheets, photography, and reference contacts, in a dedicated portfolio library, and link to them from the pursuit record rather than duplicating them inside Close or Pipedrive.
Does a studio need call recording features from Close?
Only if a meaningful share of business development happens over the phone. Most commercial architecture relationships are built through in-person meetings, site visits, and design presentations, where recording adds little value.
Sources
Where we quote a benchmark, we show its source. Other figures in this guide are estimates or general guidance, so check them against your own numbers.
- Average B2B new-logo win rate. Ebsta x Pavilion 2025 GTM Benchmarks Report, 2025.
Related Guides
Tracking Fee-Based Origination Credit at a Design Studio
Nobody at a design studio calls it a commission, but the fee changes after award and the payout math gets redone by hand each time. Here's the fix.
Two Ways to Track Client Retention at an Architecture Studio
Comparing a Gainsight or ChurnZero platform approach against a lightweight tracker for commercial architecture and design studio client retention.
Apollo vs ZoomInfo for Architecture Studios: Who's Behind the LLC
A developer is often a single-purpose entity with no public record. Here's how an architecture studio should think about Apollo versus ZoomInfo.
The Referral Network an Architecture Firm Doesn't Realize It Has
A lost developer relationship often traces back to an invisible consultant introduction. See what PartnerStack and Crossbeam solve for a design studio.
Scratchpad vs Dooly for an Architecture Practice
Commercial architecture pursuits run for months through programming and interviews. See how Scratchpad and Dooly fit that longer, relationship-driven cycle.
Does Cold Email Even Fit an Architecture Studio?
Studios win work through shortlists, which makes cold email feel beneath the practice. An honest look at Lemlist versus Instantly for design studios.