01 · Northwind / Services
Six services.
One process behind them.
Every engagement starts with a workflow, not a model. These are the six ways that workflow usually ends up automated, evaluated and running in production.
6
Services
64
Systems in production
11 wks
Median to launch
02 · Pick a starting point
Most engagements start
with one of these.
01
2–5 weeks · Typical timeline
03 · Before anything gets built
Scope is a deliverable,
not a guess.
Whatever service it starts with, every engagement goes through the same scoping steps before a statement of work gets signed. You keep the output even if you never hire us to build.
i
Workflow
walkthrough
Days 1–5
On site or remote
We sit with the team doing the work today, exceptions included, not just the documented happy path. Most of the real requirements live in the exceptions.
Shadow sessions with operators
3–5
Exception paths mapped
All
ii
Data & access
check
Days 5–8
What is actually available, what needs cleanup and what needs a new integration. We test access with real credentials, not a diagram.
Sources inventoried
Typ. 8–30
Access tested end to end
Yes
iii
Success criteria,
in writing
Day 9
The metric that decides whether this shipped or not, agreed before the build starts: an accuracy bar on a held-out set, a confidence band for human review and a cost ceiling per run.
Evaluation set drafted
200+ cases
Go / no-go metric signed
1 page
iv
Scoped statement
of work
Day 10
Timeline, deliverables and a fixed fee from our engagement models. Not an open-ended retainer, and never a price that moves after signature.
Fixed fee
Always
Named team
Before signing
04 · Proof, by service
Each service,
in production somewhere.
05 · Questions
Before you
pick a service.
Most workflows don’t fit one service neatly. The names are a map of what we do, not a menu.
01
How do services combine across one engagement?
Most engagements start with one service, often an Assessment or a single Pilot, and add others as the roadmap calls for them. A RAG build often pulls in Data & MLOps Foundations once it is in production.
02
Can we start with a Pilot instead of an Assessment?
03
Do you ever recommend against building something?
04
What if our use case doesn’t fit neatly into one service?
05
How is pricing structured?
06 · Start
Start with a call,
not a decision.
Tell us the workflow. We’ll tell you which service, or which sequence of services, actually fits it.