How we figure out an organization.
Five stages, always in this order. Each one makes the next one simpler, cheaper and more reliable — and each one produces something your team keeps.
Stage 01 · Ontology · Weeks 1–3
Name what exists.
Workshops with the people who do the work. We map the entities, relationships and rules your business runs on, and settle what each term means.
Questions we answer
- ?What is a customer, exactly?
- ?Which system is right when two disagree?
- ?Who owns each definition?
What you keep
- Entity graph
- Glossary
- Systems-of-record map
Stage 02 · Structure · Weeks 2–5
Decide where truth lives.
A target architecture on top of the ontology: systems of record, data contracts, integrations and a migration path that keeps the business running.
Questions we answer
- ?What do we keep, wrap or retire?
- ?How do systems agree on one record?
- ?What has to move first?
What you keep
- Target architecture
- Data contracts
- Roadmap
Stage 03 · Workflows · Weeks 4–8
Redesign how work moves.
We trace the handoffs, waiting and judgement calls, then redesign each workflow so people make decisions and systems do the rest.
Questions we answer
- ?Where does work wait?
- ?Which steps need judgement?
- ?What can run on its own?
What you keep
- Process maps
- Decision points
- Automations
Stage 04 · Intelligence · Weeks 6–12
Put AI to work.
Agents and copilots grounded in the ontology, evaluated against real cases and placed inside the redesigned workflows — with humans in the loop where it matters.
Questions we answer
- ?Which decisions can AI support?
- ?How do we know it is right?
- ?What does each task cost?
What you keep
- Agents
- Copilots
- Evaluation
- Governance
Stage 05 · Delivery · Continuous
Ship the surfaces.
The web, mobile and internal products people use every day, shipped in weekly increments by the same team — then handed over or run with you.
Questions we answer
- ?Who uses this, and where?
- ?What ships first?
- ?Who runs it after launch?
What you keep
- Web
- Mobile
- Internal tools
- MVPs
Four rules we do not trade away.
Model before you build
The most valuable work happens before a line of code: naming what exists, where truth lives and how work actually moves. Software built on a clear model stays simple.
One senior team, end to end
Strategy, architecture, design and engineering sit in the same room. No account layer, no deck handed to a junior bench to implement.
Built to be owned
You get the ontology, the architecture, the repositories and the documentation. Your own team can run and extend it — no lock-in.
Proof over promises
A working demo every week and numbers that come from the work. If a metric is not on file, it does not go on the site.
Start with a diagnostic,
not a sales deck.
Three ways in. Most organizations start with a Depth Diagnostic on one domain, then move into a phased program.
Depth Diagnostic
Fixed fee
A focused assessment of one domain: the ontology, the systems, the workflows and where AI can do real work. Ends with a roadmap you can act on with or without us.
- Stakeholder workshops
- Domain ontology & glossary
- Systems and workflow map
- AI opportunity map
- Prioritized roadmap
Transformation Program
Scoped per phase
Ontology, architecture, workflow redesign and AI systems delivered in phases, each with a fixed scope and a working demo every week.
- Everything in the Diagnostic
- Target architecture & migration
- Workflow redesign & automation
- Agents and copilots in production
- Web, mobile and internal tools
Embedded Partner
Monthly
A senior pod that stays on: evolves the ontology, ships releases, monitors AI systems and keeps the roadmap moving.
- Architect + engineers
- Monthly releases
- AI evaluation & monitoring
- Quarterly roadmap review
- Fixed scope per phase
- A working demo every week
- You own every artefact
- One senior team, start to finish