X-AI builds sovereign workflow software for International and South African financial advice, insurance, finance, operations, and creative teams. Sensitive records stay inside your approved boundary, every drafted line cites its exact source, and a person signs off before anything is sent or posted.
How it works · Interactive architecture
Click any node or step the live circuit to inspect how recordings, contracts, and spreadsheets move from sealed local hardware to human-verified sign-off.
Agreed recordings, claims, contracts, and spreadsheets are processed inside your private environment—capable of operating offline with zero public-cloud model training or per-token cloud bills on local steps.
Instead of black-box chat summaries, X-AI generates structured working files where every figure, exception, or promise links back to the exact timestamp, clause, or attachment.
Nothing auto-emails a client, approves cover, or posts an invoice. Missing signatures or unconfirmed stock trigger a hold—and if new evidence arrives, prior sign-off resets automatically.
Cloud AI risk vs. Local X-AI · 10 business scenarios
Compare ten international and South African operating scenarios—from runaway seat subscriptions and payroll privacy exposure to underground manuals and factory quality gates. Jump to any topic, trigger an animated sweep, drag the luminous split curtain, or expand to full screen.
At US$200 per employee per month, 10,000 paid seats cost US$2,000,000 per month and US$24,000,000 per year.
Teams share locally operated AI capacity.
Business risk: At US$200 per employee per month, 10,000 paid seats cost US$2,000,000 per month and US$24,000,000 per year. (Open risk image)
Local X-AI response: Teams share locally operated AI capacity. (Open Local X-AI image)
Business risk: Uploading payroll records to an external AI service can put personal information at risk. A qualifying POPIA infringement can lead to an administrative fine of up to R10 million. (Open risk image)
Local X-AI response: The payroll team processes sensitive records on company infrastructure. (Open Local X-AI image)
Business risk: Loss of regional access interrupts a cloud-dependent dispatch workflow. (Open risk image)
Local X-AI response: A locally operated dispatch system keeps orders moving. (Open Local X-AI image)
Business risk: Sensitive bid information leaves the company’s controlled environment. (Open risk image)
Local X-AI response: The bid team works with confidential tender material on its own systems. (Open Local X-AI image)
Business risk: A provider limit leaves invoices waiting at month end. (Open risk image)
Local X-AI response: A local invoice-processing workflow handles the next invoice. (Open Local X-AI image)
Business risk: An upstream model change disrupts a validated workflow. (Open risk image)
Local X-AI response: The team controls when its locally deployed model changes. (Open Local X-AI image)
Business risk: At illustrative rates of R18 and R20 per US dollar, a US$2,000,000 monthly bill costs R36 million and R40 million respectively, a difference of R4 million per month. (Open risk image)
Local X-AI response: The business can plan and compare the rand cost of operating local capacity. (Open Local X-AI image)
Business risk: A technician underground needs a maintenance manual that is unavailable offline. (Open risk image)
Local X-AI response: The local manual search finds the pump seal on page 42. (Open Local X-AI image)
Business risk: Critical engineering knowledge is missing at handover. (Open risk image)
Local X-AI response: The incoming team can retrieve engineering knowledge locally. (Open Local X-AI image)
Business risk: A cracked cap slips through inspection. (Open risk image)
Local X-AI response: Local inspection detects the cracked cap and diverts the defective bottle. (Open Local X-AI image)
AI investment canvas · Cloud per-token bleed vs. Local X-AI asset
Cloud AI starts small—$10 on Day 1, another $10 on Day 2, another $10 on Day 3—then compounds across months and years through prompt growth, vendor price hikes, and USD/Rand exchange movements without ever building an asset. Compare that side by side with a one-off R250 000.00 Local X-AI deployment whose upfront cost dilutes away onto level ZAR electricity and maintenance.
Every prompt, long PDF context window, team seat, and agent retry triggers a new US Dollar charge. When usage grows, vendors reprice tiers, or the Rand weakens, your monthly operating bill climbs permanently.
Deploy dedicated local AI hardware and X-AI workflows upfront (e.g. R250 000.00). As months turn into years, that original outlay dilutes smaller and smaller while electricity and maintenance stay level.
Interactive Live Example: Transcribe Studio
Press play on this full two-way Q&A recording: adviser Daniel Mercer questions COO Claire Vance across Meridian’s Rotterdam, London, and Johannesburg/Durban cold-chain lanes. Scrub the live waveform, follow the diarized transcript, inspect the $480,000 → $310,000 live claim correction, and test what changes when an underwriter credit letter arrives after the call.
Morning Claire. Thanks for carving out fifteen minutes between the Rotterdam handover and your Johannesburg ops call. Is my audio coming through clearly on your end?
Loud and clear, Daniel, thanks. I have my door shut and the surveyor files open on my second screen, so we have a clean fifteen minutes before my quarter-past check-in.
Before we open October's underwriter pack or touch any numbers, what single outcome would make these fifteen minutes genuinely useful for your Friday steering committee?
If I walk into Friday knowing exactly what cash is genuinely committed between now and thirty-one March—and without anyone mixing unverified insurance estimates into our working reserve—I can defend the Q1 plan. Have you seen the compliance hold our Data Protection Officer issued on Tuesday?
I saw the one-line summary in the intake note, not the full directive. Right now our prior file still shows Meridian processing claims packs across Rotterdam, London, and Durban with manual spreadsheet sign-off. What triggered the compliance block?
Two of our regional managers tried piloting a browser-based cloud transcription and summarizing tool to clear the January backlog. Group Legal and our South African POPIA officer shut it down within forty-eight hours. Every cold-chain incident pack carries client cargo manifests, bilateral pricing clauses, and driver biometric logs from the Durban depot.
So external cloud model egress is completely off the table for operational and claims evidence across both jurisdictions?
Completely off the table. Nothing containing shipper pricing, loss-adjuster notes, or South African driver records may leave racks we control in Frankfurt or Johannesburg. Meanwhile, my commercial operations leads are still compiling over a hundred and forty incident and renewal files a month by hand.
And on the commercial side, our October record shows your old marine cargo policy renewing on fixed monthly declarations, with sixty-eight thousand dollars a month in predictable rebates landing at month-end. Is that rebate stream still active this quarter?
No, don't carry that sixty-eight thousand forward. December was the final fixed-rebate declaration under the old syndicate. From January we moved onto a quarterly performance-indexed corridor treaty. Finance won't know the Q1 rebate—or what they need to hold back for cold-chain deductibles—until April.
Got it. Do you have the signed January corridor schedule showing the new settlement window in writing yet?
I have the signed slip summary—I will send you the settlement-terms page with Tuesday's bundle—but please treat January through March rebate inflows as zero in our near-term cash bridge so we don't kid ourselves.
Understood—we will mark the sixty-eight thousand as historical through December only. Let's turn to the big item sitting in your October file: the Durban-to-Rotterdam pharmaceutical reefer incident. What is the current exposure figure on your desk?
That's the voyage seven-fourteen excursion. I have four hundred and eighty thousand dollars written at the top of my board pack. That was the gross spoilage figure the depot manager logged the night the vessel docked.
Our October intake exhibit E-zero-one also lists four hundred and eighty thousand dollars as an early provisional estimate. Did all six refrigerated containers actually fail secondary pulp-temperature testing, and do you have a signed loss-adjuster figure?
Wait a second—thank goodness you asked about the secondary pulp test. Let me pull up the marine surveyor's Tuesday addendum rather than quoting my handwritten cover note.
Take your time. Let's read directly off the surveyor's schedule so we record the exact status.
Here it is—page three of the Rotterdam lab annex. Sorry, Daniel, please cross out the four hundred and eighty thousand. Two of the six containers stayed inside the two-to-eight-degree stability envelope on internal data loggers and cleared QA release. Three hundred and ten thousand dollars is the revised gross claim estimate. We still don't have the insurer's signed adjustment certificate, and salvage credit plus policy excess aren't netted off yet.
Then here is how we will govern it in the file: we will preserve four hundred and eighty thousand in the audit trail so nobody wonders why the October board figure changed, record three hundred and ten thousand as your revised surveyor estimate, and keep zero dollars of it in confirmed available cash.
Yes, please. The last thing I want is our treasury sheet assuming three hundred and ten thousand lands in February when not a cent of it is confirmed cash.
With that claim held out of cash, let's look at hard near-term outflows. What actually has to be paid out of Meridian's operational reserve in February before Q1 customer settlements clear?
The immediate pressure point is our sovereign cold-chain telemetry and compliance rollout. Keep in mind everybody on the executive floor keeps repeating 'two hundred and eighty-five thousand in February' because the vendor master schedule says two hundred and eighty-five thousand dollars at the bottom. My procurement lead says I'm reading the milestones wrong.
Let's split the master contract total from the February invoice line right now. What does the milestone table state beside fifteen February, and what does it say about the balance?
Okay, reading line one: ninety-five thousand dollars is payable on fifteen February for Phase One hardware and corridor telemetry commissioning. The remaining one hundred and ninety thousand is split across Phase Two and Year Two tranches, and the deployment dates for those tranches aren't fixed yet.
And wasn't there an underwriter risk-engineering subsidy or rebate application tied to installing that exact Phase One telemetry?
We submitted the risk-mitigation rebate application to our lead syndicate two weeks ago—it would credit forty-five thousand dollars directly against the Phase One compliance invoice—but we have no award letter today. Please budget as if Meridian has to fund the full ninety-five thousand ourselves on fifteen February until a verified letter arrives.
Agreed—an application is never an asset. If you pay that ninety-five thousand on fifteen February without touching your revolving credit facility or selling fleet assets, what unencumbered cash reserve is actually sitting in the ring-fenced operations account today?
As of this morning's treasury flash, we have two hundred and forty thousand dollars accessible in our ring-fenced operational reserve. Before anyone calls the remainder 'free headroom', our Durban cold-store lease, reefers' generator fuel settlements, and customs bond renewals all hit that same account between mid-February and mid-March.
Let's check that arithmetic plainly: two hundred and forty thousand opening reserve minus ninety-five thousand on fifteen February leaves one hundred and forty-five thousand dollars before a single cold-store lease, fuel debit, or customs bond comes out. We cannot responsibly call that a surplus without the exact debit schedule. Can treasury pull the committed February-to-March debit list?
Yes. I will send you the bank reserve statement and the committed February-March operational debit schedule by Tuesday afternoon, along with the corridor treaty settlement-terms page. I will also chase the loss adjuster for the written voyage seven-fourteen status, though I cannot promise when they will reply.
Good—we will track Tuesday's internal items separately from third-party responses you don't control. Before we leave Q1 obligations, Exhibit E-zero-two in our prior file flags a shipper service-level agreement clause maturing at the end of March. Is that part of normal monthly rebates, or is it a standalone exposure?
Keep it completely separate from monthly operations. Under our anchor pharmaceutical shipper contract, there is a one hundred and sixty thousand dollar liquidated-damages cap falling due on thirty-one March following the cold-chain excursion. Exhibit E-zero-two in your file is accurate. We haven't decided whether to settle from cash, offset against Q2 freight credits, or apply insurer proceeds if they clear in time.
Understood—thirty-one March, one hundred and sixty thousand dollars, modelled as a standalone dated obligation.
Daniel, before we frame the two scenarios for Friday, can I flip the script and ask you two blunt questions as an operator? Because my CTO and our Johannesburg infrastructure lead are going to grill me on how X-AI actually processes a call and file pack like this.
Please—ask away. Better we stress-test the operating boundary right now.
First: when your Transcribe Studio turns a fifteen-minute review like ours plus prior exhibits into working notes and registers, if we deploy it inside our Frankfurt and Johannesburg server rooms, does anything phone home to an external cloud API for transcription, embeddings, or model weights?
Zero external runtime calls on agreed local workflow steps. The speech-to-text, source-linking, and structured draft generation run inside hardware or private enclaves under your own firewall—capable of running completely offline with air-gapped network interfaces and zero per-token cloud API bills on local processing.
And what stops the local model from doing what generic chat tools do—confidently blending my old four-hundred-and-eighty-thousand note into available cash, or auto-emailing a half-baked summary to our insurance broker?
Three hard engineering gates. First, every drafted figure or promise carries clickable source citations back to the exact call timestamp and exhibit ID. Second, unverified numbers—like your three-hundred-and-ten-thousand surveyor estimate—trigger an explicit hold status rather than entering cash arithmetic. Third, nothing auto-posts to your ERP or emails a counterparty; a named human reviewer signs off, and if a post-call document arrives later, prior sign-off automatically resets.
What about the real cost side? My CFO hates vendor fairy tales that pretend on-premise AI is free just because there's no per-token cloud invoice.
Your CFO is right. Local AI eliminates variable cloud token spend and third-party data exposure, which makes high-volume recurring reviews predictable—but you still budget explicitly for GPU server hardware, storage, power, software licensing, and the fifteen minutes of human reviewer time per file. That's why we scope one concrete workflow pilot first and measure real end-to-end reviewer minutes against your manual baseline.
That's refreshingly honest. That gives me a clean, defensible answer for both Group IT and Finance.
Now let's lock down your exact instruction on that thirty-one March one-hundred-and-sixty-thousand-dollar SLA obligation. Are you asking us to prepare a drawdown request on your credit facility, or compare the cash positions first?
Do not touch our revolving credit facility and do not draft any settlement offer to the shipper. Show me two clean illustrations side by side: Scenario A if net insurer proceeds clear before thirty-one March using a clearly labelled assumption, and Scenario B if zero insurance money arrives before April. I am asking for a comparison to take to counsel, not an execution instruction.
Let me also check one governance detail so our risk-register note doesn't misrepresent you: when you say this quarter is keeping you awake, is Meridian rethinking its long-term Durban cold-chain corridor strategy, or is the pressure strictly this sixty-day liquidity timing bridge?
It is strictly the sixty-day timing bridge between funding Phase One compliance on fifteen February and facing the thirty-one March SLA cap while our new treaty rebates haven't started landing. Demand on the Durban-to-Rotterdam pharma lane is strong; I just refuse to breach our operational reserve floor because someone confused gross claim estimates with bankable cash.
Crystal clear. I will record that concern verbatim under near-term liquidity timing and leave your strategic corridor risk appetite unchanged in the register.
One critical distribution rule, Daniel: send the Thursday comparison pack and recap email strictly to me and our General Counsel, Priya Nair—nobody else. Please do not copy our external insurance broker or the shipper account director. I want Legal and me aligned on the exact numbers before we put anything in front of external parties.
Noted as a hard recipient restriction: addressed to Claire Vance and General Counsel only, zero external CCs, held for human check before anything leaves the workspace. If your reserve statement, February-March debit list, and treaty payment-terms page arrive by Tuesday, I will have both comparisons drafted for Thursday morning—or if anything is missing, I will flag exactly what is missing rather than plug in a guess.
Thursday morning on that basis works perfectly. If the loss adjuster hasn't confirmed net salvage and payment timing by Tuesday, don't hold up the whole pack—just label Scenario A clearly as an unverified 'what-if'. And as soon as the vendor sends fixed dates for the remaining one-hundred-and-ninety-thousand Phase Two compliance tranches, I will forward them.
Let me read back the five guardrails I am taking away so you can correct me on the spot. First: no credit-facility drawdown, no shipper settlement instruction, and no broker contact. Second: fifteen February compliance is ninety-five thousand dollars, not the full two-hundred-and-eighty-five-thousand multi-year total. Third: thirty-one March holds a separate one-hundred-and-sixty-thousand SLA cap.
Spot on so far. And fourth, keep the fifteen February Phase One compliance line modular—because if the underwriter's forty-five-thousand-dollar risk-mitigation credit letter comes through this week, I want to see immediately how that changes February cash without pretending the remaining one-hundred-and-ninety-thousand contract tranches or the March SLA cap disappeared.
Exactly right. We will isolate that fifteen February line so a verified underwriter credit letter updates only the February outlay and opening reserve headroom—and automatically invalidates any prior draft sign-off until we re-verify the rest of the pack. Fifth: nobody contacts the syndicate, the vendor, or the shipper off the back of this call.
That covers every single base. I've got Tuesday afternoon in my calendar for the three internal documents—the treasury reserve statement, the committed February-March operational debits, and the corridor treaty payment-terms page—and I'll chase the loss adjuster and Phase Two schedule separately without promising dates I don't control.
Agreed. The very first thing that will land with you and General Counsel on Thursday is either the source-checked two-scenario comparison pack or a crisp missing-evidence hold note—nothing leaves unverified.
Brilliant. Thank you, Daniel—this already saved me an hour of untangling spreadsheets before Friday's committee. Speak on Thursday.
Thanks Claire. Good luck on the Johannesburg ops call—speak Thursday.
Marine cargo treaty: fixed $68,000 monthly rebate through December. Voyage 714 Durban–Rotterdam cold-chain excursion logged at $480,000 provisional gross exposure; causation, salvage and policy excess unconfirmed.
That's the voyage seven-fourteen excursion. I have four hundred and eighty thousand dollars written at the top of my board pack. That was the gross spoilage figure the depot manager logged the night the vessel docked.
Here it is—page three of the Rotterdam lab annex. Sorry, Daniel, please cross out the four hundred and eighty thousand. Two of the six containers stayed inside the two-to-eight-degree stability envelope on internal data loggers and cleared QA release. Three hundred and ten thousand dollars is the revised gross claim estimate. We still don't have the insurer's signed adjustment certificate, and salvage credit plus policy excess aren't netted off yet.
Approved risk-mitigation credit covers $45,000 of Phase 1 corridor telemetry commissioning on 15 February, applied directly against the compliance vendor invoice. No cash is remitted to Meridian. Phase 2 tranches of $190,000 remain Meridian’s responsibility on dates to be agreed.
Permanent employee. Net monthly income R52,000. HR exit estimate R300,000, provisional; timing and deductions unconfirmed.
There’s a leaving payment too. I think it’s R300,000. That’s what I wrote in my notebook when HR first spoke to me.
Hang on. I’ve found the voice note I made after the second HR meeting. Sorry, R180,000 was the revised estimate. Please cross out the three hundred. I still don’t have a letter, and I honestly don’t know whether that figure is before deductions or when they’ll pay it.
The award covers the full R28,000 January registration charge. The university will credit the student fee account directly. No cash is payable to the family. Tuition of R56,000 remains the student’s responsibility. This letter does not set its instalment dates.
Target industries & interactive demos
Rather than generic chat prompts, X-AI targets specific recurring bottlenecks where source accuracy and auditability matter: adviser review packs, invoice exception checks, insurance claim preparation, stock-constrained quotations, and studio campaign direction.
Open any sector study below to change a factual input, inspect the cited source, and see the exact decision reserved for your reviewer.
Trace every number in the file note, cash timeline, CRM delta, task register, and client-only recap back to exact call timestamps—keeping unconfirmed estimates out of available cash.
Reconcile contract rate amendments against customer concessions—separating a justified R2,400 review candidate from an unsigned exception that must be held.
Cross-check intake notes against received files so handlers never re-request an estimate already on file—and hold mismatched item codes automatically.
Distinguish 10 physical units on hand from 2 unconfirmed supplier units so draft quotes never over-promise stock or delivery dates before owner review.
Keep product geometry and specifications locked while comparing two distinct three-shot campaign treatments and edit-decision tables before production.
Local & offline security
X-AI builds local AI systems for International and South African business teams, with technology already used by major corporate clients in insurance, finance and banking. Agreed transcription and drafting run inside your private environment—capable of operating offline without external per-token cloud model fees on local steps.
Illustrative scenario assumption only (not a measured customer benchmark): if manual post-call administration takes 195 minutes and checking a source-linked draft takes 15 minutes, 180 minutes (3 hours) of adviser capacity returns per completed review. Hardware, licences, storage, power, support and human review still require explicit budgeting.
Manual post-call write-up vs. source-linked adviser check
Scenario model (not a customer benchmark): comparing 195 minutes of manual post-call write-up against 15 minutes of adviser review returns 180 minutes (3 hours) of capacity per completed review. Measure actual human minutes—including exceptions—in an authorised pilot.
