6 min readAgentic delivery, Evidence
Quoted nine weeks, built in an evening: what actually happened
The plan said 52 to 63 developer-days. The designer shipped the same evening. Here's the process that made that possible, and the parts that still took time.
By Gary Kellett, architect, fractional CTO and chief AI officer
On 22 September I wrote a plan for the visual rule designer in Condexa. It was an honest plan, the kind any delivery lead would recognise: front end 41 to 49 days, back end 11 to 14, about nine to ten weeks with two developers.
By 11:45 that night, eight build phases had been committed: the API, the scaffold, the canvas, the inspector, run history, the reference editors, hardening and deployment. The pull request merged the next day after a round of UX fixes.
The speed didn't come from the AI typing faster than a person. It came from three things. First, the plan existed before the build, with phases small enough to test. Second, several agents worked in parallel on separate parts, each in its own workspace. Third, nothing merged without passing its tests, so there was no long tail of bugs to chase afterwards.
What still took time? The decisions. What should the designer feel like, what should a non-developer be able to do, what should they never be able to break. Those are the questions I spend my time on now, and they're the questions my clients are really paying for.
The estimate was written for a conventional team, so the fair comparison is team-weeks of estimated effort, not a claim that one person is fifty times faster. Production hardening, performance runs and penetration tests follow as normal steps.