Otto owns the job.
You own the decision.
The agents do the reasoning and the execution. Otto holds the job, the activity history, the approval and the command. Your accounting system stays the final system of record. That separation is why Otto can add a new agent without rebuilding anything.
Review queue
March 2026 · Lamusse & Co · 5 of 214 remaining
Otto flagged this. The VAT on IBL/44192 is 18,600.00, but 15% of the net is 18,600.00 only if the 142,600.00 is VAT-inclusive. The invoice does not say which. Otto has not guessed — please confirm the treatment.
Four steps. The third one is the product.
Nobody changes how they work. Documents arrive the way they always have, and a person still signs everything that matters.
It arrives the way it always has
Nobody changes how they work. Documents keep coming by email, on a shared drive, over WhatsApp, or in someone's hand — and all of it lands in one pipeline.
- A forwarding address per client, so email carries the volume
- A watched folder your team can map as a network drive
- Drag and drop in the app for the stragglers
- Duplicates caught before they reach the ledger twice
One engine. Many processors.
The single most important structural decision in the product: build concretely twice, abstract on the third. New use cases become configuration rather than a new system to maintain.
Processors
Invoices · Bank rec · VAT · Onboarding · CDD · Social
Each agent is a processor: its own schema, its own review screen, its own rules. A new use case is configuration, not a new codebase.
Workflow engine
Cases · steps · state machine · timers · approval gates
Long-running work that waits. An onboarding case can sit open for three weeks chasing a passport copy and still know exactly where it is.
Shared core
Tenancy · auth · storage · queue · audit log · dashboards
Built once, properly, before anything sat on it. Tenancy in particular is never retrofitted — it is enforced in the database itself.
Four rules everything else bends around. Models extract, code computes — no model does arithmetic, applies a tax rule, or makes a final classification. Regulated judgement is never automated. Tenancy is enforced by the database, not by application discipline. And nothing irreversible happens without human approval.
Every agent,
on one screen.
Agents can be separate services with their own credentials, tools and channels — and your team should never have to know that. Otto presents them as one workforce, with one activity feed, one approval queue and one place to see what is running.
Agent health, in business terms
Online and idle, working, waiting for approval, degraded, offline. Plus last heartbeat, current task, last success, success rate and jobs today. Online and working are not the same state, so Otto does not pretend they are.
Commands, not prompts
A button in Otto never fires a loose sentence at an agent. It creates a structured, signed, idempotent command with a target record and a before-and-after — so a double click cannot bill your client twice.
Every job, from every channel
A request typed into Telegram and a document dropped in a folder produce the same record: who asked, what was interpreted, which tool ran, what came back, how long it took, and what a person decided.
One ledger format, many ledgers
Otto holds a normalised invoice and converts it through adapters — Zoho, Sage, Xero, QuickBooks, Odoo. The same agent sells to firms running different software.
Same engine. Three very different conversations.
An accounting practice buys capacity. A management company buys inspection-readiness. A broker buys not missing a renewal. The packaging, the deck and the regulatory conversation differ; the machinery underneath does not.
Accounting practices
Take on more clients without hiring more juniors.
Invoices, receipts and bank statements arrive the way they always have. Otto reads them, matches them, and hands your team a checked draft. Your preparer edits the exceptions and your partner signs.
- Document capture with VAT treatment and suggested GL codes
- Bank reconciliation with per-client learned rules
- VAT 3 figures and the monthly annex, assembled
- Client chase-ups drafted, never sent without you
Management companies
Inspection-ready, not just faster.
Otto assembles the CDD file, runs licensed screening, and pre-populates your board-approved risk matrix. It shows its working on every line. Your MLRO assigns the rating — Otto never does.
- Onboarding cases with timers and automatic chase-ups
- CRA pre-populated from your own scoring methodology
- Sanctions, PEP and adverse media from a licensed provider
- Deadline register across every administered entity
Insurance brokers
Never miss a renewal again.
The same engines, pointed at your dates and your insurer statements. Five quote PDFs in five layouts become one like-for-like comparison table your client can actually read.
- Renewals pipeline at 30, 60 and 90 days
- Commission reconciliation against insurer statements
- Quote comparison across insurers, side by side
- Claims pack assembly and document chasing
Seven steps, and we never skip the fifth.
The parallel run is what turns scepticism into trust — and it is where your accuracy benchmark comes from.
- 01Scoping callWhich entities, which systems, which volumes.
- 02Sign the MSA and DPADrafted by a Mauritian lawyer. Yours to review.
- 03ProvisionYour tenant, your users and roles, your forwarding address, your folder.
- 04Historical importThree to six months of past data, so the rules memory starts warm.
- 05Parallel runTwo to four weeks. Your team works as normal AND checks Otto beside them. This is the step nobody skips.
- 06Agree the baselineWe measure how long the work actually took. That number goes in the contract.
- 07CutoverAnd a monthly report that argues its own value in your numbers.
Show us your March.
Three real bank statements and twenty invoices from one entity, under NDA, redacted if you prefer. We will run Otto on your data and show you the result.