Lead engagement
AI Architecture Sprint
A two to four week fixed-fee engagement. It ends with a decision-ready deployment plan: one process, one architecture, and costs you can put in front of a committee.
Week by week
How the four weeks run
A two-week Sprint compresses weeks 2 and 3. The sequence does not change.
Discovery and process mapping
We sit with the team that runs the process today and map it step by step: inputs, decisions, exceptions, systems of record, and handoffs. We record volumes, cycle times, and where the work stalls.
Use-case selection and feasibility
We test each candidate against your data, your integration surface, and your compliance posture. Candidates that fail on data quality or access are dropped in this week, not after a build.
Solution architecture and build-vs-buy
We draw the reference architecture: models, data flow, hosting region, integrations, human review points, and audit trail. Where a licensed product beats a build, we say so and price both.
Roadmap, costing, and handover
We hand over a phased deployment roadmap with effort, cost, and risk per phase. Your team gets a working session on the plan so it can go into an internal note or a procurement file.
What you get
Deliverables
- Process map of the current workflow, with volumes and cycle times
- Prioritised use-case shortlist, ranked by feasibility and value
- Reference architecture, including hosting region and data flow
- Build-vs-buy analysis with pricing for both routes
- Phased deployment roadmap with costs per phase
What we need
From your side
- A named process owner who can answer questions and take decisions
- Access to current workflow documentation, SOPs, and sample records
- Two to three working sessions with the team that runs the process
Nothing else. We do not ask for a data-cleaning project before the Sprint starts.
Fit
Who this is for, and who it is not for
This is for you if
- You run a process with real volume that is staffed manually today.
- You want a costed plan you can take to a budget or procurement committee.
- You need the hosting region, audit trail, and review points settled up front.
- You expect the firm that designs the system to build and run it.
This is not for you if
- You want a market scan of AI vendors rather than a plan for one process.
- You need a proof of concept in a sandbox with no route to production.
- The process is undefined and no owner has been named.
- You cannot give access to workflow documentation or sample data.
Next step
Name the process. We will scope the Sprint around it.
Tell us which process you have in mind and roughly how many people run it. We reply with a scope, a fee, and dates.