AI agents turn a backlog into mergeable pull requests

<aside>

πŸ‡¬πŸ‡§ English πŸ‡©πŸ‡ͺ Deutsch

</aside>

Even with an AI coding assistant, a developer prompts, reads and corrects every change by hand. Developer attention sets the pace, and your backlog waits for it.

Agents can turn a ticket into a pull request unsupervised when it arrives as a spec they can execute, with acceptance criteria they can check themselves. Your developers review the finished pull request. Addy Osmani calls this loop engineering.

The numbers are public, with methods, baselines and limits:

The bug-fix report covers three Kimai bugs, from ticket to pull request in about 13 hours, estimated review time included. A developer and a QA engineer using AI copilots would need 148 hours. None of the three fixes adds an abstraction it doesn't need.

The regression-test report covers 350 Playwright regression test cases: 43.3 hours estimated, against 191 hours for a Playwright agency.

I set this up for your team and coach your developers to run it. Start with an audit, a pilot on one backlog item, or a workshop. Each is bounded and priced upfront.

What I delivered for an open-source project

Three Kimai bugs fixed, ticket to pull request: ~11Γ— faster and cheaper

Regression tests, 55 of 350 test cases landed: whole backlog estimated ~4Γ— faster, ~3Γ— cheaper

Who I work with

<aside> 🍸

How this ends: you own the product and the customers. I build the process that ships your decisions, which your team runs without me.

</aside>

How we can start

1️⃣ Delivery Audit

Fixed-fee assessment of how ready your team is to let agents build from your backlog.

2️⃣ Pay-on-Merge Pilot