AI adoption at enterprise scale
I get agents into the hands of whole engineering organizations, and measure what changed.
Packaging and versioning agents like software, rollout across locked-down enterprise machines, catalogs and standards so teams reuse instead of copy, governance and trust tiers, and metrics that show leadership the effect of the AI programme.
- Case studies
- 4
- Log entries
- 12
- Domains
- Telecom, Quality engineering, Developer platforms and tooling
- Core skills
- Agent packaging and rollout, AI governance and standards, Developer experience tooling, Spec-driven development, Copilot custom agents and skills, Coverage and quality metrics
Case studies
Custom Copilot agents for test-automation teams
Custom agents and skills that generate UI, API and contract tests in each team's own conventions, rolled out with hands-on sessions and a searchable catalog of 27 agents.
Enterprise test-automation teams, Mar 2026 – Sep 2026
Read the case studyAgent and skill distribution platform
Turned copy-pasted AI agent files into versioned packages from a single registry, with a cross-platform installer and a staleness report.
National telecom carrier, May 2026 – present
Read the case studyCoverage intelligence, a quality data layer for agents
Replaced spreadsheet tracking with a pipeline that reads 20+ team test repositories, publishes a weekly executive report, and is designed as the data and context layer quality agents will read through MCP.
National telecom carrier, Oct 2026 – present
Read the case studyAgent evaluation pipeline
Runs an agent programmatically, captures OpenTelemetry traces, and scores both the answer and the trajectory with LLM-as-judge plus deterministic checks.
Internal platform for an enterprise client, May 2026 – Jul 2026
Read the case studyEvidence from the log
- 19 Oct 2026
Extended coverage reporting to mobile test suites
Mobile teams write tests in Java with TestNG, which the first parser couldn't read. Added a Java-aware parser so their coverage shows up in the same weekly report.
AI angleAn agent asked "how covered is the app?" needs every platform in one model, or it answers for web only. This closes the gap so the coverage data an MCP server will serve to agents describes the whole product.
- 14 Oct 2026
Published a structure and naming standard for 20+ test repositories
Every team laid out its repository differently, which made automated reporting brittle. Wrote one standard for folders, tags and naming, with a migration checklist per team.
AI angleA predictable layout is the context layer agents need. With one standard, every agent (test generation, review, coverage queries) finds tests, page objects and tags in the same place in every repository, instead of each agent being tuned per team.
- 6 Oct 2026
Shipped the first weekly automation-coverage report
21 teams, measured straight from code instead of spreadsheets. The first run put regression automation coverage at 81.7%.
AI angleGives the AI test-automation programme a baseline measured from code, so the effect of test-generation agents shows up in the numbers, and gives future agents a trusted source to query.
- 29 Sep 2026
Started coverage measurement from source
Leadership's automation numbers came from hand-kept spreadsheets nobody could trace. Prototyped a zero-dependency pipeline that clones every team repository and counts tests by tag.
AI angleThe first step toward a quality data layer agents can read through MCP. An agent can't reason about coverage when the only source is a spreadsheet.
- 22 Sep 2026
Launched a searchable catalog of 27 agents
Mapped every agent and skill to one of seven SDLC phases and published them in a docs portal, so engineers find an agent before they write a new one.
AI angleTurns a pile of agents into a toolkit. Reuse rises, duplicates fall, and the programme can see which SDLC phases still have no agent support.
- 4 Sep 2026
Built a one-run installer for agent packages
Engineers on Windows and macOS pull every approved agent package with one command, and a staleness report shows which repositories are behind.
AI angleRemoves the setup friction that stops engineers from using agents at all, and tells the programme where teams are running stale agent versions.
- 25 Aug 2026
Moved agent distribution to a single registry
Copies of agent files had drifted across repositories. Now one registry generates every manifest, and packages are versioned and reviewed before release.
AI angleAgents are now shipped like software. A prompt or skill fix reaches every team, and nothing changes agent behavior without review.
- 13 Aug 2026
Changed the rollout plan for code-review skills
Found that code-review skills only load from a repository's default branch, so teams testing on feature branches saw nothing. Rewrote the rollout steps around that.
AI angleKnowing how the agent platform actually loads skills is the difference between a rollout that works and teams deciding AI review "doesn't do anything".
- 29 May 2026
Prototyped an internal agent marketplace
A place to publish agents, skills and MCP servers, with trust tiers (approved, community-vetted, beta) and trace-based vetting before anything is listed.
AI angleGovernance for agent sprawl. Teams share agents and MCP servers through one marketplace, and evaluation decides what they can trust.
- 12 May 2026
Started versioned packaging for AI agents
Test teams were copy-pasting agent files between repositories. Proposed packaging them like any other dependency, with a schema and a review gate.
AI angleThe first move from "everyone has their own prompt files" to a managed agent supply chain the programme can govern.
- 20 Apr 2026
Rolled out custom Copilot agents to test-automation teams
Wrote agents and skills that generate Playwright tests in each team's own conventions, and ran hands-on sessions so teams actually used them.
AI angleGeneric assistants write generic tests. Encoding each team's frameworks and conventions into agents is what made the output mergeable, and the sessions are what made people use it.
- 10 Nov 2025
Moved Visual Basic modules to Java 21 with spec-driven agents
Ad-hoc AI coding gave inconsistent results. Each module now gets a written spec first, then agents implement and test against it.
AI angleSpec-driven development makes agent output repeatable. The spec is the contract the agent is held to, and the CI loop lets it correct itself.