Custom AI Systems for the work beyond tax.
C-Suite Individual and C-Suite Commercial run your tax work. Custom AI Systems cover the workflows that sit outside both, scoped and quantified in the proposal before you commit.
Custom AI Systems sits alongside the two tax engines. See how it works for where it fits in the spine, and the guides on AI for matter intake at South African law firms and the big-company AI pattern for South African SMEs for the kind of work a bespoke build carries.
Three shapes most Custom AI Systems engagements take.
A multi-branch intake-and-routing surface, a vertical-specific workflow nobody else has built, an integration combination the off-the-shelf middleware cannot hold. In discovery, C-Suite scopes every engagement against how your business actually runs, and most fall into one of three patterns the C-Suite engineering team has shipped before.
A multi-branch operation needs a single intake surface that captures every prospect or client message across web chat, WhatsApp Business, and email, routes by capacity and language, escalates against partner-defined rules per branch, and reports the volume back to head office on a cadence the principal partner can read in two minutes. The bespoke build covers the routing logic, the per-branch escalation rules, the integration into whichever practice management or CRM tool your branches already use, and the operator who keeps the rules calibrated as the operation grows.
Your operation runs a workflow that sits outside both tax engines, in a field where this shape of operational problem has been solved before. The bespoke build covers the field-specific rules, the regulatory framing, the document templates, the integrations into the tools your team already works in, and the senior South African operator who runs the engagement against a 90-day outcome window.
A workflow depends on a tool combination nobody else has built a clean integration for, where the off-the-shelf middleware breaks at the part of the work that needs judgement instead of routing, and the cost of building it correctly the first time is lower than the cost of running on a brittle workaround for the next three years. The bespoke build covers the integration architecture, test cases that catch failures before they reach your team, and a senior South African operator who calibrates it until it is stable.
From discovery to live operation, the build phase plus the 90-day outcome window.
Custom AI Systems run on the same operating logic as the two tax engines, with a longer build phase scoped to the integration shape and a 90-day outcome window from first day of live operation. The phases below are the normal shape of an engagement, with the actual cadence anchored to your firm’s sign-off rhythm.
Ninety minutes on Google Meet that document how the workflow runs in your business today, name the integration boundaries, and set the outcome the engagement is accountable to. The result is a one-page brief signed by you, plus an early read on the integration work your firm’s setup involves.
Engineering work set against the integration architecture agreed in discovery, with weekly progress notes sent to the partner who signed the brief. The build phase covers the routing logic, the integrations, the test cases that catch failures before they reach your team, and the senior operator briefed on how your firm runs. Build time depends on the integration depth of the workflow, so there is no fixed published timeline.
The 90-day window opens on the first day of live operation, with the outcome the build is accountable to locked in writing in the brief signed at the end of discovery. If the engagement has not hit the agreed outcome by day 90, we keep working at no further cost until it does. A Custom AI System carries a longer outcome window than the two tax engines because the integration depth deserves the time.
After the build phase ships, a monthly retainer covers the ongoing calibration, the test maintenance, and the senior South African operator who keeps the routing rules current as the operation grows. It runs on the same 30-day notice exit terms that govern every C-Suite engagement.
The two tax engines against Custom AI Systems, side by side.
The discovery call covers both options before you sign anything. Final terms are set before contract signature.
| Factor | The two tax engines | Custom AI Systems |
|---|---|---|
| What it covers | Filing season and the company-tax calendar: the document chase, the intake, and exception flagging, run on your existing software. | A workflow that sits outside both tax engines and needs a scoped build. |
| Outcome window | 60 days from first day of live operation. | 90 days from first day of live operation. |
| Pricing shape | A monthly retainer, set against the volume your firm runs and the integration overlap in your business. | A build phase plus a monthly retainer, set against the integration work and how your business runs. |
| Time to live operation | Discovery, integration, shadowing, live operation. Live begins when both sides sign off it is ready. | Build phase scoped to the integration depth, then the same discovery to live-operation rhythm. |
| Who runs it | A senior South African operator on retainer running the close on your stack, with your staff approving every output. | The C-Suite engineering team for the build, plus the same senior South African operator on retainer for the run-rate work. |
POPIA-aligned by default.
Client data and integration credentials stay in infrastructure hosted in South Africa. The senior operator (and the build team during the build phase) operates as a delegated user inside accounts you already own, with the right to revoke access at any time. Processing is logged per workflow, deletion on request inside seven days, audit log exportable on demand. You see the DPA up front.
Why is a Custom AI System worth trusting with the work?
A bespoke build sits closer to the heart of your firm than the two tax engines, so the reasons it earns that place have to hold up. Here is what stands behind one.
The build is run by senior engineers who have shipped this shape of work before, in operations larger and more complex than yours. The hard calls get made correctly the first time, and the judgement that decides what NOT to build saves you the six weeks a junior team wastes on a feature that never earns its place.
The build plugs into the practice management, ledger, and document tools your firm already lives in: Xero, Sage, Pastel, GreatSoft, CaseWare, SARS eFiling, and the mailbox the work already flows through. No rip-and-replace, no new system for your staff to learn. We work inside the accounts you already own, including the South African regulatory edges and the integration overlap that off-the-shelf tools never account for.
The system reads from your tools and never posts to your ledger. Every output waits for one of your people to approve it before anything moves. You stay in control of the work, and nothing reaches a client or a return without a partner signing it off.
Before any output reaches your team, it runs through a set of tests built for the ways your workflow can go wrong. The build is checked against the cases that break it, so errors surface in our environment instead of on your staff during a busy close.
The outcome the build is accountable to gets named and quantified in the proposal before you commit to anything. You know what you are buying and what it has to deliver, in writing, before a contract is signed.
The result is a workflow your firm could not run with its existing team, delivered as bespoke engineering plus a senior operator on retainer, with the engineering team keeping the integrations stable as the work grows.
Four questions firm owners ask about Custom AI Systems.
What is a Custom AI System?
A Custom AI System is a bespoke AI build for a workflow that sits outside C-Suite Individual and C-Suite Commercial: multi-branch intake and routing, a vertical-specific workflow, or an integration nobody has built cleanly before. C-Suite scopes the build in discovery, names the outcome it is accountable to in the proposal, and runs it after launch as managed AI, with a senior South African operator on retainer and your staff signing off every output.
Does a Custom AI System work with the software the firm already runs?
Yes. The build plugs into the tools the workflow already touches, whether that is Xero, Sage, Pastel, GreatSoft, CaseWare, SARS eFiling, a practice management system, or the firm mailbox, through read-only access you grant and can revoke at any time. Nothing posts to a ledger and no output reaches a client until a person on your firm approves it.
How is a Custom AI System different from the two tax engines?
The two tax engines are productised: they run filing season and the company-tax calendar on your existing software with a 60-day outcome window. A Custom AI System is scoped from scratch for a workflow outside that spine, carries a build phase before live operation, and runs a 90-day outcome window because the integration depth deserves the time.
Who runs the system after it ships?
The C-Suite engineering team keeps the integrations stable, and a senior South African operator runs the day-to-day on retainer, calibrating the routing rules and the test cases as the operation grows. Your firm keeps sign-off: every output waits for a named person on your team, and the engagement runs on the same 30-day notice exit terms as every C-Suite engagement.