Custom AI Systems for the work beyond tax.

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.

Fifteen minutes on Google Meet that map how the workflow runs in your business today and name 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 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 is scoped around the practice management, ledger, and document tools your firm already lives in, which for most practices means Xero, Sage, Pastel, GreatSoft, CaseWare, and the mailbox the work already flows through. No rip-and-replace, no new system for your staff to learn. Any connection deeper than the watched folder and mailbox the two tax engines already work from gets scoped, priced, and agreed in the proposal before it is built, 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, and every output waits for one of your people to approve it before anything moves, so nothing reaches a client or a return without a partner having looked at it.

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.