AI use and access, for mid-sized businesses
AI at work, on rules your business sets.
Is your team already using AI tools? We write clear rules on what goes in, who sees what and what you spend, then hand them to your team.
You will recognise this if
Does this sound like your team?
- Your team pastes customer details into a free AI app because it is quick.
- Someone uploaded a file to a chat last week. Today nobody can find it.
- The whole team shares one login, so everyone sees everything.
- You asked an AI about your business and it answered like a stranger.
- The AI bill went up again, and nobody can say which job caused it.
- You like your AI tool, but switching would mean starting from zero.
If a few of these sound like your team, AI is running without rules. Writing the rules is the first thing to fix.
Before and after
What the setup is built to do
These are aims. We have no measured results to show yet.
Where to start
Pick your biggest problem. Fix that first.
Your work is locked inside one tool
Not sure where uploaded files end up
Everyone sees everything
Answers come back thin and uneven
AI costs keep creeping up
Every answer starts from zero
Where your files sit
In storage you own, such as your own cloud account. We hold no copy. The plan you choose sets what each tool’s maker may do with what it reads.
Which data you may use is a legal question. Your adviser decides it, and we set up the rules they give. We give no legal advice.A setup your team cannot run goes stale, so it is handed over with the rules in writing.
How the work runs
How an engagement runs
Sit down with the people who use AI tools. List the tools, the plans, who has access and what has been uploaded.
Choose plans that protect your data, set who sees what, and write down what may never go in.
Files and notes go into storage you own. Your sheets, mail and WhatsApp are connected. You and our team write one short note on how your business works.
Your team runs real jobs through the setup and sees what each one costs.
Your team holds the logins and the written rules, and one named person runs them.
What an IT head will ask
Each department gets its own folder and logins. One named person on your team keeps the list current.
It sits beside your ERP and your Excel files, and replaces neither.
Your team holds the logins and the written rules, and one named person runs them.
That person is the first call. Support after handover is agreed in the quote.
They are listed first. Each is kept, moved to storage you own, or deleted where the tool allows.
Common questions
A build, then a handover. For this work there is no product to subscribe to. The setup lives under your own logins, and your team owns it afterwards.
Whichever fits the job and your budget. Your files and notes stay in storage you own, so you can change the tool later without starting again.
On your own systems. We build in your sheets and storage, and nothing is copied into a database we hold. When an AI tool reads a file, the plan you chose sets what its maker may do with it. That is why the plan is part of the setup.
That is a legal question. Your own adviser decides it, and we set up the rules they give. We give no legal advice.
Yes, beside them. It sits next to your ERP and your Excel files and replaces neither.
That is the aim. A setup your team cannot run goes stale, so we build it with your team and hand over the rules in writing. Support after handover is agreed in the quote.
The first conversation is free. After it, the work is scoped to what your business needs and quoted in writing before anything starts.
Make a start
Start with the worry that costs you most.
A free conversation. Bring the AI problem that worries you most. You leave knowing where the first fix would start.