The ToBa Method
Think. Orchestrate.Build. Accelerate.
A four-phase method that takes you from a messy, manual process to a production system your team owns, without the 12-month roadmap or the guesswork.
T
01
Think
Understand the real problem
O
02
Orchestrate
Design the system end-to-end
B
03
Build
Engineer, test and ship
A
04
Accelerate
Measure, improve and scale
Four phases
How each phase works.
Every phase ends with something tangible you can review, approve and keep, even if we stop there.
T
Think
Week 1–2
What is actually slowing the business down?
We interview the people doing the work, shadow the process and audit your tools and data to find the bottleneck worth solving first.
Stakeholder interviews & process shadowing
Systems, data and integration audit
Opportunity sizing and ROI scoring
You walk away with
Problem brief
Process map
ROI model
O
Orchestrate
Week 2–4
What should the system look like end-to-end?
We design how people, AI, software and existing tools fit together, and validate it with a prototype before writing production code.
Solution architecture & data flows
UX flows and clickable prototype
Guardrails, roles and approval paths
You walk away with
System blueprint
Prototype
Delivery plan
B
Build
Week 4–11
Ship it, safely and visibly.
A senior squad builds in weekly increments. You see a working demo every week and can change direction without derailing the project.
Weekly sprints with live demos
Automated tests & evaluation suites
Integration with your stack & SSO
You walk away with
Production system
Test suite
Runbooks
A
Accelerate
Week 12+
Make it faster, smarter and bigger.
After launch we monitor real-world performance, tune models and workflows, and roll the system out to new teams and use cases.
Usage, accuracy & cost dashboards
Model tuning and workflow expansion
Team training and adoption support
You walk away with
Impact report
Roadmap v2
Trained team
Typical timeline
Twelve weeks from kickoff to live system.
Every project is scoped individually, but most first systems follow this rhythm. Phases overlap so momentum never stalls.
W1
W2
W3
W4
W5
W6
W7
W8
W9
W10
W11
W12
Think
Discovery
Audit & interviews
Orchestrate
Design
Blueprint & prototype
Build
Engineering
Weekly sprints & demos
Accelerate
Optimise
Launch
Week 0 · Kickoff
Goals, success metrics and access agreed.
Week 4 · Blueprint sign-off
Architecture and prototype approved.
Week 8 · First release
Pilot users working in the live system.
Week 12 · Launch
Full rollout, handover and training.
Principles
The rules we don’t break.
Six commitments that shape every engagement, whether it’s a two-week sprint or a multi-year partnership.
01
Outcomes over output
We measure success in hours saved and revenue unlocked, not tickets closed or features shipped.
02
Senior people, small teams
The people in the discovery call are the people writing the code. No hand-offs to juniors.
03
Ship every week
Working software every Friday. Progress you can click, not status reports you have to trust.
04
Humans stay in charge
Automation handles volume; people own judgment. Every system has clear approval and override paths.
05
Boring tech where it counts
Proven, well-supported tools for the core, and cutting-edge AI only where it creates real leverage.
06
You own everything
Code, models, prompts, data and infrastructure live in your accounts from day one.
Ownership
Everything we build is yours. No lock-in.
Many agencies keep the keys so you keep paying. We do the opposite: from the first commit, the system lives in your accounts, and at handover your team is trained to run it, with or without us.
30 days
hypercare after launch
100%
IP transferred to you
0
proprietary lock-in
Source code & repositories
Clean, documented code in your GitHub or GitLab.
Infrastructure as code
Reproducible cloud setup in your own AWS, GCP or Azure account.
Prompts, models & configs
Versioned prompts, evaluation sets and model settings.
Docs, runbooks & training
Everything your team needs to operate and extend the system.
FAQ
Questions about how we work.
Still deciding if the method fits your team? We’re happy to walk you through a real project plan.
Talk to a Lead
Can we start with just the Think phase?
Yes. Many clients start with a two-to-three week discovery sprint. You keep the blueprint and ROI model whether or not we build it together.
How involved does our team need to be?
What if priorities change mid-build?
Do you work with our in-house engineers?
What happens after launch?
Start Here
Two worlds, one team. One unlocks intelligence and removes systemic friction. The other builds high-fidelity digital touchpoints that capture attention.