Product managers can ship small, reversible changes alone when AI coding agents write the first draft, while engineers keep review policy, production accountability, and the audit evidence SOC 2 requires. Intercom reported on April 21, 2026 that agents drive more than 93 percent of its pull requests and that 19.2 percent merge with no human reviewer. The number that should hold a founder’s attention sits elsewhere: in a 2025 randomized trial, experienced developers took 19 percent longer with AI tools and still believed they had gone 20 percent faster.
That gap between measured and felt speed explains why the division of labor matters more than the tools. Drafting code now costs cents; one developer reported 73 cents across 23 runs on October 5, 2026. Everything after the draft, meaning review, testing, approval, and the pager, still costs engineer attention, and attention is what a young company lacks.
Why Has Review Become the Bottleneck?
Review is the bottleneck because agents raise the volume and size of changes faster than people can read them. Telemetry from more than 10,000 developers across 1,255 teams found 98 percent more pull requests merged on teams with high AI adoption, with review time up 91 percent and average pull request size up 154 percent. Bugs per developer rose 9 percent. The drafting stage sped up and the queue behind it filled.
I saw the principle at work long before software agents existed. On a nuclear submarine, the watchstander who changed a critical valve lineup was never allowed to verify it; a second, independent person checked it. Whoever makes a change cannot certify it. When an agent drafts code and a product manager clicks approve, nobody independent has looked at the system.
Which Changes Can a Product Manager Ship Alone?
A product manager can ship alone any change that scores low on size, blast radius, reversibility, data and security exposure, operational impact, and test completion. Those six dimensions come from a review bot demonstrated on August 10, 2026, which cleared changes under 24 points as low risk and sent anything above 64 to a human. The thresholds are an illustration from one build. The dimensions travel well.
In practice the list is copy edits, documentation, release notes, configuration values behind a feature flag, internal dashboards, read only queries, and sandbox prototypes with no customer data. One product leader described a workflow on March 11, 2026 where a plain English question becomes SQL that is shown for audit before the answer appears. Showing the query keeps a person in the audit seat.
Authentication, payments, data migrations, personal data, infrastructure, public API contracts, and shared components still need an engineer. Intercom’s own reviewer refuses to approve a change that is too large, complex, or broad until someone splits it.
What Do Engineers Own When Agents Write the Draft?
Engineers own the policy that decides which changes get a line by line read, the context files that teach agents the system’s rules, the test and deployment pipeline, and the on call response. Intercom reports that its engineers write the review guidance, rate whether review comments helped, and may request human review of any change. The engineer who ships a change still watches it in production and stays accountable. A model cannot be put on call.
Reported results are encouraging and carry a caveat. Intercom measured revert rates of 0.53 percent for AI authored backend changes against 5.39 percent for human authored ones, and downtime from breaking changes fell 35 percent while deployments doubled. Automatic approval applies only to changes already judged low risk, so selection explains part of that gap. A company reporting its own numbers is also a party with something to show.
How Should Founders Change Hiring Plans?
Founders should hire the reviewer before the implementer. My estimate for a seed stage company is a senior engineer who can write the review policy and read agent output critically as the first engineering hire, and a security or platform engineer at Series A who owns the routing thresholds and the audit log. Product managers should be able to read a diff, write acceptance tests before the agent runs, and use a feature flag.
Entry level roles need a plan and not a freeze. A 2025 payroll analysis found a 13 percent employment decline for workers aged 22 to 25 in AI exposed occupations, a figure that combines several occupations and does not isolate software developers. A company that stops training junior engineers also stops producing the senior reviewers it will need.
Two legal housekeeping items belong on the same list. In my practice, enterprise security questionnaires now ask who may merge to production and how approvals are logged, and a seed stage company that cannot produce the log loses deals. Each product manager who writes code also needs an invention assignment agreement, because the Copyright Office concluded on January 29, 2025 that prompts alone do not make a user the author of AI generated output.
What Remains Unknown About Agent Review?
Three matters are still unknown. Whether the revert advantage survives a matched comparison of equal risk changes. Whether auditors will accept fully automatic approval under the SOC 2 change management criterion. And where the next generation of senior reviewers will come from if early career hiring keeps falling.
My next piece will examine how SOC 2 auditors are treating AI approved pull requests and which change management evidence a seed stage company should keep from its first merge. Subscribe to The Innovation Attorney on Substack so that analysis reaches you the day it publishes, and bring your own review policy questions to the comments.
Interested in analysis about the intersection of tech, policy and the law? Check out my Substack channel.
