ZirolyZiroly is a Polish e-invoicing and accounting app for sole traders and accounting offices, connected to the national KSeF system, with a backend, a web app and a mobile app. It is our own product, and the first team we took through AI enablement. Every number on this page comes from its git history and deploy pipelines.
Monthly averages. Before AI: October to December 2025. With AI: January to October 2026, every full month since the switch.
Before
After
The enablement
No training days and no slide decks. The changes went into the repos, the backlog and the pipelines, the same way we run the 8-week Sprint for clients.
From mid-January 2026 AI coding agents became part of daily work, with a person reviewing and merging each pull request.
A dedicated dev-agent repo holds the instructions, conventions and workflows the agents follow. It grew through 86 pull requests.
In February 2026 the Trello bug list became tasks the agents could pick up inside the repo. February was the busiest month, with 187 merged pull requests.
Production deploy pipelines for the backend and, from May 2026, the web app, so merged work actually ships.
A security-docs repo with 79 pull requests, and dedicated security weeks from October 2026.
Month by month
Merged pull requests per month in the product repos, with the number of people who contributed that month underneath. Output went up while the team got smaller.
Aug
2025
Sep
Oct
Nov
Dec
Jan
2026
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
February 2026 was the backlog month, when the old bug list became agent tasks. August and September 2026 were quieter, with 2 to 3 people. We show them anyway: a before-and-after you can trust has to include the slow months too.
| Metric | Before AI | With AI |
|---|---|---|
| Merged pull requests | 294 | 921 |
| Merged pull requests per week | 12.0 | 21.6 |
| Commits per week | 26.7 | 32.2 |
| People committing in an average week | 4.2 | 2.8 |
| Pull requests per active person per week | 2.8 | 7.7 |
| Median pull request size (lines) | 267 | 193 |
| Feature pull requests | 72 | 343 |
| Security pull requests | 11 | 62 |
Before AI: 29 July 2025 to 15 January 2026 (24 weeks). With AI: 16 January to 9 November 2026 (43 weeks).
Backend
2 to 46
successful production deploys
Web app
0 to 48
production pipeline added in May 2026
Mobile app
45 to 349
merges to main, each one a production release
The data comes straight from GitHub: merged pull requests by people (bots excluded), non-merge commits on each default branch, and successful runs of the production deploy workflows. It covers the five product repos: backend, backend framework, web, mobile and landing page.
A person counts as on the team in a month if they made a commit or merged a pull request that month. People joined and left at different times, so we compare by team size each month.
Pull requests are an activity measure, not a quality measure. Next we are adding change failure rate and review wait time, the same metrics we baseline for clients in the AI Engineering Snapshot.
The one-week Snapshot measures your delivery from git, CI and Jira, and shows where AI would pay off first. The fee is credited to the Sprint if you go ahead.