Ten days to a decision you can defend
A fixed-scope engagement that tests one AI use case against your data, your infrastructure, and your business case. It ends with a recommendation you can take to the board: proceed, pause, or stop.
What happens in the ten days
The clock starts when kickoff ends and data access is confirmed. The schedule below is working time, not calendar hope.
- Day 1
Alignment
- Kickoff with business and technical stakeholders
- Define the target workflow, success metrics, and ROI assumptions
- Confirm data sources, access, and compliance constraints
- Set the communication cadence for the sprint
- Days 2-4
Discovery and data audit
- Audit data quality, coverage, and labeling gaps
- Review infrastructure, integrations, and security boundaries
- Interview the people who own the process today
- Score production readiness across data, platform, and process
- Days 5-7
Feasibility and ROI modeling
- Test candidate architectures against your constraints
- Model expected value, cost, and implementation risk
- Run sensitivity analysis on the assumptions that matter most
- Select a recommended approach worth defending
- Days 8-10
Roadmap and briefing
- Assemble a phased roadmap with milestones and owners
- Write the go/no-go recommendation and its evidence
- Brief technical and executive stakeholders
- Hand over all documentation and next actions
Five documents, built to be used
Each deliverable is written so your team can act on it without us in the room.
- 01
Data Quality Scorecard
Where your data is strong, where it is thin, and which gaps block production ML.
- 02
Technical Feasibility Report
Candidate architectures assessed against your constraints, dependencies, and security boundaries.
- 03
ROI and Business Case Model
A cost and benefit model with explicit assumptions, scenarios, and expected payback.
- 04
Production Roadmap
A phased delivery plan with milestones, owners, and decision gates.
- 05
Go/No-Go Recommendation
A direct recommendation with the evidence, tradeoffs, and risks behind it.
Terms without surprises
- Duration
- 10 business days, counted from confirmed data access
- Team
- A project lead and a technical lead, with specialist support where needed
- Pricing
- Fixed price, set in the proposal after a discovery call confirms scope
- From your side
- A decision owner, access to the relevant data, and interview time in week one
The price includes all five deliverables, the executive briefing, and 30 days of follow-up support. No day rates, no open-ended consulting.
Asked before every sprint
- What if the recommendation is "stop"?
- Then the assessment did its job. A documented stop costs ten days; discovering the same thing after an eight-month build costs far more. We only take engagements where a no-go is an acceptable answer.
- What do you need from us?
- A decision owner, access to the relevant data, and a few hours of stakeholder time in the first week. If data access is not ready, the clock does not start.
- What happens after the ten days?
- You get 30 days of follow-up support while you act on the roadmap. If the recommendation is proceed and you want us to build it, we prepare a separate implementation proposal. There is no obligation either way.
- Why fixed scope instead of day rates?
- Because the sprint exists to answer one question. A fixed scope keeps us accountable to the answer, not to the hours.
- Can you assess several use cases at once?
- One use case per sprint. If you have several candidates, the discovery call helps pick the one with the strongest evidence behind it.
Find out if your use case is worth building
Book a discovery call. Within one conversation we will tell you whether the assessment fits your situation, and what we would test.
- ProceedBuild, with evidence and a roadmap
- PauseFix what is missing first
- StopSave the budget for a better bet