Most AI projects fail not on the technology but on duration. The longer a project drags on, the more the context shifts, the more enthusiasm fades, and the higher the bill climbs. Our answer: a tightly scoped 21-day sprint that forces decisions and ships something usable at the end. This format is reserved for well-bounded use cases whose ROI has already been validated at scoping.
Week 1 — Scope and prototype
The first days aren't for coding but for cutting uncertainty. We write down the quantified success criterion (for example: 'handle 80% of incoming emails without human intervention'), we gather real data, and we build a throwaway prototype by day 3 or 4. The goal is to prove the core works before investing in everything else.
- Day 1-2: scoping workshop, defining the success criterion and edge cases.
- Day 3-4: data access, first prototype on a real sample.
- Day 5: internal demo, go / no-go decision, scope adjustment.
If the core of the system isn't convincing by day 5, better to know now than three weeks later.
Week 2 — Build for real
Once the go is confirmed, we move from the throwaway prototype to a real implementation. This is where the essentials play out: integration with existing tools (CRM, mailbox, ERP), error handling, guardrails on model outputs, and logging to audit what the AI does. An AI agent in production with no logs and no net is a time bomb. We work in daily increments visible to the client, which avoids the tunnel effect.
Week 3 — Harden and ship
The final week separates a demo from a product. We deploy first in supervised mode, with a human validating, before switching to autonomy, then we run the handover: documentation, access and a point of contact for the first 30 days.
- Load tests and edge cases identified in week 1.
- Error-rate measurement on real cases at volume.
- Monitoring dashboard: cost per task, success rate, alerts.
- Supervised deployment then gradual switch to autonomy.
Let's be honest: a sprint ships a scope, not an infinite platform. Enhancements, new use cases and cost optimisation are handled afterwards, once the tool has proven itself in the field. That's precisely the point of the format: prove value fast, then invest with eyes open. Got an idea to scope? Write to us at contact@nexus-os.fr.