A modern AEC firm does not make its best people hold the whole business together in their heads. The work is easier to see, knowledge is easier to find, decisions have owners, and the tools support the team instead of creating another place to look.
Start with the size closest to your firm. Look for the problem you recognize. Then read one size backward for the foundation you may have skipped and one size forward for what is likely to break next.
Modernizing the firm is bigger than buying software
It is how leaders set direction, how work moves, how tools help, how the firm remembers what it knows, how projects become a healthy business, how expertise becomes reputation, and how relationships become work.
These are not seven independent departments. They are seven connected capabilities:
Leadership & Culture
Make priorities visible and give people room to improve the work.
Workflow & Operations
Turn recurring delivery into a visible, teachable system.
Technology & AI
Give each system a job and connect AI to governed firm knowledge.
Knowledge Transfer
Move the firm’s judgment from individual memory into daily work.
Business Model & Finance
Know which work creates value and how the firm converts effort into margin.
Positioning & Brand
Make the firm’s point of view legible before the interview begins.
Business Development
Turn relationships, evidence, and follow-through into a repeatable path to good work.
A technology decision is also a decision about the work, the people, the firm’s knowledge, the money, and how the practice grows.
This model comes from AEC practitioners, firm surveys, industry research, Office Hours questions, and workflow studies. What AEC firms are actually doing with AI provides the dated evidence. This playbook shows how the parts of the firm connect.
The 7 × 5 playbook
The five size bands are operating archetypes, not official industry categories. They make one point concrete: a solo principal, a 15-person studio, and a 150-person practice may want the same capability, but they should not build it the same way.
| Capability | Solo 1One principal | Small 5Founder-led team | Growing 15Roles taking shape | Established 50Multiple leaders | Large 150Studios or offices |
|---|---|---|---|---|---|
| 01Leadership & Culture | Protect the principal’s attention; write down the decisions only the principal can make. | Set a weekly priority rhythm and make ownership explicit instead of carrying it in the founder’s head. | Create real team leads, decision rights, and a repeatable way to surface friction from the work. | Run a leadership operating cadence across studios, delivery, finance, people, and growth. | Set enterprise guardrails while giving offices and disciplines room to adapt within them. |
| 02Workflow & Operations | Use one trusted project and task record; standardize the few recurring checklists that protect quality. | Map pursuit-to-closeout handoffs and stop rebuilding the same tracker for every project. | Define stage gates, owners, exception paths, and current-state dashboards before adding more tools. | Connect project, staffing, financial, and quality workflows so leaders can see drift before a crisis. | Manage an operating architecture across offices, disciplines, acquisitions, and shared services. |
| 03Technology & AI | Choose a secure core stack and automate one frequent, high-friction workflow at a time. | Standardize accounts, files, templates, permissions, and approved AI use before habits fragment. | Assign system owners; connect project data; build reusable workflows with human review and writeback. | Create a technology roadmap, integration layer, adoption program, and measured portfolio of automations. | Govern platforms, data, models, agents, security, and interoperability as enterprise capabilities. |
| 04Knowledge Transfer | Capture decisions, templates, details, and lessons as work happens so the practice can reuse them. | Create a shared project library and document the why behind standards, not only the steps. | Build onboarding, mentorship, searchable precedent, and closeout capture into project delivery. | Give knowledge domains owners, maintenance cycles, source links, and measures of reuse. | Connect expertise across offices and disciplines through governed search, communities, and succession paths. |
| 05Business Model & Finance | Know cash, backlog, effective rate, project cost, and the minimum fee needed for healthy work. | Build a monthly financial rhythm, consistent project setup, and fast invoicing and collections. | Connect staffing, scope, schedule, fees, pipeline, and project health in one management view. | Manage portfolio mix, capacity, risk, pricing, and investment with reliable forward-looking data. | Model enterprise performance by market, office, client, service, and acquisition—not only in aggregate. |
| 06Positioning & Brand | Name the work, client, and belief the practice wants to be known for; show proof from real projects. | Turn project experience into a consistent story, visual system, and useful body of expertise. | Choose priority markets and align website, proposals, talks, awards, and recruiting around them. | Manage reputation across practice areas while preserving a coherent firm-level point of view. | Operate a portfolio of brands, sectors, geographies, and public expertise with shared standards and local relevance. |
| 07Business Development | Maintain a small relationship list, a follow-up rhythm, and a reusable record of project proof. | Create one lead desk for inquiries, referrals, pursuits, next actions, and proposal ingredients. | Define qualification, pursuit ownership, capture planning, proposal assembly, and win-loss learning. | Connect market intelligence, seller-doers, account plans, pipeline, workload, and project outcomes. | Coordinate enterprise accounts, sectors, regions, partnerships, and cross-selling through shared intelligence. |
Read down a column for a firm-size path. Read across a row to see how one capability changes with scale.
Five sizes. Five different constraints.
Headcount is only a proxy. Complexity also comes from offices, disciplines, markets, project types, ownership structure, and client requirements. Still, firm size changes where work breaks first and what the firm can realistically maintain.
Protect the principal’s attention
The principal is designer, seller, project manager, finance lead, and final reviewer. The first modern systems reduce reconstruction: a trusted project record, a relationship list, clear templates, disciplined file structure, supported AI accounts, and automation around recurring administrative work.
Primary riskEvery critical decision and relationship lives in one person.Build shared habits before complexity hardens
A five-person firm still moves through proximity, but handoffs begin to matter. The useful move is shared operating clarity: one place for work, consistent project setup, visible responsibilities, basic financial rhythm, reusable proof, and a small number of tools that everyone can actually use.
Primary riskThe founder remains the router for every exception.Turn informal coordination into an operating model
Specialization arrives. Project managers, designers, finance, marketing, and operations see different slices of the firm. The work now needs stage gates, role definitions, system owners, current-state dashboards, structured knowledge transfer, and a repeatable pursuit-to-project handoff.
Primary riskThe firm scales through heroic people and parallel spreadsheets.Connect leadership decisions to portfolio reality
Multiple leaders must coordinate markets, staffing, project performance, hiring, investment, and quality. Modernization shifts from individual efficiency to connected management: portfolio visibility, integrated systems, formal knowledge ownership, reusable delivery standards, and measured technology adoption.
Primary riskEach team solves the same operating problem differently.Govern a network without flattening it
Large firms need shared data, security, interoperability, domain ownership, and enterprise standards. They also need local judgment. The modern structure creates a strong common layer—identity, permissions, records, models, metrics, and approved capabilities—while allowing offices and disciplines to adapt the work.
Primary riskEnterprise consistency becomes another name for delay and local workarounds.How the seven pillars connect
A firm becomes more capable when improvement in one pillar strengthens the others. A new dashboard has limited value without reliable workflow state. A proposal system has limited value without clear positioning and reusable project knowledge. AI adoption has limited value without leadership, review, training, and ownership.
Leadership & Culture
Make priorities visible and give people room to improve the work.
- Translate strategy into named priorities
- Create decision rights and operating cadences
- Make improvement part of everyone’s job
Workflow & Operations
Turn recurring delivery into a visible, teachable system.
- Map work from trigger to accepted outcome
- Define handoffs, exceptions, and current state
- Protect design intent through delivery
Technology & AI
Give each system a job and connect AI to governed firm knowledge.
- Give every platform and AI capability a job
- Connect data with permissions and human gates
- Measure use, quality, and business effect
Knowledge Transfer
Move the firm’s judgment from individual memory into daily work.
- Capture the why while work is happening
- Make approved precedent and lessons searchable
- Build onboarding, mentorship, and succession into delivery
Business Model & Finance
Know which work creates value and how the firm converts effort into margin.
- Connect effort, scope, fees, cash, and margin
- See portfolio health early enough to act
- Fund the operating capacity that improves practice
Positioning & Brand
Make the firm’s point of view legible before the interview begins.
- Choose a clear audience and point of view
- Turn project outcomes into credible proof
- Align public expertise with the work the firm wants
Business Development
Turn relationships, evidence, and follow-through into a repeatable path to good work.
- Capture and qualify relationships consistently
- Assemble proposals from trusted evidence
- Feed win, loss, and client learning back into the firm
If an improvement belongs to only one pillar, inspect the handoffs. The value usually appears when the change reaches the next part of the firm: knowledge into delivery, delivery into finance, finance into leadership, project proof into positioning, and positioning into growth.
A practical modernization sequence
The sequence repeats at every size. What changes is the scope: one principal’s week, one team’s project workflow, a firmwide pursuit system, or an enterprise operating domain.
See the firm as it works
Trace real work from trigger to outcome. Record where information begins, who decides, what gets re-entered, where state disappears, and which exceptions consume leadership attention.
Make the recurring path explicit
Define the owner, source, handoff, review gate, accepted destination, and measure for the workflow. A usable standard describes the normal path and what happens when reality departs from it.
Connect the record
Reduce parallel versions of truth. Link project, relationship, financial, staffing, document, and decision records so the team can retrieve context and see current state without reconstruction.
Build leverage into the work
Use templates, automation, AI skills, dashboards, and role design to remove repeated assembly and checking. Qualified people retain the decisions that require judgment and accountability.
Run the learning loop
Measure adoption, exceptions, rework, cycle time, quality, margin, and client response. Feed corrections and project lessons back into standards, training, offers, and the next workflow.
Start with a domain people care about and can observe. The AEC AI Workflow Atlas shows concrete possibilities across winning work, production, delivery, construction, operations, finance, knowledge, and adoption. Where should an architecture firm start with AI? turns that possibility map into a first-step decision.
A seven-question firm scorecard
Use these questions in a leadership meeting, annual planning session, technology committee, or project-retrospective cycle. The answers should point to evidence in the work—not only a policy, intention, or product list.
Can people name the firm’s current priorities, who owns them, and where decisions get made?
Can a team see the current state of a pursuit or project without building a fresh spreadsheet?
Does each core system have an owner, an authoritative record, and a defined relationship to AI?
Can someone find the approved detail, decision, precedent, or lesson with its source and context?
Can leaders see backlog, capacity, project health, cash, and pipeline early enough to act?
Does public proof make the firm’s expertise and point of view obvious to the right buyer?
Does every meaningful relationship and pursuit have an owner, next action, and learning record?
Patterns matter more than a total score. A weak connection between two pillars—technology and workflow, knowledge and delivery, positioning and business development—often creates more friction than one capability in isolation.
A universe, not a single article
The Modern AEC Firm Playbook is the organizing map. The other Clearworks flagship resources answer the next questions with current evidence and practical workflows.
Strengthen the connection that is holding the firm back.
Clearworks maps the work, identifies the operating gap, and helps the firm build a practical path across workflow, technology, knowledge, visibility, and adoption.
Sources and further evidence
- AIA, 2024 Firm Survey Report. More than 1,200 firms; firm-size and day-to-day AI figures. The five playbook archetypes are Clearworks operating models, not AIA reporting categories.
- McKinsey, “How AI is reshaping the future of the AEC industry,” July 15, 2026. Analysis of more than 150 workflows across 25 AEC-related domains and the case for redesigning connected domains rather than isolated use cases.
- McKinsey, “Delivering on construction productivity is no longer optional,” August 9, 2024. Industry productivity context.
- AIA AI Firm Toolkit, 2026. Current guidance for responsible firm use, workflow definition, and human review.
- buildingSMART, Industry Foundation Classes. Open, machine-interpretable foundations for cross-system information exchange.
- Clearworks, “State of AI in AEC — Q3 2026.” Public industry sources, anonymized field research, adoption patterns, and methodology supporting this playbook.