Most architects who do BD are also running projects. That structural collision, you're the one who wins the work and the one who delivers it, creates a predictable pattern: BD goes fine when things are slow, falls apart when projects are full, and you end up scrambling to refill the pipeline during the brief windows between. You've probably felt this cycle.
A different structure changes this without adding hours. Here's how seller-doers who run consistent pipelines think about their BD time and what they protect even when projects are demanding.
The Three Buckets of BD Time
BD time in an architecture firm falls into three categories, each with different rhythms, different tools, and different consequences if you let them go.
Relationship development. Staying present with contacts who might become clients, refer work, or open doors. Coffee meetings, industry events, LinkedIn visibility, follow-up on past conversations. This is the slowest-compounding bucket and the first one seller-doers cut when they're busy. It's also the one with the longest consequence lag: the relationships you stop maintaining today disappear from your pipeline 12 to 24 months from now.
Existing client growth. Staying engaged with current and past clients so they bring you more work. Proactive check-ins, sharing relevant thinking, being present at the right moments (a building anniversary, a news mention about their project, a change in their organization). The return here is faster and more certain than new business because the relationship is already built.
New business development. Identifying and pursuing net-new client relationships. This is the most time-intensive and least efficient bucket, because you're starting from no relationship. Worth doing, but worth doing thoughtfully, targeting sectors and client types where your wins are concentrated.
The principle that runs all three: BD compounds slowly. An hour of relationship investment today pays off months from now. The firms and individuals who run consistent pipelines are the ones who protect BD time even when projects don't have room for it.
The Time Allocation Question
There's no universal right answer, but there's a useful starting framework.
Firms that have studied this, including PSMJ in their annual A/E/C industry benchmarking, find that principals in high-performing firms allocate somewhere between 15 and 25% of their time to BD. The exact number matters less than the consistency: sellers who show up for BD every week, even for small amounts, outperform sellers who do intensive BD bursts followed by long droughts.
Within that BD time, a rough allocation that works for most seller-doers:
- Existing clients (growth and retention): roughly 50% of BD time. These relationships are already warm and the return rate is the highest.
- Active pursuits (go/no-go, proposal strategy, interviews): roughly 30%. This is the near-term revenue work.
- Relationship development and new business: roughly 20%. This is investing in the future pipeline.
Adjust based on where your firm sits. A firm that's well-established with a strong repeat client base can shift more time toward relationship maintenance and less toward new business. A firm trying to break into a new sector needs to flip the ratio on that last bucket.
What Eats Seller-Doer BD Time
Understanding where the time goes is a prerequisite for protecting it.
Unplanned project fire-fighting. The meeting that wasn't on the calendar, the client call that comes in during a scheduled BD block, the coordination problem that only you can solve. This is real and unavoidable. The only countermeasure is protecting BD blocks on the calendar and treating them as client meetings you can't reschedule.
Proposal assembly. When you're both the relationship owner and the proposal writer, the proposal draft ends up taking time from relationship development. The better structure: you own strategy and review, someone else does assembly. Even in small firms, separating these roles protects the senior seller-doer's time.
RFP front-end analysis. Reading a 60-page RFP to understand requirements and assess fit takes hours a coordinator could spend on better things. This is exactly where AI compresses time: extracting requirements and matching against your portfolio in a fraction of the manual time. The go/no-go decision still belongs to a person with context. The analysis that informs it doesn't.
Low-fit pursuits. Time spent writing a proposal you should have declined is time stolen from a pursuit you could have won. A consistent go/no-go discipline, even a 30-minute weekly assessment of incoming opportunities against defined criteria, recovers more BD time than most other practices.
The Weekly Rhythm That Works
The seller-doers with the most consistent pipelines have a rhythm that doesn't require heroic effort to maintain. Here's what it tends to look like.
Weekly: a short BD block. 1 to 2 hours, protected time, same slot each week. Use it for relationship follow-up, opportunity assessment, and correspondence you'd otherwise push off. The goal is maintenance, not sprints.
Monthly: a pipeline review. Who's in the relationship development stage? Which past clients are due for a touchpoint? What's moving in the active pursuit bucket? A 30-minute monthly review catches the relationships that have gone quiet before they go cold.
Quarterly: a new business focus session. A longer block, 2 to 4 hours, to think about where new work is coming from, which sectors are performing, and where to direct relationship development effort over the next 90 days. This is the strategic layer that monthly maintenance doesn't cover.
The reason this works is that it's sustainable. A seller-doer running a full project load can protect 1 to 2 hours per week without wrecking anything. They can't sustain an all-hands BD sprint that adds 20 hours on top of project work.
What AI Changes About the Rhythm
AI compresses the time cost of specific BD tasks, which lets seller-doers maintain their rhythm without sacrificing as many hours.
Faster RFP analysis means the go/no-go decision takes 20 minutes instead of 2 hours. That's a direct return to the weekly BD block.
AI-drafted follow-up emails and first-pass proposal narratives mean the seller-doer edits and approves rather than writes from scratch. Editing is faster than writing.
Client research and stakeholder profiles generated before a meeting or interview mean preparation time drops, while the quality of the conversation goes up.
None of these eliminate the judgment and relationship work that only the seller-doer can do. They eliminate the administrative work that surrounds it, which is the time that was crowding out the real BD in the first place.
Where Foveate Fits
Foveate is built for seller-doers who need to pursue more without spending more time on pursuit mechanics. It reads an incoming RFP against your firm's actual portfolio and team, returns a fit assessment that informs the go/no-go, and builds a client-specific presentation from your own content so proposal assembly doesn't consume the hours that belong in relationship development. For the post-submission stage, it prepares you for the specific stakeholders who'll evaluate your firm.
The seller-doer's time is the firm's scarcest resource. Book a demo and we'll show you where the pursuit time is going now and where it'd go instead.
Frequently Asked Questions
How much time should principals in architecture firms spend on business development? High-performing firms typically allocate 15 to 25% of principals' time to BD. Consistency matters more than total hours: sellers who show up weekly, even briefly, build better pipelines than ones who sprint and then disappear.
What are the three types of business development work for architect seller-doers? Relationship development (staying present with contacts who might become clients), existing client growth (keeping warm relationships with past and current clients to generate repeat work), and new business development (building relationships with net-new clients). Each has a different rhythm and different compounding rate.
How do seller-doers protect BD time when projects are busy? Block it on the calendar and treat it like a client meeting. Even 1 to 2 hours per week, consistently protected, outperforms irregular bursts. The second practice is separating proposal assembly from strategy: the seller-doer should own the go/no-go and the positioning, not the document assembly.
Where does most seller-doer BD time get wasted? Proposal writing for low-fit pursuits is the biggest time drain. A disciplined go/no-go process recovers more time than almost any other practice. After that: RFP front-end analysis, which AI can compress significantly without removing the human judgment on the actual decision.
What's the best way for an architect to structure their weekly BD routine? A 1 to 2 hour weekly block for maintenance and correspondence, a monthly 30-minute pipeline review, and a quarterly session for strategic new business targeting. This is sustainable alongside a full project load and compounding over time produces more consistent pipeline than periodic BD sprints.
Sources
- AIA, "New research explores perceptions and opportunities for artificial intelligence" (2025)
- Bluebeam, "Building the Future: AEC Technology Outlook 2026"
- Foveate: How Architecture Firms Win Work (BD Lifecycle)
- Foveate: Go/No-Go Decision Framework for Architecture
- Foveate RFP Research
- Foveate Stakeholder Networks
- Foveate
About the Author
Kitae Kim
Architect with 10 years of experience in design and client communication. Co-founder of Foveate, the Pursuit Intelligence Platform for AEC firms. Former studio lead who saw too many winning designs lose to worse proposals.