Connecting the apps you already use: small automations that add up
How to spot re-keying in your business, the small automations that stop it, and how to keep them documented, owned and easy to live with.
· 6 min readA practical, low-risk way to begin using AI in a small business, starting with everyday tasks, the tools you already have and a few simple guardrails.

If you run a small business, you've almost certainly been told that AI will change everything. It's on the news, in your inbox, and probably mentioned by a supplier or two. It's natural to wonder whether you should be doing more, and what "doing more" would even look like.
Here's the reassuring part: most well-run small businesses are better placed than they think. You don't need a data science team, a big budget or a grand strategy to get real value from AI. You need a sensible starting point, a few everyday tasks, and some simple guardrails.
This article sets out a practical way to begin.
The most useful question isn't "what can AI do?" It's "where does our time go on work that doesn't need our full attention?"
Every business has tasks like this. They're necessary, but repetitive, fiddly or slow:
These are exactly the areas where today's AI assistants tend to be most helpful, and where the risks are easiest to manage, because a person is still reading and approving the result.
Spend ten minutes with a pen and paper, or better still ask two or three colleagues, and list the tasks that feel like friction. That list is your starting point.
Before buying anything new, it's worth checking what's already within reach. Many businesses already have access to AI features through software they pay for:
Features and plans change frequently, so check the current details with each provider. What matters here is the principle: start with what fits naturally into the way you already work. An AI tool that sits inside the software your team uses every day is far more likely to be used than one that needs a new login and a new habit.
Rather than rolling something out to everyone, pick two or three people and two or three tasks from your friction list. Give it a few weeks.
A good first experiment has three qualities:
Ask the people involved to keep a few informal notes: what worked, what didn't, and roughly how much time it saved. You're not after precise measurement at this stage, just an honest sense of whether it's worth continuing.
A little structure helps people feel confident. It doesn't need to be a long document. For most small businesses, a handful of clear points is enough:
We'll cover how to write a short, positive AI use policy in a future article. For now, even an email to the team setting out these points is a good step.
After a few weeks, sit down with the people involved and ask:
The answers will tell you where to go next. That might mean extending the same approach to more people, trying a new set of tasks, or investing in a more capable tool. And sometimes it means deciding that a particular use isn't worth it yet, which is a perfectly good outcome.
Plenty of businesses make a good start on their own. It can be worth bringing in outside help when:
If you do one thing this week, make it this: write down five tasks that take up time without needing much judgement, and ask one colleague to do the same. Compare the lists. The overlap is where AI is most likely to help first.
From there, you can choose one or two to try with the tools you already have, and you'll have taken your first practical step, at your own pace.
If you'd like a hand working out where AI could help most in your business, our AI Adoption service starts with exactly that conversation.

How to spot re-keying in your business, the small automations that stop it, and how to keep them documented, owned and easy to live with.
· 6 min read
How AI can answer questions from your own documents using RAG, explained without jargon: how it works, where it helps, its limits and a sensible first step.
· 6 min read
Why a short, positive AI use policy helps your team use AI with confidence, what it should cover under UK GDPR, and a one-page outline you can adapt.
· 6 min read