Estimated before the build
Each estimate comes from a written plan, produced before any code, sized as a conventional team would size it. The plans are still in the repositories, dated.
Work / Evidence
Method
Each estimate comes from a written plan, produced before any code, sized as a conventional team would size it. The plans are still in the repositories, dated.
Built, tested and working against acceptance criteria. It does not mean production-hardened. Penetration tests, performance runs and identity set-up follow, and are part of a build engagement.
A team-week is the effort a conventional team would put in. Quoting it that way keeps the comparison fair and stops the claim sliding into a boast about our own speed.
At a glance
Condexa rule designer52-63 developer-days for two developers
9-10 weeksOne evening
Healthcare scheduling platformAbout 560 person-days across three phases
29 team-weeks2 days
KashPots refactorRoughly 5.5 working weeks for one engineer
5.5 weeks4 hours
Multi-tenant access-control framework248 person-days for 4.5 people
14 weeks5 days
Technology budget and approvals appSliced plan for a team of 4.5
15.5 team-weeks2 days
The log
| Build | Estimated before the build | Delivered | Evidence |
|---|---|---|---|
| Condexa rule designer | One eveningEight build phases committed in about 3.5 hours; merged the next day after UX fixes | Plan and commit history in the repository | |
| Healthcare scheduling platformClient work, anonymised | 2 daysAll three phases built and passing acceptance tests; phase two in about an hour | Phase plans and commit history | |
| KashPots refactor | 4 hours57 of 64 planned tasks (89%) complete in one morning | Refactor plan and branch commits | |
| Multi-tenant access-control frameworkClient work, anonymised | 5 daysWorking packages in a day; a remediated alpha with 822 automated tests in five | Plan, package feed and 191 commits | |
| Technology budget and approvals appClient work, anonymised | 2 days14.5 team-weeks of slices built and working | Slice plan and project notes | |
| PrezzyList | 3 daysIdea to live platform with CI/CD, observability and a full onboarding epic | 26 commits, 28-30 September 2026 |
Sources: dated plans, git history and project notes. Client builds are anonymised with permission.
What the research says
In a randomised trial, experienced open-source developers were 19% slower when they used AI tools, while believing they were faster.Read the source (METR, 2025, opens in a new tab)
AI amplifies whatever engineering practice is already there. Strong teams get stronger; weak practice gets louder.Read the source (Google DORA, 2025, opens in a new tab)
So the speed does not come from the tool. It comes from the process and the architecture discipline around it. That is what you are buying.
In 30 minutes you'll know whether to fix it, buy it, build it or leave it. No pitch deck.
We reply within 2 business days.