You’re the managing director of a 30-person architecture firm. You have 7 active projects, 14 clients, 20+ contractors and consultants, and a team of architects and designers who need your input on everything from material selections to code compliance questions.
This morning, your inbox has 94 emails. Here’s what’s in there:
A contractor on the downtown mixed-use project submitted an RFI about the curtain wall detail — it went to the project architect, who forwarded it to you because it requires a design change. A client on the residential project wants to know if the permit submission is on track — they’re asking for the third time this month. The structural engineer on the office renovation replied to a thread from two weeks ago with updated calculations, but their reply went to the original thread that you’d mentally closed. A new consultant is requesting access to project files. Your junior architect submitted a design option for the lobby that needs review. Three material suppliers sent spec sheets. Two newsletters from AIA. An invoice from a subconsultant. And a cold email from a rendering company.
Somewhere in those 94 emails is the one that actually matters today — the RFI that could delay the downtown project by two weeks if it doesn’t get answered by Friday. But it looks exactly like the other 93 in your inbox: a sender you recognize, a subject line that could be routine or critical, and no way to know without opening and reading it.
This is the architecture firm email problem. Not volume. Fragmentation.
Architects spend 2+ hours per day managing email
Industry research from EntreArchitect and broader workplace studies show architects spend 2+ hours daily on email management. For firm principals managing client relationships, contractor coordination, and internal design reviews simultaneously, the time investment is often higher. At principal billing rates of $150-$300/hour, this represents $300-$600/day in opportunity cost — time not spent on design, client development, or strategic firm management.
EntreArchitect research; McKinsey workplace communication studiesWhy Architecture Firms Have a Unique Email Problem
Architecture is a communication-intensive profession in a way that other industries aren’t. Every project involves a constellation of stakeholders — client, contractor, structural engineer, MEP consultant, landscape architect, interior designer, code reviewer, permit officer — and they all communicate via email. A single project might have 20-30 active email threads at any given time. Seven projects means 150+ threads. And they’re not simple threads.
The RFI cascade
One RFI — a contractor asking about a floor drain detail — becomes five conversations. The contractor emails the project architect. The project architect forwards to the principal for a decision. The principal emails the structural engineer for input. The structural engineer replies with questions. The principal answers those questions. The structural engineer provides revised calculations. The principal emails the project architect with the updated detail. The project architect responds to the contractor.
That’s eight emails across four people for one question. Multiply by the 3-5 RFIs that arrive weekly on an active construction project, and you have 20-40 email exchanges just for information requests — on one project.
“One RFI quickly turns into multiple conversations, with questions forwarded, replied to, or partially answered in different threads,” as Newforma, the architecture project management firm, describes it. “RFIs often get buried in overflowing inboxes, lost in file folders, or scattered across communication platforms.”
The RFI that gets buried isn’t just an inconvenience. It’s a construction delay. A contractor waiting on an RFI response can’t proceed with that scope of work. A two-day email delay becomes a two-day construction delay. On a project with a $50,000/day general conditions cost, a buried RFI has real financial consequences.
The multi-stakeholder thread problem
Architecture email doesn’t follow clean lines. A client emails the principal about a design concern. The principal copies the project architect. The project architect responds with a technical explanation. The client replies only to the principal (not the project architect) with a follow-up question. The principal forwards to the project architect for input. The project architect responds to the principal. The principal paraphrases the response back to the client.
Now there are two parallel threads about the same issue — one between the client and the principal, one between the principal and the project architect. The information in them overlaps but isn’t identical. When the client brings up the issue in next week’s project meeting, the principal has to reconstruct the conversation from two separate threads.
“Email doesn’t manage deadlines or ownership,” as one project information management firm puts it. It’s a communication channel — not a coordination tool. But architecture firms use it as both, because it’s where their stakeholders communicate.
The long-project problem
A residential project takes 12-18 months. A commercial project takes 2-5 years. Over that timeline, a single project generates thousands of emails across dozens of threads. When a question comes up in month 14 about a decision made in month 3, someone has to search through those thousands of emails to find the relevant exchange.
“Finding crucial emails feels like searching for a needle in a haystack,” as Planman, another project management platform, describes it. And in architecture, finding that needle isn’t optional — it’s the difference between honoring a design decision and making a costly revision based on forgotten context.
The creative-professional-turned-business-owner problem
Most architecture firm principals didn’t start their careers wanting to manage email. They started their careers wanting to design buildings. Somewhere along the way, the firm grew, the client load increased, the contractor base expanded, and the principal’s job shifted from design to communication management.
This is the Jeremy Robinson problem — a managing director who chose architecture for creative work and now spends most of their day coordinating communication between clients, contractors, and internal teams. The skills that built the firm (design thinking, spatial reasoning, creative problem-solving) are not the skills that consume most of the principal’s time (email triage, meeting coordination, follow-up tracking).
What Architecture Firms Have Tried
Project management software
Tools like Newforma, Procore, or Autodesk Construction Cloud provide structured environments for RFI tracking, document management, and submittal logging. They’re valuable for formal project documentation. But they don’t replace email — they supplement it.
Clients email. Contractors email. Consultants email. The project management tool captures the structured side of project communication — logged RFIs, approved submittals, filed documents. The unstructured side — the quick client question, the contractor’s “heads up about a site condition,” the consultant’s “can we discuss this before I finalize?” — stays in email.
Architecture firms end up maintaining two communication systems: the PM tool for formal documentation and email for everything else. The gap between them is where things get lost.
Folders and labels
The discipline approach: create a folder for every project, every client, every phase. Label emails by project and priority. Sort incoming email into the right folder.
This works when you have three projects. At seven active projects with 20+ stakeholders each, the folder system breaks down. An email from a contractor about Project A that also references Project B — which folder? A client email that’s both a design question and a scheduling inquiry — which label? The categorization becomes a task in itself, and the time spent filing exceeds the time saved by organization.
Delegation to project architects
“Let the project architect handle the email for their projects.” Reasonable in theory. The problem is that clients often email the principal directly — because the relationship is with the principal, not the project architect. Contractors CC the principal on everything because they want the decision-maker in the loop. And the consultant’s question that starts as routine often requires the principal’s judgment before it’s resolved.
The principal can delegate the response but not the awareness. They still need to read the email to know whether it requires their input. The delegation saves reply time but not triage time — which is where most of the 2+ hours goes.
What Actually Works for Architecture Firms
1. Smart triage across all project communication
Instead of reading 94 emails and deciding which ones matter, you see a prioritized view. The contractor’s RFI with a Friday deadline sits at the top. The client’s third request for a permit status update is flagged. The structural engineer’s buried reply from a two-week-old thread is surfaced. The material spec sheets, newsletters, and cold emails are at the bottom — or not visible at all.
The triage isn’t by sender or arrival time. It’s by actual urgency: Is there a deadline? Is someone blocked? Is this a client relationship that needs attention? Is this an RFI that could delay construction?
2. Follow-up tracking across projects
Every commitment you make in email — “I’ll review the curtain wall detail by Thursday,” “Let me check with the structural engineer and get back to you,” “I’ll send the updated drawings this week” — is extracted and tracked. Your Thursday morning briefing says: “You committed to reviewing the curtain wall RFI by today. The client is still waiting on the permit status update (3rd request). You promised the lobby design feedback on Monday.”
Across seven projects, you might have 15-20 active commitments at any time. No human — not even the most organized architect — can hold all of those in their head while also designing buildings. The system holds them so you don’t have to.
3. Morning briefings that replace the inbox scan
Before you open your inbox, a structured summary tells you: what arrived overnight across all projects, what’s urgent, what’s overdue, and what context you need for today’s meetings. “Client meeting at 2 PM on the residential project — they emailed last night about the material selection. Here’s the thread.”
You spend 10 minutes reading a briefing instead of 45 minutes scanning 94 emails. You start your day knowing the RFI deadline, the client follow-up, and the meeting context — without making 94 individual decisions about what matters and what doesn’t.
How alfred_ Works for Architecture Firms
alfred_ ($24.99/month) connects to your firm’s email — Gmail, Outlook, or both — and reads every message across every connected account. For a firm principal managing 7 projects, that means every client email, contractor RFI, consultant update, and internal thread surfaces in one prioritized view.
Smart triage for project communication. alfred_ evaluates every email on urgency, sender importance, and content. The contractor’s RFI with a Friday deadline surfaces above the material spec sheet that can wait a week. The client’s third follow-up about the permit status surfaces above the AIA newsletter. You see the 10-15 emails that need your attention today — not the 94 that arrived.
Morning briefing for project awareness. Every morning, a structured summary covers what arrived overnight across all projects. “Downtown mixed-use: contractor RFI on curtain wall — response due Friday. Residential: client asking about permit status (3rd request). Office renovation: structural engineer updated calculations — thread from Oct 15.” Ten minutes of reading replaces an hour of inbox archaeology.
Follow-up tracking across projects. Every commitment you make in email is extracted and tracked automatically. “Review curtain wall RFI by Thursday. Send client permit status update. Provide lobby design feedback by Monday.” Nothing slips because the system catches every promise — across every project, every thread, every reply you’ve sent.
Draft replies for routine communication. The client asking about the permit status for the third time gets a professional, patient reply that references the timeline you discussed. The contractor’s RFI acknowledgment gets a prompt response. You review and send — minutes instead of the 15-minute composition that each reply usually requires.
SMS alerts for genuine urgency. When a genuinely urgent email arrives — the contractor who discovers a site condition that requires an immediate design decision, the client who needs to reschedule tomorrow’s presentation, the permit office with a code compliance question — you get a text. You’re at a job site, in a client meeting, or at the drawing board. The urgent issue reaches you. The routine email waits.
The result isn’t that you stop doing the work of a firm principal. It’s that the administrative overhead of managing communication across 7 projects, 14 clients, and 20+ contractors gets compressed. The 2+ hours of daily email management becomes 30 minutes of briefing review and reply approval. The rest of your day goes back to design, client relationships, and the creative work that built the firm in the first place.
“Finding crucial emails feels like searching for a needle in a haystack.” It shouldn’t. Not when the system can find the needle for you.
Frequently Asked Questions
How much time do architects spend on email?
Research from EntreArchitect and industry surveys shows that architects spend 2+ hours per day managing email — consistent with the broader McKinsey finding that knowledge workers spend 28% of their workweek on email. For firm principals and managing directors, the number is likely higher because they handle client communication, contractor coordination, internal design reviews, and regulatory correspondence. At a principal’s billing rate of $150-$300/hour, 2 hours of daily email management represents $300-$600/day in opportunity cost.
What’s the best email management system for architecture firms?
The best system works on top of email rather than trying to replace it. Your clients will always email you. Your contractors will always email you. Regulatory bodies will always email you. The question is whether you manually sort, track, and follow up on all of that, or whether a system handles the administrative layer. alfred_ ($24.99/month) reads every email, prioritizes by project urgency and sender importance, drafts replies based on thread context, and tracks follow-ups automatically. It functions as the communication layer between your inbox and your project management tool.
How do architecture firms handle RFI communication?
RFIs (Requests for Information) are the highest-stakes email communication in architecture. One RFI from a contractor can spawn multiple email threads — forwarded to the project architect, copied to the structural engineer, partially answered by a junior associate, then re-asked by the general contractor who didn’t see the original response. The best approach is a system that surfaces all RFI-related emails by priority and tracks responses across threads, so nothing goes unanswered. Project management tools like Newforma help with RFI logging, but the initial communication still happens in email.
Should architecture firms use a client portal instead of email?
Client portals are excellent for document sharing, plan reviews, and formal approvals. But they don’t replace email for the majority of client communication — quick questions, schedule changes, feedback on presentations, introduction of new stakeholders. Clients default to email because it’s what they know. The firms that manage best don’t fight this — they accept that email is the primary communication channel and build systems to manage it effectively. A tool like alfred_ ($24.99/month) works on the email layer directly, triaging client messages and tracking follow-ups without requiring clients to adopt a new platform.
How do architecture firm principals manage their time?
The architect who became a firm principal faces a unique challenge: the skills that built their career (design thinking, creative problem-solving) are not the skills they spend most of their time on (email management, project coordination, business development). Most principals report spending 50-60% of their time on administrative and communication tasks, with design work squeezed into the margins. The firms where principals reclaim time for design are the ones that systematize communication — using tools to handle triage, follow-ups, and routine responses so the principal’s time goes to the work only they can do.