Process
Four phases, each with a door out.
Weeks are ranges we stand behind. Skip a phase when you already have what it produces. Each phase is priced before it starts.
-
01
Assess
- How long
- 1 to 2 weeks
- What happens
- We read your data, your tools and the decision the system has to make, then say what is worth building and what is not.
- What you get
- An assessment document: the recommended shape, the risks, the plan for the next phase.
-
02
Prototype
- How long
- 2 to 4 weeks
- What happens
- A working slice on your real data, evaluated against cases your team writes, so the go or no-go is based on evidence.
- What you get
- A prototype you can put in front of people, with its evaluation results.
-
03
Production
- How long
- 4 to 8 weeks
- What happens
- The system built to survive: retrieval, checks, monitoring, delivery inside the tools your team already uses.
- What you get
- A production system, a runbook, and the handover to whoever runs it with us.
-
04
Run
- How long
- Ongoing
- What happens
- We watch it, evaluate it, fix what real usage breaks and report what changed in plain language every month.
- What you get
- Monitoring, evaluation and a monthly report you can read in ten minutes.
What stays the same in every phase
Your evaluation set decides
Your team writes the cases. The system passes them or it does not ship.
Your cloud, your keys
Everything is deployed into your account. Our access can be removed in a day.
Written down
Model choice, limits and known failures are documented, so decisions can be revisited.
A door out
Each phase produces something you can use without the next one.
Scope a project
Pick what fits. The plan draws itself as you go, and the link carries your answers.