Plan · Org design

Agentic Squad Sizing Calculator

Size platform vs domain agent squads from workload volume and automation depth.

Staffing model for agentic delivery — platform FTE, domain FTE, and a 90-day hiring sequence. Not a headcount mandate.

How it works

Set weekly ticket/workflow volume, automation depth, complexity, and how many domains you serve.
Tune platform maturity and risk appetite — outcomes update with platform vs domain FTE and a hiring sequence.
Use the model in org-design reviews; unlock a printable one-pager with a work email when ready.

Workload & org inputs

Directional staffing model — validate against budget and change capacity.

Weekly ticket / workflow volume Automate-able workflows per week across in-scope domains.

800

Automation depth (%) Share of volume you expect agents to handle with acceptable quality.

40%

Workflow complexity Higher complexity raises domain and platform load (evals, exceptions). Domains in scope Distinct product/business domains owning agents (ITSM, CX, finance…).

Platform maturity Early = more platform build; mature = more domain adoption. Risk appetite Conservative adds review / HITL seats; aggressive leans on autonomy.

Recommended staffing

Defaults match the form. Change any input — numbers refresh instantly.

Platform FTE — Runtime, evals, identity, observability

Domain FTE — Workflow owners across domains

Total FTE — Platform + domain (rounded)

Platform : Domain — Relative staffing mix

90-day hiring sequence — Phased roles — not a locked org chart

Architecture note

—

Adjust inputs to see a tailored note.

Directional org-design estimate only — not a headcount mandate or guarantee of delivery outcomes.

How the model works

Effective agent load ≈ weekly volume × automation depth × complexity multiplier.
Platform FTE starts from a base (maturity-weighted), then scales with load and domain count; risk appetite adjusts review overhead.
Domain FTE ≈ domains × per-domain base × load factor × risk factor.
Ratio = platform : domain (normalized). Early platforms skew platform-heavy; mature ones skew domain-heavy.
90-day sequence phases platform foundations first, then domain pods, then hardening / SRE-style seats based on risk.

All math runs in your browser. Treat FTE as planning bands (±1–2) before opening requisitions.

Unlock printable staffing summary

Work email unlocks Print / Save as PDF. Same subscribe flow as the newsletter.

FAQ

How does the Agentic Squad Sizing Calculator work?

You set weekly workflow volume, automation depth, complexity, domain count, platform maturity, and risk appetite. The model estimates platform FTE, domain FTE, a platform:domain ratio, a 90-day hiring sequence, and an architecture note.

What is platform FTE vs domain FTE?

Platform FTE owns shared agent runtime, evals, identity, observability, and FinOps routing. Domain FTE owns workflows, prompts, and success metrics inside a business or product domain.

Is this a hiring mandate?

No. It is a directional staffing model for planning conversations. Validate against your budget, existing platform team, and change capacity before opening reqs.

Why does risk appetite change headcount?

Conservative appetite adds human-in-the-loop and review capacity (higher FTE). Aggressive appetite assumes more autonomy and fewer review seats — higher delivery risk, leaner staffing.

What does platform maturity change?

Early platforms need more platform FTE to build foundations. Mature platforms shift effort toward domain adoption, so domain FTE rises relative to platform.

Can I get a printable summary?

Yes. Enter a work email to unlock Print / Save as PDF, or book a 30-minute architecture review to pressure-test the org design.

How it works

How the model works

Unlock printable staffing summary

FAQ

Agentic Squad Sizing Summary