Services

Review, control, build, and hand over.

Four parts of one engagement, for businesses that want AI used on client work in a way leadership can account for. We work inside your business with your IT and operations people, on the systems you already run, and leave behind work your team can check and maintain.

Talk to us

The work

What each part covers.

An engagement starts with the review. The later parts are scoped from what it finds, and you can stop after any of them.

Review what is already in use

Before anything is built, you need to know what is already running. We look at the AI tools in use across teams and support staff, the accounts behind them, whether those accounts are personal or company-managed, and what client information is flowing into them. This is for leaders and IT leads who suspect usage has moved ahead of policy and want a factual picture rather than a survey.

What you get

An inventory of AI tools, extensions and licences in use, and who holds each account
A map of which information goes into which tool, and where it is stored
A written findings report, ranked by risk to client confidentiality
A short list of what to change first, reviewed with your IT lead

Put controls around client information

Many fixes are configuration, not new software. We work with your IT team or managed service provider on single sign-on, tenant settings, data retention and access, so AI use runs through accounts you control and can audit. Changes are made under your change process, with your people, and written down as they happen.

What you get

Configuration changes made with your IT team, each recorded with its reason
Company-managed accounts in place of personal ones, behind single sign-on
Retention and sharing settings that match how you keep client files
A record of what changed and how to reverse it

Build AI into the work itself

Once the controls are in place, we build inside the systems you already run, such as document management and Microsoft 365. Examples include search across your own documents, first-pass document review, intake preparation and project summaries. Each build is scoped with the people who will use it, and respects the access rules already set.

What you get

A written scope for each build, agreed with the people who will use it
Working tools inside your existing systems, not a separate platform
Testing on real work with the people involved, before wider use
Source code and configuration that you own

Leave your team able to run it

The engagement ends when your team can run what we set up without us. We document the systems, train the people who use and support them, and draft a written AI usage policy for leadership to review and adopt. Nothing should depend on us staying.

What you get

Runbooks for your IT team or managed service provider
A training session for users, plus one for the people who support them
A draft AI usage policy written for leadership to review
A closing note on what was done and what to watch next

Where we fit

Alongside your IT team, not in place of it.

Your IT team or managed service provider keeps the business running, and that does not change when we arrive. We bring the review, the configuration detail and the builds. They keep ownership of the environment, the change process and the support afterwards.

Your IT team: Owns the environment and approves changes
Tanto: Reviews, configures and builds alongside them
Systems: Your document systems, Microsoft 365 and existing identity setup
Access: What you grant, read-only wherever that is enough

Scoping

Talk through what a first review would cover.

A scoping call with a leader, your IT lead or your operations lead. We ask how your business works today and agree what the review should look at.

Book a scoping call