A chat interface, already built
Conversations, history, files and shared prompts — deployed and working in your environment before we write a line of custom code.
Custom AI setup, end to end
One AI system, wired into everything your business already runs.
We install a working setup — chat your team will actually use, the models you choose, behind your own login — then connect it to the systems you work in every day. Including the ones that were never built to be connected.
No platform licence. No lock-in. It runs in your environment.
60%
less time advisers spend hunting for product and compliance answers
78%
of customer enquiries resolved without a human, at 92% satisfaction
Yours
the tools we build are handed over as code you own, not rented back to you
01 — The setup
The base is already built. We don't start from a blank page.
Most of an AI rollout is plumbing everybody rebuilds badly. We arrive with that part finished, so the work goes into the parts that are actually yours.
The models you pick
Claude, GPT, Gemini, or open models on hardware you control. Different models for different jobs, and swapping one out later doesn't mean rebuilding anything.
Your login, your permissions
We put an account layer over the top — your SSO if you have it, a simple one if you don't — so who can reach which system follows your org chart, and every action is logged.
02 — Integrations
Three ways we connect a system. We use whichever is cheapest for you.
An assistant that can't touch your systems is a search box. Every connection is a real tool the model can call, with its own permissions and its own audit trail.
Turned on, not built
The systems most businesses already run on. These we switch on rather than write.
- Google Workspace
- Microsoft 365
- Slack
- Salesforce
- HubSpot
- Xero
- Jira
Built before, adapted to you
Tools we've already written for systems like yours — a booking platform, a claims system, an industry database — reshaped to your fields, your rules, your terminology. You pay for the fitting, not the build.
The ones only you need
The process that exists nowhere else because it's how your business actually works. We write it, document it, and hand it over as code you own.
03 — The hard systems
We automate the systems that were never meant to be automated.
Much of what a business runs on has no usable API — the freight portal, the twenty-year-old ERP, the industry system with a login page from another decade. That's usually where the integration project quietly dies. It's the part we solve.
Observe
A browser extension sits with the people who do the job and records what the application actually sends while they do it — the real requests underneath the screen, not the clicks on top of it.
Derive
From that traffic we work out the interface the vendor never published: the endpoints, the parameters, how a session is held, what a valid response looks like.
Automate
Then we build a real tool against it. A proper integration, driving the system directly — not a script pretending to be a mouse, and nothing that breaks when a button moves.
We only ever observe systems you already have the right to use, with your people, on your say-so. Nothing is captured outside the applications you nominate.
04 — How it runs
Four steps, and you own what comes out of it.
Sit with the people doing the work
Not a workshop with the executive team. We watch the actual tasks, list the actual systems, and find the handful of jobs where this pays for itself first.
Stand the system up
Chat, models and logins go live in your environment. Your team can use it before a single custom integration exists — and that's the point.
Connect the systems, easiest first
Off-the-shelf connections go in immediately. The awkward ones get the observation work. Each tool lands in the assistant as it's finished, so value arrives piece by piece rather than all at the end.
Hand it over, then keep it alive
Documentation, source and credentials are yours. Vendors change their systems and models improve — we stay on to keep the tools working and add the next ones.
Tell us which systems are the painful ones.
You describe the work your team repeats and the systems that don't talk to each other; we tell you honestly which parts we can automate, which we can't, and what it would take.
- No preparation needed — bring the frustrations, not a requirements document.
- You leave knowing what's feasible and roughly what it costs.
- If it isn't worth doing, we'll say so.