01 · Northwind / Services
Tell us the workflow.
We’ll name it.
Six services, each scoped around a real operational workflow. If you are not sure which one fits, three questions below usually narrow it to one or two.
3
Questions
6
Services
30 s
To a shortlist
02 · Three questions
Answer these,
and the shortlist gets short.
Do you already know the use case, or are you comparing a few?
Is the work mostly a repeatable multi-step task, or answering questions from documents?
Is the starting point documents that need to become data, or a model that needs to stay accurate?
Rolling this out firm-wide instead of one workflow? That’s AI Enablement & Training
03 · Side by side
Six services,
one honest comparison.
Best when
Typical timeline
Starts from
You leave with
Typical outcome
Pairs well with
In production at

01 · Strategy
AI Strategy & Readiness
Several candidate use cases, no shared way to rank them
2–5 weeks
$18k
A ranked use-case matrix and a costed 12-month roadmap
5 weeks
average time from kickoff to a signed roadmap
Pilot, on the top-ranked use case

02 · Agents
Agent & Workflow Automation
A repeatable multi-step task eats skilled hours
8–14 weeks
$65k
A production agent, its eval harness and a review queue
63%
average reduction in manual processing time
Document AI, Data & MLOps

03 · Knowledge
Knowledge & RAG Systems
People answer questions from policies and past cases
6–12 weeks
$65k
A cited assistant, a gold question set, a grounding score
38%
faster average resolution time on grounded queries
Enablement, Data & MLOps

04 · Documents
Document AI
Unstructured documents have to become trusted data
10–16 weeks
$65k
An extraction pipeline with field-level thresholds
91%
average straight-through processing rate
Agents, Knowledge & RAG

05 · Data & MLOps
Data & MLOps Foundations
A model that was right at launch is quietly drifting
12–20 weeks
$65k
Pipelines, drift alerts, scheduled retraining, runbooks
6.4 pts
average improvement in forecast accuracy (MAPE)
Any system already in production

06 · Enablement
AI Enablement & Training
Rolling AI out across teams, not one workflow
8–12 weeks
$32k
Curriculum, governance playbook and adoption targets
71%
average weekly active use within 90 days of rollout
Strategy & Readiness
Fees are starting points; every engagement is quoted as a fixed fee
04 · Proof, by service
Whichever one you picked,
it has shipped somewhere.
05 · All six, for reference
The full list,
if you’d rather browse.

2–5 weeks
01
·
Strategy
AI Strategy & Readiness
A structured assessment of your data, infrastructure and use cases, ending in a prioritized 12-month AI roadmap.
See how it works

8–14 weeks
02
·
Agents
Agent & Workflow Automation
Production-grade AI agents that execute multi-step operational workflows, with human review where it matters.
See how it works

6–12 weeks
03
·
Knowledge
Knowledge & RAG Systems
Retrieval-augmented assistants that answer from your own documents, policies and systems of record, with citations.
See how it works

10–16 weeks
04
·
Documents
Document AI
Extraction, classification and routing pipelines that turn unstructured documents into structured, trustworthy data.
See how it works

12–20 weeks
05
·
Data & MLOps
Data & MLOps Foundations
The pipelines, feature stores and monitoring that let models stay accurate after launch, not just at demo time.
See how it works

8–12 weeks
06
·
Enablement
AI Enablement & Training
Hands-on training, governance playbooks and adoption support so your team owns what we build.
See how it works
06 · Still deciding
A few more
questions before you book.
If none of this settles it, that is what the readiness call is for.
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?

07 · Start
That’s what
the call is for.
Describe the workflow, even roughly. We’ll tell you which service fits, or whether it needs an Assessment first.



