Workflow automation
Do you need an AI consultant or an AI automation agency?
The two labels overlap. Good agencies do some consulting before they build, and some consultants build. What separates them is what you pay for and what you're left holding at the end.
This post covers what each one hands over, how each tends to charge, which a small business in South Africa usually needs first, and the warning signs on both sides. We're an AI automation agency in South Africa ourselves, so we'll flag where that colours the advice.
What does an AI consultant give you?
Mostly decisions and documents. A consultant looks at where your team's time goes, picks out the jobs AI could take over, and recommends what to do first and with which tools. Expect an assessment, a ranked list of uses, a business case and a shortlist of products or suppliers, sometimes with a staff policy on using AI tools.
What you don't usually get is a working system. Someone still has to build what the consultant recommends: your own developers, an agency, or you, inside a product you subscribe to.
A consultant earns the fee in two cases. One is when you can't yet say where AI would help. The other is when you want a second opinion from someone with no build to sell you, say on an agency's proposal. If you have developers of your own, that may be all you need: the plan from a consultant, the build in-house.
What does an AI automation agency deliver?
A working system connected to your tools, and someone to keep it working. That might be an AI receptionist that answers your line and books into your diary, a WhatsApp chatbot on the WhatsApp Business Platform, or workflow automation that takes quoting and invoicing off someone's evenings.
A good agency scopes the job before building, and that scoping is a narrow piece of consulting. It settles what the system will do, what it connects to, when it hands over to a person and how you'll know it works. The difference is that the advice covers one build the agency then has to make work, not your whole business.
Builders also know the problems that only show up once a system is live. A launch can wait on access to a CRM someone else administers, and customers ask questions nobody wrote an answer for.
| AI consultant | AI automation agency | |
|---|---|---|
| What you get | A plan: priorities, a business case, tool choices | A working system in your channels and tools |
| Who builds it | Your developers, another supplier or you | The agency |
| Who runs it afterwards | Usually not the consultant | Usually the agency, under a support arrangement |
| Usual charging | Hourly or daily rates, a fixed fee, or a retainer | A build fee plus a monthly fee, or one monthly fee, with platform usage on top |
| Best when | You can't yet say where AI fits | You can name the job and want it done |
How do AI consultants and agencies usually charge?
Consultants usually sell time or a defined piece of work: hourly or daily rates, a fixed fee for an assessment or roadmap, or a monthly retainer. The fee buys thinking, so judge it by the decisions you'll be able to make afterwards that you can't make now.
Agencies charge for building the system and for running it. Some split that into a once-off build fee and a monthly fee for hosting, support and changes; others fold everything into one monthly figure. On top of either, the platforms bill their own usage, such as AI model usage, voice minutes and WhatsApp messages. That part rises with volume, and some of it is billed in US dollars, so its rand cost drifts with the exchange rate.
Before you sign with either, get answers in writing. Which parts of the price are fixed, and which grow with use? What will changes cost after launch? What do you keep if you stop paying?
Should a small business hire an AI consultant or an AI automation agency first?
Usually an agency, for one narrow build that's scoped properly, rather than a consultant's strategy. That's a builder's answer, so weigh the reasoning for yourself. Most small businesses don't have a long list of AI projects competing for attention. They have one job that eats hours or loses customers, and handing that job over teaches you more than any plan.
A quick test tells you whether you're ready for a builder. Can you name the job, say roughly how often it happens and list the systems it touches? "We miss calls in the late afternoon while we're on site, and those callers should be booked into the diary" passes. If yours is a phone job like that one, the questions in choosing an AI voice agent are the ones to put to each provider.
Say you run a conveyancing practice in Cape Town, and buyers fill the inbox asking how their transfer is going. You can describe that job, so it's a builder's job.
Start with a consultant instead if you can't name the job, if different parts of the business want different things, or if your own developers will do the building.
Look at your customer data first, too. If your customer records are split between a spreadsheet, a few cellphones and someone's memory, AI has nothing reliable to read from or write to. Our post on when a spreadsheet stops being enough helps you judge whether that's your real first step.
Can the firm that builds it also give you honest advice?
Yes, as long as you know where its incentive sits. An agency is paid to build, so the risk is a plan that always ends in a build, or in a bigger one than you need. A consultant carries the opposite risk. They're paid for the plan, not for making it work, so a roadmap can promise more than your systems or budget can carry.
The same questions test both. What would they advise you not to automate, and why? Will they work with the tools you already pay for? Is the scope in writing before you pay anything? How will success be measured, and by whom? Then set their answers beside the timelines and payback ranges in how long AI automation takes to set up.
What red flags should you watch for?
Most warning signs apply on both sides. Stop and ask more questions if you see any of these:
- A savings figure or a payback date offered before anyone has seen your call log, your inbox or your diary.
- A strategy document with no named first project, no owner and no date.
- Tool recommendations from someone who earns a commission on them and doesn't say so.
- No way to pass a customer to a person when the AI is out of its depth.
- Accounts in the supplier's name. Your WhatsApp Business account, phone numbers, AI platform accounts and CRM should belong to your business, with the supplier given access.
- No written agreement about your customers' personal information.
- An AI that makes decisions about people with nobody checking them.
The last two are POPIA questions, and the first applies to a consultant as much as to a builder. Send a consultant your customer records to analyse and they're handling personal information for you, just as an agency hosting your chatbot is.
In the Protection of Personal Information Act, a supplier like that is an operator, and under section 21 you need a written contract that binds it to keep the information secure. Ask to see that agreement before you hand anything over. Section 71 restricts, with exceptions, decisions that have legal consequences for a person or affect them to a substantial degree, where the decision rests solely on automated processing that profiles them. Our POPIA guide covers both sections in more depth, and none of this is legal advice.
Is Cognexa a consultant or an agency?
Cognexa is an AI automation agency based in Centurion, Gauteng, so read this with our side of the line in mind. We build AI receptionists and voice agents, WhatsApp and website chatbots, workflow automation for quoting, invoicing, bookings and inbox triage, and custom CRMs.
Every project starts with a scoping conversation about what's eating your team's hours, and you get a written plan. That conversation is the first of the five stages of how we build, set out on our homepage. We scope the work before naming the technology, because what a system is allowed to do matters far more than what it's called.
Our usual order is a chatbot on your website and WhatsApp that catches and qualifies enquiries first, then workflow automation behind it once we can see which admin is taking up the time. We'd advise you not to automate low-volume work, work that needs a person's judgement or empathy every time, or a process that changes so often the build would need redoing before it paid for itself. That's our answer to the first test question above.
How do you brief an AI consultant or an agency?
One page, the same for everyone you talk to:
- The job you'd hand over first, in one sentence.
- How often it happens in a normal week, from your own records.
- The systems it touches, such as your calendar, CRM or spreadsheet, accounting package, phone line and WhatsApp number.
- Who in the business owns each of those accounts and logins.
- What working would look like a few months from now.
Send it before the first meeting. A consultant should come back with questions about the business, and a builder with questions about your systems. Anyone who comes back with a price and no questions has told you what you need to know.