Block says 95% of its engineers use AI daily. The interesting part is who runs five agents.

Fifty engineers at 30 percent of their time is fifteen full-time equivalents ^[15], and that invoice does not arrive from a vendor. What it bought is unglamorous: AGENTS.md context files with build and test commands, human-facing HOWTOAI.md guides, packaged agent skills for repeated jobs like API test generation and legacy refactors, automated AI review on pull requests, and headless assistance that iterates on tasks, fixes CI failures and pushes changes ^[11]. Block says the work was dull enough to need a wrapper, so its developer relations team built Repo Quest, an RPG in which developers collect companions through four tiers running Locked, Novice, Adept, Artisan ^[12][13].

Where that effort landed is the part other CTOs should read twice. Block put its champions at the repo level, reasoning that the repo is the central point of reference for everyone contributing code, and that agents must be able to discover and consume a codebase before they can be trusted to contribute to it and maintain it ^[10]. Read alongside the stage distribution, that implies the binding constraint on running five agents in parallel is not the model, it is whether the repository can brief five agents without a human in the loop translating.

The coverage was deliberately uneven in the useful way. The program reached Square, Cash App, Afterpay, Tidal, Proto and Platform teams, spanning frontend, backend, mobile, hardware, data engineering and infrastructure, and repos ranging from massive monorepos to tight focused services ^[14]. Block says this pressure tested patterns across different engineering realities rather than one. Meanwhile it declined to pick tools, buying a lot of frontier models and IDEs on the grounds that no clear winner emerged across 2025 and locking in would be foolish, while conceding it would like to standardize on a couple eventually ^[6][7].

Two things should stop anyone from lifting the 95 percent figure as a benchmark. First, Block's own finding that its mobile and JVM backend developers struggle with frontier models and tools in a way web developers do not ^[8]. A uniform adoption rate across a company with that spread is measuring logins, not leverage. Second, the distribution is ordinal only. Largest, second largest, small: no sizes, no percentages beyond the headline ^[16]. And Stage 5 is characterised in a single clause, a single agent run mostly outside an IDE ^[2], with the ladder itself prompted by Steve Yegge's Gas Town essay rather than defined in the post ^[5]. Nobody outside Block can audit their own position against it.

The org chart claim rests on the smallest group. A population is already building an internal agent orchestrator, described as preparation for the inevitable ^[4]. That is a platform team forming around agent supervision before any vendor has sold one, funded on the expectation that the Stage 6 cohort keeps growing. Fifteen FTE bought repo readiness. Supervision is the next bill.