AI Build Sprint

Who this is for

You have a clear AI feature to ship, a budget to ship it, and a team that is either not large enough or not deep enough in AI production to carry it alone. Typical shapes: a RAG system that has to reach faithfulness ≥ 0.85 to get past legal signoff, a multi-agent workflow that has to handle 10x production traffic by a specific date, a migration from a brittle prompt chain to a reliable LangGraph architecture with real evals.

What we deliver

• Written statement of work on day one, signed by both sides. Scope, exclusions, acceptance criteria, timelines. Any scope change is a written amendment before work continues.
• Weekly demo every Friday. You see live working software, not slides. What shipped, what is next, what I am blocked on.
• Code in your repo, deployed to your infra. No black-box handovers. Your engineers learn by watching the work land.
• Production infrastructure included: CI/CD pipeline, eval harness gated on pull requests, structured logging with correlation IDs, cost guardrails, retry logic with exponential backoff and jitter, graceful-degradation fallback.
• 30-day production warranty. Defects found in the delivered scope are fixed at my cost during the warranty window.
• Handover to your team at the end: runbook, architecture doc, on-call playbook, recorded walkthrough.

How it runs

Week 0 (pre-engagement): discovery call, written proposal in 48 hours. Week 1: architecture spike, data model, eval set definition, signed SOW. Weeks 2–6: building, with weekly demos and pull-request review cadence. Weeks 7–8 (if needed): hardening, load test, handover.

Deliveries scope themselves to the 4–8 week window. If the real ambition requires 12 weeks, we scope it as two sequential Sprints with a go/no-go gate between them.

FAQ

Why is it fixed price if the work is uncertain?

Because T&M incentivises slowness. Fixed scope and fixed price means my incentive matches yours: ship well, fast. Genuine scope changes are handled in writing with a written amendment, before the next invoice.

What if the spec is still fuzzy?

Then the right first step is the Production Audit or a paid Discovery Sprint (one week, £8,500) where the deliverable is the SOW for the full Build Sprint. We tighten the scope until fixed pricing is safe for both sides.

Will you work with our existing engineers?

Yes — that is the point. Your team owns the code afterwards. They pair on PRs, sit in on demos, and learn the patterns by doing. No "consultant leaves, nobody knows how it works" situations.