Skip to content
GrowthCred · South Africa

AI automation built around your business.

You've got work that repeats every week. Proposals. Quotes. Follow-ups. The same questions from your team. I find that work and build AI workflows around it. It starts with one conversation about your process, your tools and the result you need.

By Phila Ngwenya · Reviewed

Start with one workflow

Don't try to automate the whole business. Pick one thing. Proposal drafts. Quote prep. Follow-ups. Recurring research. That's where I start.

I look at the real workflow before I promise an integration. Why? Because if the records are incomplete, or every case needs judgement, you need a process fix first. Automating a mess just gives you a faster mess.

We also agree what to measure before we build. Otherwise, how would you know it worked?

How the engagement works

It's four steps. First, discovery. We write down the current process, the volume and what hurts.

Second, scope. We agree what gets built, what it connects to, how we'll test it and what's left out.

Third, build and test. We run it against real examples with your team. Not a demo. Your actual work.

Fourth, handover. You get the documentation, the access and a clear answer to who maintains what. No mystery box.

Results clients have reported

TaiAscend reported that a document process that took three days now takes two hours.

Sandile runs MNE Waste. Trucks, drivers, compliance, municipal contracts. He built his Operator's Brain in one day and is now fully operational. If AI can handle that, it can handle what you do.

What will it cost?

There's no single price. Honestly. It depends on the workflow, how ready your data is, what it connects to, the exceptions and the support. We quote after we've seen your brief.

And the R990 workshop? That's training. It's not the price of a custom build.

Ask for setup costs, running costs and third-party subscriptions separately. And agree how changes get handled. Otherwise a small first project grows without anyone deciding it should.

Your systems and your information

Tell us which tools you use now. Whether they connect depends on their APIs, your account permissions and the workflow. Naming a tool isn't a promise that a connector exists. We check.

Keep confidential customer data out of your first message. During scoping we agree data access, retention, review and who approves anything that goes out. And no, installing an AI tool doesn't make you compliant with any law. Nobody can sell you that.

Training or implementation?

Want to build it and understand it yourself? Take the workshop. Does the work cross systems, need testing and maintenance, or need a team to deliver it? Talk to us about implementation.

Either way, start with one real task. Not a promise to automate everything.

Frequently asked questions

What does AI automation cost in South Africa?
There's no single price. It depends on the workflow, your data, the systems it connects to, the exceptions and the support. We quote after we've reviewed your brief. The R990 workshop is training, not the price of a custom build.
Which workflows should we automate first?
Start with proposal drafts, quote prep, follow-up drafts or recurring research. We look at the real workflow before we promise any integration.
Will it connect to the tools we already use?
That depends on each tool's APIs, your account permissions and the workflow. Naming a tool isn't a promise of a connector, so we check before we scope.