Benchmark your org against hundreds of agentic eng teams.
A detailed picture of how your org works, and where it has room to improve.
01
Benchmark how your org works
Output
What each engineer on the team produces per working day, weighted by each change's complexity, against the field we measure.
Build mix
The share of your output that builds and improves the product, against the bug fixing that only keeps it running.
Parallelism
The pull requests each engineer keeps in flight on an active day, the clearest trace of running agents side by side.
Iteration
The commits it takes to land a pull request: few means the agent lands it, many means someone is hand-holding it.
Rework
The share of reviewed pull requests that needed more commits after their first review: what a check before review could catch.
PR quality
Every merged pull request graded for quality and weighed by its output, so speed from cutting corners shows up here.
Review load
How much of the reviewing the busiest fifth of reviewers carries, and whether they are the people the team needs building.
Cycle time
Hours from a pull request's first commit to its merge, split into coding, waiting for a first review, reviewing and merging.
Review quality
The share of merged pull requests whose review changed anything, against the rubber stamps that approve without a word.
Review risk
The share of high-risk pull requests (a migration, a secret, CI, the public API) a person reviewed before merging, against the routine ones.
Delivery
The share of the output your team produced that has not reached the default branch: still unreleased, or quietly discarded.
Archetypes
How each engineer's work leans across these measures: a description of the team, never a ranking of it.
Conveyor Most of the review, and it changes almost nothing.
What each engineer on the team produces per working day, weighted by each change's complexity, against the field we measure.
Output
What each engineer on the team produces per working day, weighted by each change's complexity, against the field we measure.
02
Find the root causes in your systems
InstructionsReusabilityCI checksReleaseObservabilityRealistic test dataAgent QAPromptingDev environment
Do AGENTS.md, CLAUDE.md and your READMEs still match the code they describe?When one engineer works out a better way to use agents, does the rest of the team get it?Does anything stop a bad change from merging before a person has to catch it?Does a change that breaks something stop before your customers get it?When a release breaks something, can an agent see what broke?Can an agent test a change against data that looks like production, without touching production?Can an agent check that its own change works before a person looks at it?Does the engineering team plan, hand over context and delegate whole tasks to agents?Can an agent start your app from a clean clone, without anyone’s help?
Do AGENTS.md, CLAUDE.md and your READMEs still match the code they describe? Partially, the brief is right but for its test command.When one engineer works out a better way to use agents, does the rest of the team get it? No, .claude/ is gitignored, so each skill stays on the laptop it was written on.Does anything stop a bad change from merging before a person has to catch it? Yes, a failing test, lint or type check blocks the merge.Does a change that breaks something stop before your customers get it? No, changes ship on merge, nothing checks the deploy, and rollback is by hand.When a release breaks something, can an agent see what broke? Partially, errors name their release, but nothing marks when it went out.Can an agent test a change against data that looks like production, without touching production? No, the seeds are placeholders, and the only realistic data is a dump of production.Can an agent check that its own change works before a person looks at it? No, every PR gets a preview, and one person checks them all by hand.Does the engineering team plan, hand over context and delegate whole tasks to agents? No, 64% of the engineering team steers agents a line at a time, with no plan or context.Can an agent start your app from a clean clone, without anyone’s help? No, setup stops until someone logs in to npm.
Dev environmentReusabilityCI checksReleaseObservabilityRealistic test dataAgent QAPromptingInstructions
Can an agent start your app from a clean clone, without anyone’s help?When one engineer works out a better way to use agents, does the rest of the team get it?Does anything stop a bad change from merging before a person has to catch it?Does a change that breaks something stop before your customers get it?When a release breaks something, can an agent see what broke?Can an agent test a change against data that looks like production, without touching production?Can an agent check that its own change works before a person looks at it?Does the engineering team plan, hand over context and delegate whole tasks to agents?Do AGENTS.md, CLAUDE.md and your READMEs still match the code they describe?
Can an agent start your app from a clean clone, without anyone’s help? No, setup stops until someone logs in to npm.When one engineer works out a better way to use agents, does the rest of the team get it? No, .claude/ is gitignored, so each skill stays on the laptop it was written on.Does anything stop a bad change from merging before a person has to catch it? Yes, a failing test, lint or type check blocks the merge.Does a change that breaks something stop before your customers get it? No, changes ship on merge, nothing checks the deploy, and rollback is by hand.When a release breaks something, can an agent see what broke? Partially, errors name their release, but nothing marks when it went out.Can an agent test a change against data that looks like production, without touching production? No, the seeds are placeholders, and the only realistic data is a dump of production.Can an agent check that its own change works before a person looks at it? No, every PR gets a preview, and one person checks them all by hand.Does the engineering team plan, hand over context and delegate whole tasks to agents? No, 64% of the engineering team steers agents a line at a time, with no plan or context.Do AGENTS.md, CLAUDE.md and your READMEs still match the code they describe? Partially, the brief is right but for its test command.
Dev environmentInstructionsCI checksReleaseObservabilityRealistic test dataAgent QAPromptingReusability
Can an agent start your app from a clean clone, without anyone’s help?Do AGENTS.md, CLAUDE.md and your READMEs still match the code they describe?Does anything stop a bad change from merging before a person has to catch it?Does a change that breaks something stop before your customers get it?When a release breaks something, can an agent see what broke?Can an agent test a change against data that looks like production, without touching production?Can an agent check that its own change works before a person looks at it?Does the engineering team plan, hand over context and delegate whole tasks to agents?When one engineer works out a better way to use agents, does the rest of the team get it?
Can an agent start your app from a clean clone, without anyone’s help? No, setup stops until someone logs in to npm.Do AGENTS.md, CLAUDE.md and your READMEs still match the code they describe? Partially, the brief is right but for its test command.Does anything stop a bad change from merging before a person has to catch it? Yes, a failing test, lint or type check blocks the merge.Does a change that breaks something stop before your customers get it? No, changes ship on merge, nothing checks the deploy, and rollback is by hand.When a release breaks something, can an agent see what broke? Partially, errors name their release, but nothing marks when it went out.Can an agent test a change against data that looks like production, without touching production? No, the seeds are placeholders, and the only realistic data is a dump of production.Can an agent check that its own change works before a person looks at it? No, every PR gets a preview, and one person checks them all by hand.Does the engineering team plan, hand over context and delegate whole tasks to agents? No, 64% of the engineering team steers agents a line at a time, with no plan or context.When one engineer works out a better way to use agents, does the rest of the team get it? No, .claude/ is gitignored, so each skill stays on the laptop it was written on.
Dev environmentInstructionsReusabilityReleaseObservabilityRealistic test dataAgent QAPromptingCI checks
Can an agent start your app from a clean clone, without anyone’s help?Do AGENTS.md, CLAUDE.md and your READMEs still match the code they describe?When one engineer works out a better way to use agents, does the rest of the team get it?Does a change that breaks something stop before your customers get it?When a release breaks something, can an agent see what broke?Can an agent test a change against data that looks like production, without touching production?Can an agent check that its own change works before a person looks at it?Does the engineering team plan, hand over context and delegate whole tasks to agents?Does anything stop a bad change from merging before a person has to catch it?
Can an agent start your app from a clean clone, without anyone’s help? No, setup stops until someone logs in to npm.Do AGENTS.md, CLAUDE.md and your READMEs still match the code they describe? Partially, the brief is right but for its test command.When one engineer works out a better way to use agents, does the rest of the team get it? No, .claude/ is gitignored, so each skill stays on the laptop it was written on.Does a change that breaks something stop before your customers get it? No, changes ship on merge, nothing checks the deploy, and rollback is by hand.When a release breaks something, can an agent see what broke? Partially, errors name their release, but nothing marks when it went out.Can an agent test a change against data that looks like production, without touching production? No, the seeds are placeholders, and the only realistic data is a dump of production.Can an agent check that its own change works before a person looks at it? No, every PR gets a preview, and one person checks them all by hand.Does the engineering team plan, hand over context and delegate whole tasks to agents? No, 64% of the engineering team steers agents a line at a time, with no plan or context.Does anything stop a bad change from merging before a person has to catch it? Yes, a failing test, lint or type check blocks the merge.
Dev environmentInstructionsReusabilityCI checksObservabilityRealistic test dataAgent QAPromptingRelease
Can an agent start your app from a clean clone, without anyone’s help?Do AGENTS.md, CLAUDE.md and your READMEs still match the code they describe?When one engineer works out a better way to use agents, does the rest of the team get it?Does anything stop a bad change from merging before a person has to catch it?When a release breaks something, can an agent see what broke?Can an agent test a change against data that looks like production, without touching production?Can an agent check that its own change works before a person looks at it?Does the engineering team plan, hand over context and delegate whole tasks to agents?Does a change that breaks something stop before your customers get it?
Can an agent start your app from a clean clone, without anyone’s help? No, setup stops until someone logs in to npm.Do AGENTS.md, CLAUDE.md and your READMEs still match the code they describe? Partially, the brief is right but for its test command.When one engineer works out a better way to use agents, does the rest of the team get it? No, .claude/ is gitignored, so each skill stays on the laptop it was written on.Does anything stop a bad change from merging before a person has to catch it? Yes, a failing test, lint or type check blocks the merge.When a release breaks something, can an agent see what broke? Partially, errors name their release, but nothing marks when it went out.Can an agent test a change against data that looks like production, without touching production? No, the seeds are placeholders, and the only realistic data is a dump of production.Can an agent check that its own change works before a person looks at it? No, every PR gets a preview, and one person checks them all by hand.Does the engineering team plan, hand over context and delegate whole tasks to agents? No, 64% of the engineering team steers agents a line at a time, with no plan or context.Does a change that breaks something stop before your customers get it? No, changes ship on merge, nothing checks the deploy, and rollback is by hand.
Dev environmentInstructionsReusabilityCI checksReleaseRealistic test dataAgent QAPromptingObservability
Can an agent start your app from a clean clone, without anyone’s help?Do AGENTS.md, CLAUDE.md and your READMEs still match the code they describe?When one engineer works out a better way to use agents, does the rest of the team get it?Does anything stop a bad change from merging before a person has to catch it?Does a change that breaks something stop before your customers get it?Can an agent test a change against data that looks like production, without touching production?Can an agent check that its own change works before a person looks at it?Does the engineering team plan, hand over context and delegate whole tasks to agents?When a release breaks something, can an agent see what broke?
Can an agent start your app from a clean clone, without anyone’s help? No, setup stops until someone logs in to npm.Do AGENTS.md, CLAUDE.md and your READMEs still match the code they describe? Partially, the brief is right but for its test command.When one engineer works out a better way to use agents, does the rest of the team get it? No, .claude/ is gitignored, so each skill stays on the laptop it was written on.Does anything stop a bad change from merging before a person has to catch it? Yes, a failing test, lint or type check blocks the merge.Does a change that breaks something stop before your customers get it? No, changes ship on merge, nothing checks the deploy, and rollback is by hand.Can an agent test a change against data that looks like production, without touching production? No, the seeds are placeholders, and the only realistic data is a dump of production.Can an agent check that its own change works before a person looks at it? No, every PR gets a preview, and one person checks them all by hand.Does the engineering team plan, hand over context and delegate whole tasks to agents? No, 64% of the engineering team steers agents a line at a time, with no plan or context.When a release breaks something, can an agent see what broke? Partially, errors name their release, but nothing marks when it went out.
Dev environmentInstructionsReusabilityCI checksReleaseObservabilityAgent QAPromptingRealistic test data
Can an agent start your app from a clean clone, without anyone’s help?Do AGENTS.md, CLAUDE.md and your READMEs still match the code they describe?When one engineer works out a better way to use agents, does the rest of the team get it?Does anything stop a bad change from merging before a person has to catch it?Does a change that breaks something stop before your customers get it?When a release breaks something, can an agent see what broke?Can an agent check that its own change works before a person looks at it?Does the engineering team plan, hand over context and delegate whole tasks to agents?Can an agent test a change against data that looks like production, without touching production?
Can an agent start your app from a clean clone, without anyone’s help? No, setup stops until someone logs in to npm.Do AGENTS.md, CLAUDE.md and your READMEs still match the code they describe? Partially, the brief is right but for its test command.When one engineer works out a better way to use agents, does the rest of the team get it? No, .claude/ is gitignored, so each skill stays on the laptop it was written on.Does anything stop a bad change from merging before a person has to catch it? Yes, a failing test, lint or type check blocks the merge.Does a change that breaks something stop before your customers get it? No, changes ship on merge, nothing checks the deploy, and rollback is by hand.When a release breaks something, can an agent see what broke? Partially, errors name their release, but nothing marks when it went out.Can an agent check that its own change works before a person looks at it? No, every PR gets a preview, and one person checks them all by hand.Does the engineering team plan, hand over context and delegate whole tasks to agents? No, 64% of the engineering team steers agents a line at a time, with no plan or context.Can an agent test a change against data that looks like production, without touching production? No, the seeds are placeholders, and the only realistic data is a dump of production.
Dev environmentInstructionsReusabilityCI checksReleaseObservabilityRealistic test dataPromptingAgent QA
Can an agent start your app from a clean clone, without anyone’s help?Do AGENTS.md, CLAUDE.md and your READMEs still match the code they describe?When one engineer works out a better way to use agents, does the rest of the team get it?Does anything stop a bad change from merging before a person has to catch it?Does a change that breaks something stop before your customers get it?When a release breaks something, can an agent see what broke?Can an agent test a change against data that looks like production, without touching production?Does the engineering team plan, hand over context and delegate whole tasks to agents?Can an agent check that its own change works before a person looks at it?
Can an agent start your app from a clean clone, without anyone’s help? No, setup stops until someone logs in to npm.Do AGENTS.md, CLAUDE.md and your READMEs still match the code they describe? Partially, the brief is right but for its test command.When one engineer works out a better way to use agents, does the rest of the team get it? No, .claude/ is gitignored, so each skill stays on the laptop it was written on.Does anything stop a bad change from merging before a person has to catch it? Yes, a failing test, lint or type check blocks the merge.Does a change that breaks something stop before your customers get it? No, changes ship on merge, nothing checks the deploy, and rollback is by hand.When a release breaks something, can an agent see what broke? Partially, errors name their release, but nothing marks when it went out.Can an agent test a change against data that looks like production, without touching production? No, the seeds are placeholders, and the only realistic data is a dump of production.Does the engineering team plan, hand over context and delegate whole tasks to agents? No, 64% of the engineering team steers agents a line at a time, with no plan or context.Can an agent check that its own change works before a person looks at it? No, every PR gets a preview, and one person checks them all by hand.
Dev environmentInstructionsReusabilityCI checksReleaseObservabilityRealistic test dataAgent QAPrompting
Can an agent start your app from a clean clone, without anyone’s help?Do AGENTS.md, CLAUDE.md and your READMEs still match the code they describe?When one engineer works out a better way to use agents, does the rest of the team get it?Does anything stop a bad change from merging before a person has to catch it?Does a change that breaks something stop before your customers get it?When a release breaks something, can an agent see what broke?Can an agent test a change against data that looks like production, without touching production?Can an agent check that its own change works before a person looks at it?Does the engineering team plan, hand over context and delegate whole tasks to agents?
Can an agent start your app from a clean clone, without anyone’s help? No, setup stops until someone logs in to npm.Do AGENTS.md, CLAUDE.md and your READMEs still match the code they describe? Partially, the brief is right but for its test command.When one engineer works out a better way to use agents, does the rest of the team get it? No, .claude/ is gitignored, so each skill stays on the laptop it was written on.Does anything stop a bad change from merging before a person has to catch it? Yes, a failing test, lint or type check blocks the merge.Does a change that breaks something stop before your customers get it? No, changes ship on merge, nothing checks the deploy, and rollback is by hand.When a release breaks something, can an agent see what broke? Partially, errors name their release, but nothing marks when it went out.Can an agent test a change against data that looks like production, without touching production? No, the seeds are placeholders, and the only realistic data is a dump of production.Can an agent check that its own change works before a person looks at it? No, every PR gets a preview, and one person checks them all by hand.Does the engineering team plan, hand over context and delegate whole tasks to agents? No, 64% of the engineering team steers agents a line at a time, with no plan or context.
Whether an agent can clone a repository cold, boot it and run its tests without borrowing anyone's credentials.
InstructionsReusabilityCI checksReleaseObservabilityRealistic test dataAgent QAPromptingDev environment
Do AGENTS.md, CLAUDE.md and your READMEs still match the code they describe?When one engineer works out a better way to use agents, does the rest of the team get it?Does anything stop a bad change from merging before a person has to catch it?Does a change that breaks something stop before your customers get it?When a release breaks something, can an agent see what broke?Can an agent test a change against data that looks like production, without touching production?Can an agent check that its own change works before a person looks at it?Does the engineering team plan, hand over context and delegate whole tasks to agents?Can an agent start your app from a clean clone, without anyone’s help?
Agent shell · cold clone of web-app
Do AGENTS.md, CLAUDE.md and your READMEs still match the code they describe? Partially, the brief is right but for its test command.When one engineer works out a better way to use agents, does the rest of the team get it? No, .claude/ is gitignored, so each skill stays on the laptop it was written on.Does anything stop a bad change from merging before a person has to catch it? Yes, a failing test, lint or type check blocks the merge.Does a change that breaks something stop before your customers get it? No, changes ship on merge, nothing checks the deploy, and rollback is by hand.When a release breaks something, can an agent see what broke? Partially, errors name their release, but nothing marks when it went out.Can an agent test a change against data that looks like production, without touching production? No, the seeds are placeholders, and the only realistic data is a dump of production.Can an agent check that its own change works before a person looks at it? No, every PR gets a preview, and one person checks them all by hand.Does the engineering team plan, hand over context and delegate whole tasks to agents? No, 64% of the engineering team steers agents a line at a time, with no plan or context.Can an agent start your app from a clean clone, without anyone’s help? No, setup stops until someone logs in to npm.
03
Get a first draft of what we would fix
A preview of what Mesmer would do for you.
Every gap we find becomes a task on a roadmap, in waves, each with the check that proves it done and a prompt your coding agents can run.
Every gap we find becomes a task on a roadmap, in waves, each with the check that proves it done and a prompt your coding agents can run.
Make it safe
Wave 1True briefs and one shared kit
- The agent file tells the truth
Wave 2Any clone boots cold
- Any clone boots and verifies
Make it fast
Wave 3Every change proves itself
- Realistic data below production
