Automation & Integrations
Automate the repetitive work. Keep people on the decisions that matter.
Practical AI automation and integrations for businesses in Johannesburg and across South Africa. We map how enquiries and information actually move through your business, connect the systems you already use, then automate the steps that are predictable enough to be automated safely — and leave the rest alone.
Tell us which process is costing you time. If it starts with enquiries arriving through your website, a free Website Review covers that journey too.
One enquiry, six steps, one human decision
- Enquiry arrivesWebsite · WhatsApp
- Details capturedStructured form
- Request sortedRules · AI
- Sent to the right personEmail · CRM
- Follow-up scheduledEmail · WhatsApp
- A person takes overHuman decision
What it actually means
Business automation is mostly plumbing, not intelligence
Most of the value comes from connecting things that are currently connected by a person: a form that writes to the CRM, an enquiry that reaches the right inbox, a reminder that fires without anyone remembering.
AI earns a place in a narrow set of steps — sorting messages, pulling structured detail out of unstructured text, drafting from material you have approved. It is one component in a workflow, not the workflow.
Where the process needs a system that interprets context and chooses its next action rather than following the same steps every time, that is an AI agent — and we will tell you plainly which one your process actually needs.
Where the time goes
The work that repeats every week
Automation candidates cluster in three places. Recognising your own business in one of these columns is more useful than a list of technologies.
Enquiries coming in
Typically the website, WhatsApp and the shared inbox.
- Acknowledging an enquiry so nobody waits in silence
- Collecting the same details by hand, every time
- Routing requests to the right person or branch
- Answering the questions asked the same way every week
- Sorting genuine enquiries from noise
Following up
Typically whoever remembers, in whatever they use to remember.
- Qualifying leads against a consistent set of questions
- Reminders after a quote goes out with no reply
- Booking and appointment confirmations
- Status updates a customer would otherwise phone for
- Handing a qualified lead over to the CRM cleanly
Internal admin
Typically spreadsheets, email and copy-paste between systems.
- Retyping the same information into a second system
- Creating tasks from something that happened elsewhere
- Routing documents and data to where they belong
- Notifying the team when a record changes
- Pulling recurring reports together by hand
Most projects start with one item from one column. Automating a single process properly beats automating five badly, and it tells you quickly whether the approach is worth extending. The Fullstop Bars case study shows where that starts on a service business: enquiries arriving by WhatsApp, form and email at once.
Suitability
Not every process should be automated
Some processes are ready. Some are not yet. Some should stay with a person permanently. Working out which is the first hour of any project, and it is the hour that saves the money.
Leave it with a person when
- The process changes shape every time it runs
- The step needs judgement, negotiation or a relationship
- Being wrong carries legal, financial or safety consequences
- The volume is too low to justify maintaining it
- Nobody will own the workflow once it is live
Worth automating when
- The steps run the same way most of the time
- The information arrives in a predictable shape
- The rules can be written down and agreed upfront
- It happens often enough that the time saved is real
- Someone in the business will own and review it
Automating a confused process gives you a faster confused process. Where a process is not yet consistent enough, fixing the process comes first — even where that means there is less to build.
How it runs
Map first, build last
The first two phases often conclude that less should be built than expected. That is a successful outcome, not a failed one.
-
Map
Walk the process as it runs today, including the undocumented parts and the workarounds people have quietly invented.
-
Assess
Test it against the suitability criteria above. Decide what to automate, what to fix manually first, and what to leave.
-
Prototype
Build the smallest version that proves the workflow, on real cases, before anything is connected to a live system.
-
Connect
Wire it into the actual tools with the minimum access needed, and define what requires a human approval.
-
Test
Run the normal path, then deliberately break it: bad input, missing fields, a service that is down, an unexpected request.
-
Monitor
Document it, hand over ownership, and watch the first period of live running. Automation that nobody watches drifts.
Limits and dependencies
A person stays accountable for the outcome
Every workflow is built with explicit boundaries: what it may read, what it may do on its own, and the point at which it must stop and ask.
Built in by default
- A defined escalation route to a person
- Minimum necessary access to data and systems
- Exception and failure handling, not just the happy path
- Logging, so you can see what it did and why
- Transparency where a customer is interacting with automation
Depends on your setup
- Whether the platforms involved expose a supported connection
- Your WhatsApp account type and provider
- The quality and consistency of your existing data
- Who can grant access, and how quickly
- Who will own the workflow after handover
Not on offer
- A guarantee of leads, sales or a specific time saving
- Removing the need for the people doing the work
- Legal, medical or financial advice generated automatically
- Compliance sign-off — that stays with you and your advisers
- Automation of a decision that should not be automated
Personal information handling, data residency and POPIA obligations are agreed in the scope before anything is connected. Responsible design reduces risk; it does not transfer your regulatory responsibility to us.
Scope, price and timing
What an automation project costs depends on
Unlike a website, part of the cost here is ongoing rather than once-off, and some of it is paid to third parties rather than to us. That is worth understanding before you commit.
Build
- How many workflows, and how many steps in each
- Number of systems that have to talk to each other
- How much of the process must be fixed before automating
Access and data
- Condition of the data being moved or matched
- Account types and permissions on third-party platforms
- Privacy and security requirements you need met
Running it
- Third-party subscriptions, billed to you directly
- Usage fees that scale with volume, including AI usage
- Monitoring and maintenance after handover
Automation work is normally scoped as a Website and Automation project, or under Custom Apps & Business Systems where the workflows are more involved. Published starting points are under project packages. Every project receives a written scope and price before work begins, with third-party costs identified separately.
Where to start
If the repetition starts at an enquiry, start with the review
Most automation requests we receive begin at the same point: something arrives through the website or WhatsApp and a person has to do six things with it. The review covers that journey — how enquiries arrive, what happens to them and where they stall.
If the process you want to automate has nothing to do with the website, skip it and describe the process instead. That is the faster route.
Free Website Review
Free, with no obligation, and normally back within two business days.
If the workflow needs interpretation, not just rules
AI AgentsIf the enquiries are thin because the website itself is losing people
Website RedesignQuestions about automating a business process
Which process should we automate first?
The one that repeats most often, runs the same way most times, and currently depends on somebody remembering. That combination gives the clearest return and the lowest risk. It is rarely the most impressive-sounding candidate.
Can this connect to WhatsApp?
Often, through WhatsApp-compatible providers — but not always, and not for every account type. What is possible depends on the provider and the kind of WhatsApp account the business holds, so this is confirmed during scoping rather than assumed. Anyone promising WhatsApp automation before checking your account type is guessing.
What happens when it breaks?
It will, eventually — a service goes down, an account expires, someone sends something unexpected. The workflow recognises what it cannot handle, stops, and puts it in front of a person. Silent failure is the real risk with automation, not visible failure.
Does our company information go into an AI service?
Only where a step genuinely needs it, and only material you have approved. Which data is involved and how the provider handles it is set out before anything is connected. Many workflows use no AI service at all.
Will this let us reduce staff?
That is not what we sell and not what we would claim. Automation removes repetitive steps from work people are already doing. Whether that changes anything about your team is a business decision that belongs to you, not an outcome we guarantee.
Next step
Start with one process that keeps costing you time
Tell us where enquiries stall, what gets retyped, or which follow-up depends on somebody remembering. We will tell you whether automation is the right answer.
Is the stall happening on enquiries from your website? A free Website Review covers that journey.
Or email lance@wedevelop.co.za