3-week engagement
Onboarding founding clientsAI-Native Delivery Accelerator.
The deeper engagement the Readout points to: install the operating-model fix and prove it on one team and one repo, with a before-and-after number.
The three-week engagement that installs the fix the Readout identifies (measurement, review standards, and workflow) and proves it on a single team and repo with an attributable before-and-after number. This is the follow-on, offered after the Readout, not a starting point.
01 · Published tiers
Same SKU, sized to the org.
The Standard price is the anchor. Startup is published for smaller teams. Above 300 engineers the scope changes enough that the band is priced on the call.
Startup
5 to 25 engineers, funded
One-team, one-repo pilot, 2 to 3 interviews, lighter rollout support
Standard
Standard anchor25 to 300 engineers
One-team, one-repo pilot, 3 to 5 interviews, full 3-week async rollout support
Enterprise
300 to 600 engineers
One-team, one-repo pilot with broader interview coverage and rollout-plan surface
02 · What you get
What you walk away with.
Week 1 · Diagnose
Baseline instrumentation plus three to five interviews to find the binding constraint, usually review bandwidth or workflow, rarely the tool itself.
Midpoint · Half-day readout
Findings presented to leadership, followed by a kickoff working session on the fix.
Weeks 2 to 3 · Execution support
Async support while your team rolls the change out, on a fixed end date set at kickoff.
The proof
A one-team, one-repo pilot with a measured before-and-after delta (review time, throughput, revert rate). That number is your attributable case study.
03 · The terms
Plain terms, published up front.
04 · What it installs
Three modules that install the fix.
Credited in full from the Readout, this installs three modules. It is the deeper engagement the Readout points to, not a starting point.
Module A · The Golden Path
One ticket start to finish as the reference standard: read the ticket, spec upstream, set guardrails, run the agent in small batches, self-review, open a pull request with a real summary, then tiered review and merge. The template your pilot team copies.
Module B · AI-navigable repo and tiered-review restructure
Module boundaries and CODEOWNERS on sensitive paths, a risk-tier review rubric, a pull-request size cap enforced in CI, and guardrails at the merge boundary. This is the governance change, not an individual-contributor trick, and it is the core of the engagement.
Module C · The .claude/ folder as institutional memory
Your standards encoded as config the agents actually read: CLAUDE.md context files, slash commands, subagents, hooks, and skills, so team knowledge compounds instead of living in one engineer's head.
Book the discovery call.
Thirty minutes, free, no pitch. We walk your setup and I name the smallest thing that would move your numbers, even when that thing is not hiring me.
alextongme@gmail.com →I reply within one business day