The WhatsApp messages are almost always the same sentence. Someone knows they should be using AI, and they can't picture the first hour of it inside their own office. Tool lists don't help with that. They assume you've already decided which job to hand over.
If you run a firm of somewhere between five and thirty people, integrating AI is a small sequence. You hand one repetitive job to a system, you watch it for two weeks, and then you decide whether a second job is worth the bother. That's the method. The rest of this is how to pick the job so you don't lose a month.
Write down the work before you open a new tab
For five working days, keep a note on your phone. Every time you or someone on the team does something you've done before, write the task, roughly how long it took, and who was waiting on it. Don't tidy it. A messy note is the point.
At the end of the week, sort the pile into buckets:
- Only a person who knows the client can do this
- A junior could do it if the steps were written down
- It's the same steps every time, and the inputs already live in email, a spreadsheet, or the accounting file
- It happens once a quarter and isn't worth touching
The third bucket is where this pays. Quote follow-ups. Appointment reminders. The "we've received your documents" email. Pulling last month's numbers into a one-page note. Chasing a supplier who hasn't replied. None of that needs a strategy offsite.
If you can't name the job in one sentence, you don't have a project yet. "Use AI in the business" is a mood. "Send the second quote follow-up on day three" is a job.
Which jobs to hand over first
I keep coming back to the same short list, because the inputs already exist and a person forgetting is the actual failure.
| Job | Why it tends to work | Leave it alone if |
|---|---|---|
| Reply to a new enquiry within a few minutes | The person who answers first usually gets the conversation | Your offer changes every week and nobody can describe it plainly |
| Follow up a quote that went quiet | The wording is stable. The timing is the part humans drop | The quote needs a site visit before anyone can say yes |
| A Monday note on what came in last week | The numbers already sit in tools you pay for | You don't trust the source data |
| Chase missing documents | The email is polite, specific, and boring | The relationship is already tense and tone matters more than speed |
Pick one row. If you pick four, you'll finish none of them and decide AI "doesn't work here."
Connect it to the software you already pay for
A chat window on its own is a bright intern with no key to the filing cabinet. Fine for a draft. Useless as part of the working day. The follow-up only counts if it can see the quote, the calendar, or the inbox.
Say you run a four-person accounting practice in Bellville. Clients email source documents to a shared inbox. Someone checks it twice a day, files what they recognise, and sends a "still waiting on the VAT schedule" note when they remember. The integration is small. A new email lands. The system checks it against the list of documents you expected. It files the obvious ones. It drafts the chase for a person to send. For the first fortnight, a person still hits send. If the drafts have been right, the routine ones can go out on their own.
That is what integrating AI looks like. It is a subscription only in the sense that the model has a monthly bill. The work is the connection.
Use what you already pay for. Email. A spreadsheet. Xero, Sage, or whatever is actually open on the bookkeeper's screen. WhatsApp, if that's where clients already talk to you, and only where they've agreed to hear from you there. POPIA still applies when the sender is a model. Don't paste a client list into a chatbot you found at 11pm. Keep the data in accounts the business controls.
Run it with a person checking the output
Write the before number down first. How many quotes got a second follow-up last month? How many hours did the Monday report take? How long did a new web enquiry sit? If you don't have the number, week three turns into a debate about vibes.
Keep the scope mean.
- After-hours web enquiries only
- Invoices more than 14 days late
- Document chases for VAT clients, not the file that's already in dispute
Name one person who reads the output every morning. If a draft is wrong, fix the instruction. Two weeks will tell you whether the job is real. Clumsy drafts mean the instruction was vague. Drafts that are fine, and a before number that moved, mean you do the second job the same way.
What I would leave alone for now
Judgment stays with you. Pricing a weird job. Telling a long-standing client their payment is a problem. Hiring. Anything that depends on a conversation you had in the car park last Thursday. A model doesn't have that afternoon.
Leave the brand voice alone too, if the way you sound is why people hire you. A first draft of an internal email is fair game. A homepage that could belong to any firm in your industry is how you start sounding like a template.
Skip the pile of new apps. One paid chat subscription is a few hundred rand a month. The cost that hurts is the week you lose connecting five tools you don't need yet. Once one job is actually running, the longer map is an AI operating system: memory, data, and the repeat work in one place. The services page is the menu if you'd rather not wire the first job yourself. The discovery call is thirty minutes on one workflow, not a free build.
The first job changes with the work. A law firm has a confidentiality line. An estate agency owes sellers a weekly note. Advisors can't let a model invent product talk. An online store is usually drowning in "where is my order?" Don't copy one generic follow-up into all four.
If you want the plainer background first, there's a plain-English guide to AI in business and a separate note on what is actually working for small businesses.
Questions people ask
Do I need a developer to integrate AI?
Not for the first job. If the tools you already use can pass information between them, a careful person can wire a simple follow-up. You want someone who does this every week when the steps cross three systems, or when a message goes to a client with no one checking it.
How much does it cost to start?
The software is the cheap part. A paid chat subscription is a few hundred rand a month. A first automation, scoped so it doesn't fall over in week two, sits in the range of a few thousand rand. That figure only means anything after someone has looked at the actual job.
What if my team refuses to use it?
Then the job you picked isn't one they feel. Start with the task people already complain about. Don't announce a new era in a staff meeting before a single workflow works. Show them the Monday note arriving on its own.
Is this the same as buying ChatGPT for the office?
A shared login is a writing aid. Integration means the output lands in the inbox, the job file, or the client's phone, on a schedule, with rules. If someone still copies the answer into another window, you haven't integrated anything.