Two engineers rebuilt a FedEx supplier's billing core in 3.5 months vs an estimated 7-8
alex_verem · x · 2026-10-27
A delivery orchestration platform serving FedEx estimated a 7-8 month rebuild of its core billing system. A pod of 2 full-stack engineers, supported by an AI productivity lead and a part-time PM, rebuilt the core in 3.5 months, merging 122 PRs in the first 90 days; production went live by month 6.
Key practices:
- Context before code: no coding in the first two weeks; the legacy system was a no-code tool grown into a billing engine with undocumented rules, reverse-engineered from production data
- Core was done in roughly half the estimate; getting to production took longer
- This was the author's first "AI Velocity Pod" delivery model
A concrete data point on how small AI-augmented teams speed up enterprise rebuilds — and why deployment, not coding, is the bottleneck.
More from coding & agent
- Chrome team explains WebMCP: agents get tools from your website, not a replacement for MCP — rseroter · 2026-10-27
- Agent-Native apps: why agents bypassing your UI can break business rules — rseroter · 2026-10-27
- 'My intelligence stack': developer splits AI coding work across Opus 5.5, Fable and Astra with human review gates — sh_reya · 2026-10-27
- Baseten webinar: evaluate open models for coding agents by benchmarking on your own merged PRs — baseten · 2026-10-27
- Thorsten Ball on working with agents: run more evals, automate everything, use the best models — omarsar0 · 2026-10-27
- Where to draw the approval line for scheduled agent jobs — Reddit discussion — MemStrata · 2026-10-27