The statements land, from a bank, a platform, a supplier, and someone matches every line against what actually hit the account.
Operational AI systems
Put the routine work on repeat.
Private AI systems for property operators, professional services, and business teams. Connect document intake, customer communications, and reporting to the tools your team uses, with source visibility and human review built in.
The reality
Every week the same stack of documents arrives, and someone keys it in by hand.
A document comes in as a PDF. Someone opens it, reads it, and retypes the numbers into the system that needs them.
The same customer and tenant questions arrive all day, and a person answers each one, even the routine ones anybody could.
The weekly report is a manual rebuild of numbers that already sit in the tools the team runs.
~80 to ~10 hrs a weeka London property team, payout reconciliation and guest comms, inside the first week live
Until it's one button.
What the button does.
Run the workflow.
The files your team already gets go in. The finished artifact comes out. Nothing moves to a new platform.
The inboxwhere the documents land
The spreadsheetwhere it gets keyed in
Your system of recordthe tool you already run
One clickRun the workflow
The finished artifacta reconciliation, an entry, a reply, or a report
It reads the files that already arrive, does the routine part, and ties every figure back to the document it came from. A second pass rederives the work before anything shows. You review and sign.
Connected operations
Core workflows, built around your team.
01
Payouts and statements arrive from every platform in a different shape.
Reads each statement, matches every line against the bank, and surfaces only the breaks with the money at risk on each one. Works for property payouts, marketplace remittances, or agency billing.
02
Inbound documents pile up waiting to be typed into a system.
Reads each one as it lands, pulls the fields that matter, and writes a structured entry your system can take, with the source page cited on every value.
03
Customer and tenant questions come in all day, most of them routine.
Drafts answers to routine questions from approved sources, and routes exceptions to a person with the full thread attached.
04
The weekly report is rebuilt by hand from numbers you already have.
Drafts it straight from the data sitting in your systems, every figure linked back to where it came from, ready for a human to read and send.
Proof
Most of what we build is finance: covenant checks, cash application, close packs. But the pattern underneath doesn't care what industry you're in. Read the document that already arrives, do the routine part, tie every figure to its source, block the output until a second pass agrees, keep a named human on the sign off. We ran exactly that for Regal Realms, a London property firm. Three people were spending around 80 hours a week reconciling Booking and Airbnb payouts and answering guest messages. Within the first week it was closer to 10. The full write up is the Regal Realms case study on this site. If your week has a repetitive, document driven grind, the pattern probably travels to it too.
Explore the underlying builds
Related workflows available in the Consultance build library.
Statement Matching PackTurns a stack of bank, custodian, and platform statements into a matched ledger with a clean break report. Extraction runs offline, matching runs in your own Claude. Free to run.Short Let Ops AI TeamThe same guest comms and back office pattern that runs at Regal, packaged for any short let operator. Free to pull down and keep.Enterprise Automation PackMaps every workflow worth automating, finds the real bottleneck first, and gates every money touching step behind a named human. Free.Built to be reviewed
What you keep.
- It runs in your tenant. Your data never leaves your environment.
- Every figure in the output traces back to the file it came from.
- A second pass rederives the work, and the output blocks until the two agree.
- You own the code. No subscription, no seat you rent back from us.
- No new login. It works inside the tools your team already opens every morning.
Built for the operations lead who would rather run the exceptions than key in the rest.
The manual version is free
Try it on your own file first.
The packs below run the same read on a document you paste in, in your own Claude, today. Free to pull down and keep. The installed version is the one wired into your inbox and your system of record, running the second a file lands. And if your industry isn't one of the four above, that's what the audit call is for: we scope whether the pattern fits your grind before anyone builds anything. The door stays open.
Explore the libraryPut your own file in front of it.
The audit is 30 minutes. You describe the thing your team keys in by hand every week, we put a dollar number on it and tell you straight whether this moves it. No pitch deck.
Or grab a time for the audit