Capability
AI enablement
Your team set up to use AI properly on the work they actually do, built inside your own accounts so you own it outright and it keeps working whether or not you speak to us again.
The common pattern is a team with an AI subscription that a few people use for drafting and nobody uses for anything structural. The tool is capable, the gap is that nobody has sat with the actual workflows and worked out which parts are worth automating.
This is that work, done in person and built in your own accounts. You are not buying access to something we host. You are buying the setup, and then you own it.
Process
What the engagement looks like
-
Workflow walkthrough, in person
We sit with the people who do the work and watch how it is done now. Not a workshop with sticky notes, an actual walkthrough of the jobs that take the time. Most of the value of the engagement is decided here, because this is where we find out what is worth automating and what is better left alone.
-
A short written recommendation
What we found, what we would build, what we would not, and a price per automation. If the honest finding is that two of the five ideas are worth doing, that is what the document says.
-
Build, in your accounts
The automations are built where you can see them, in the subscription you already pay for, with your team shown how each one works rather than handed a finished black box.
-
Follow-up review, in person
We come back and look at whether the automations are being used and whether the time actually went where we said it would. Anything that is not earning its place gets fixed or dropped.
What you get
- An in-person walkthrough of the workflows as they are actually run.
- A written recommendation with a price per automation before any building starts.
- Automations built inside your own AI account, owned outright by you.
- Your team shown how each one works and how to change it.
- A follow-up in-person review of whether it saved the time.
Dependencies and limits
- You need your own AI subscription. That is a genuine dependency outside our control and we confirm it before booking the walkthrough.
- In-person work is available within reasonable travelling distance of Newcastle-under-Lyme. Further afield we will say so and discuss it rather than quietly adding travel.
- Automations depend on the provider’s platform. If they change how something works, it may need revisiting, which is what the callout rate is for.
- Some tasks are poor candidates for AI. We will say which, and that is part of what you are paying for.
Questions we get asked
Why build it in our accounts rather than yours?
Because then it is yours. You are not renting access to something we hold, there is no monthly fee attached to keeping it running, and if you never speak to us again it carries on working. It also means your data stays under your own agreement with the provider rather than passing through ours.
What do we need before you start?
Your own AI subscription, and a couple of hours of the people who actually do the work. The subscription is a genuine dependency and sits outside our control, so we confirm it is in place before the walkthrough rather than discovering it on the day.
What if we do not have an established workflow yet?
Then there is nothing to walk through, and we would go straight to building against what you describe, priced as a fixed one-off instead. Newly set-up businesses are a common case and it is not a problem, it just changes the shape.
How is this priced?
Per automation, quoted after the walkthrough has established what there is to build. Pricing before the walkthrough would be a guess. Maintenance is on demand at £100 a callout and phone support at £20 a call, neither required and neither bundled.
How do you know it actually saved us time?
We come back and check. The follow-up review looks at whether the automations are being used and whether the time went where we said it would. If something is not being used we would rather find out and fix or drop it than leave it sitting there.
Is our data safe in this?
Your provider agreement governs that, not us, which is one of the reasons for building in your accounts. We will point out where an automation would send something sensitive somewhere it does not need to go, and we will tell you plainly when a task is a poor candidate for AI at all.
Start with a conversation
Tell us what the system has to do and what it has to work alongside. You will get a written scope and a price before anything is committed, and your enquiry goes straight to the person who would build it.