How Many Enterprise Architects Should a Company Have?

Why Headcount Ratios Break Down

Rules like “one architect per 100 developers” or “one EA per $1B revenue” circulate in forums but mislead when applied without context. Architecture demand scales with decision volume, integration complexity, and governance obligations—not headcount alone.

A $800M fintech with 40 core systems and heavy regulatory reporting may need more EA capacity than a $2B industrial manufacturer with a stable ERP-centric landscape. Similarly, organizations running five simultaneous transformation programs require surge capacity regardless of steady-state ratios.

Larkinized LLC sizes teams using a demand model: count major business capabilities under active change, applications in scope for cloud or retirement decisions, integration endpoints, and ARB review load. Supply equals architects who can credibly lead those domains plus operational overhead for repository and governance.

Right-sizing is dynamic. Teams often start lean, expand during transformation, then federate into business-unit architects with a thin central standards function. Executives should plan multi-year staffing curves, not a single permanent number.

Benchmark Ranges by Organization Size

The following ranges assume U.S.-based blended teams (enterprise, solution, business, data architects) and a mix of central and federated responsibilities. Adjust upward for banking, insurance, healthcare, and public sector; adjust downward for single-platform SaaS and asset-light services.

$50M–$250M revenue: 0–1 FTE equivalent (often fractional EA plus senior solution architect dual-hat). Formal team optional unless multi-product or regulated.

$250M–$1B revenue: 1–4 FTEs. Typically one lead EA plus domain specialists part-time or shared with major programs.

$1B–$5B revenue: 4–12 FTEs. Central standards, portfolio management, and embedded BUs emerge.

$5B–$20B revenue: 12–35 FTEs in federated models with strong central governance.

$20B+ revenue: 35–100+ architecture professionals across enterprise, domain, and segment teams—not all titled “Enterprise Architect.”

Portfolio-Based Sizing Formula

Use application portfolio scale as a cross-check: for organizations maintaining a governed inventory of 200–500 applications, plan 3–6 architecture FTEs minimum for portfolio curation, standards, and review capacity. Add 1 FTE per additional 150–250 applications in active transformation, or per major business domain (e.g., sales, supply chain, finance) undergoing separate target-state design.

Integration density matters. API-first organizations with thousands of managed interfaces need integration architecture capacity even if application count is moderate. Count integration platforms, event streams, and B2B endpoints—not just apps.

Transformation multiplier: if more than three enterprise programs exceed $5M spend concurrently, add 20–40% temporary capacity via consultants or loaned solution architects into a central coordination cell.

Document assumptions when presenting to finance. Architecture staffing proposals backed by portfolio metrics survive budget scrutiny better than appeals to industry folklore.

• Base: 1 lead EA for programs under $1B with formal EA charter
• +1 per major domain in active target-state redesign
• +1 per 200–250 apps under governance (rounded)
• +20–40% surge during multi-program transformation windows
• Include 0.5–1 FTE for tool/repository operations at maturity Level 2+

Centralized vs. Federated Staffing

Centralized models concentrate standards, portfolio analytics, and ARB operations in one team (typically 60–80% of total EA FTEs). Federated models embed architects in business units with a thin central council (central 20–40%, federated 60–80%). Hybrid is most common at scale.

Federation increases total headcount slightly because domain architects duplicate some coordination work, but improves business alignment and adoption. Central-only teams risk ivory-tower perception unless they publish enablement services and measurable time savings.

Title inflation warning: not every “architect” performs enterprise scope work. Capacity planning should classify roles by decision scope—enterprise, domain, solution, technical—and staff accordingly.

Larkinized LLC helps clients design federated operating models with RACI matrices clarifying which decisions central EA owns versus domain teams, preventing both gaps and duplicate staffing.

Skills Mix Within the Team

A balanced EA function combines business architecture (capabilities, value streams), application and integration architecture, data architecture, technology/platform architecture, and security architecture—either as dedicated roles or rotational coverage.

Small teams prioritize T-shaped generalists: one leader strong in business-IT alignment plus one specialist each in data and cloud/platform. Large teams add dedicated portfolio analysts, tool administrators, and governance managers.

Do not neglect soft skills. Architects spend 40–60% of time facilitating workshops, negotiating trade-offs, and communicating with executives. Hiring only deep technologists undermines adoption.

Training existing solution architects into enterprise scope can work but requires mentoring on portfolio thinking and political navigation—budget 6–12 months for transition.

When You Have Too Many—or Too Few

Too few: ARB backlogs exceed six weeks, portfolio data is stale, standards are ignored, and major programs proceed without architectural input until escalation crises occur.

Too many: Architects compete for the same reviews, produce redundant artifacts, or invent governance layers that slow delivery without reducing risk. Symptoms include low stakeholder attendance and ceremonial sign-offs.

Right-size by measuring utilization: target 60–75% of architect time on high-value decision support and roadmaps, 15–25% on governance and reviews, 10–15% on repository and standards maintenance. Chronic overload or underutilization both warrant staffing review.

Consulting overlays should have explicit exit criteria—knowledge transfer milestones and internal hire dates—so surge capacity does not become permanent dependency.

Action Plan for CIOs and CHROs

Inventory current architecture FTEs by scope, not title. Map coverage gaps against business capabilities in transformation. Apply portfolio-based formula and benchmark ranges to produce low, target, and peak scenarios for a three-year plan.

Align hiring waves with program funding—recruit domain architects when sponsored transformations start, not months after backlog appears.

Larkinized LLC provides EA staffing assessments that produce board-ready headcount models linked to your application inventory and program pipeline. Schedule a consultation to validate your numbers before requisition approval.