Services
Two tracks. A plan before you spend, or a build because you already know. Both are done by the same people, so the plan never promises what the build cannot deliver.
Workshops with leadership and with the people actually doing the work. We list candidate use cases, score each on feasibility, risk and return, and rank them. The first pilot comes back scoped to a fixed price.
You get- Prioritised roadmap
- Pilot scope and price
- Maturity snapshot
- A list of what we would leave alone
Right for you ifYou know AI should be doing something here, but not what, and you do not want to spend to find out.
A risk assessment of what is already happening in your business, a governance framework sized to your organisation rather than a multinational, and the documentation an auditor will ask for. We write policies people will actually read.
You get- Risk register
- Governance framework
- Responsible-use policy
- POPIA, GDPR and ISO audit pack
Right for you ifA board, an auditor or a client has started asking questions you cannot answer yet.
Role-specific sessions for finance, operations, sales or support: what these tools do well, what must never be pasted into one, and how to check an answer before you act on it. Your team leaves with material they can use that afternoon.
You get- Training sessions
- Prompt library for their actual work
- One-page internal usage policy
Right for you ifAdoption is uneven, output quality is a lottery, and nobody has told anyone what the rules are.
What four weeks
actually looks like.
Our discovery engagement, week by week. Nothing here is a workshop for its own sake: by week three there is a rough working version of the hardest idea, so the roadmap is grounded in something that ran.
- Week 1
We listen
Sessions with leadership and with the people doing the work. We watch the process rather than ask about it.
- Week 2
We score
Every candidate use case gets a feasibility, risk and return score. Some get struck off, and we say why.
- Week 3
We test the hard one
The top candidate gets a rough working version against your real data, so the roadmap is not a guess.
- Week 4
You decide
A ranked roadmap, the first build scoped to a fixed price, and a clear list of what we would not touch.
How we price.
No day rates you cannot forecast, and no licence that punishes you for adding people.
Fixed price, agreed before we start.
You know the number and the end date on day one. If the scope changes, we re-quote rather than run a meter.
Fixed project scope, priced against the saving.
Where the outcome is measurable, we price against what it recovers or saves. Where it is not, we say up front what we will measure instead.
Monthly retainer with a stated response time.
Optional. Plenty of clients take the handover documentation and run it themselves, which is the point of writing it properly.
Everything.
Systems run in your Google Cloud, Microsoft or AWS account, on your data, with documentation good enough for someone else to take over. Nothing is held hostage, and the AI model underneath can be swapped without a rebuild.
Not sure which track you need?
That is what the call is for. Describe the work; we will tell you whether it is a plan or a build, and what it would cost to find out.