Turning messages into orders
Orders arrive by email, WhatsApp and spreadsheet, then get keyed in by hand, often twice.
- Reads email, WhatsApp and attachments
- Matches what was ordered to your catalogue
- Stops and asks a person when it isn't sure
AI automation studio
Your best people
are doing data entry
Invoices retyped into the accounts system. Orders copied out of WhatsApp. The same report rebuilt every Monday. We automate that work so the people you hired can do the job you hired them for.
Starts with one process and a two-week pilot. You'll know the hours saved before you commit to anything bigger.
What that covers
- Invoices and documents
- Order entry
- Inbox triage
- Reconciliation
- Weekly reporting
Taking on new projects now
“A back office spends most of its week moving information between systems that were never built to talk to each other.”
Nobody planned it that way. The systems arrived one at a time, each solving a real problem, and the gaps between them became somebody's job.
What we automate
The work that fills your team’s week
The one worth explaining in full
Reading invoices so nobody has to type them
Supplier invoices, delivery notes and forms arrive as PDFs, scans and photos taken on somebody's phone. We pull out the fields you care about and write them into your accounts or ERP system, then flag anything that doesn't match the purchase order.
- Handles phone photos, not only clean PDFs
- Writes into Tally, Zoho, QuickBooks and most ERPs
Sorting the shared inbox
Shared inboxes fill faster than anyone can clear them. We classify what arrives, route it to whoever owns it, and draft the first reply for the questions that come in every single day.
- Routes on arrival, before anyone opens it
- Drafts replies for the repeat questions
- Sends anything unusual straight to a person
The Monday report
The report that costs someone a full day, and the reconciliation nobody volunteers for. We pull the numbers from every system involved, compare them, and send only the exceptions to the person who can act.
- Pulls from several systems at once
- Shows the gaps instead of quietly filling them
How we work
One process at a time, measured
You see the numbers before the build, and one automation running before we start the next.
- 01
Process audit
A week inside your operation. We follow the work, time the steps, and come back with the three processes costing you the most, and what each would take to automate.
- 02
Pilot
One process automated end to end, running alongside your team for two weeks so you can compare its output against the old way.
- 03
Rollout
The pilot goes live, your team stops doing that task, and we start on the next one.
- 04
Run and improve
Monitoring, error handling, and changes as the business shifts. When a system it depends on goes down, someone here knows before you do.
Why us
What working with us looks like
We measure first
The audit gives you hours per week and cost per task. If a process isn't worth automating, that shows up in the numbers before you've spent anything on it.
Somebody still signs it off
Anything touching money, a customer promise or a legal document gets an approval step. The automation drafts it. A person approves it.
It fails loudly
When an automation can't finish something, it raises an alert and hands the item back. The failure mode we design against is the quiet one.
You own everything
Your repositories, your cloud accounts, your data, from the first commit. Move it in-house whenever you like. You don't need our permission or our help.
How it is built
Automation you can audit
Every run leaves a record: what came in, what the system decided, who approved it.
READING
Documents, email and chat
Models pull structured fields out of invoices, forms, email threads and WhatsApp, each field carrying a confidence score.
DECIDING
Rules first, models second
Plain rules handle what plain rules can handle. Models take the judgement calls. Low-confidence cases go to a person, full stop.
ACTING
Into the systems you already use
Writes into your ERP, accounts software, CRM and spreadsheets through their own APIs, retrying when one of them is down.
WATCHING
Nothing disappears quietly
Every step is logged and searchable. Model spend has a ceiling. A failure raises an alert instead of vanishing.
Pricing
What it costs
Start with the audit. Everything after that is priced against the hours it gives back.
Process audit
On request
fixed fee, one week
We map how the work actually happens, then cost out what's worth automating and what isn't.
- Time and cost per process, written down
- A ranked list of what to automate first
- Yours to keep if you stop here
Automation build
Most projectsOn request
per month
We build and roll out automations, one process at a time.
- One process live before the next starts
- Approval steps where they are needed
- 30 days notice to stop
Care
On request
per month, once live
Someone watching it while your team depends on it. If a connected system changes, we hear about it before you do.
- Monitoring and error alerts
- Fixes when a connected system changes
- An agreed number of change requests
Beyond automation
Automation needs somewhere to live
When a process needs a screen, an app or an internal tool, the same team builds it. We've also shipped our own product, which is a better proof point than anything we could write here.
Internal tools
The admin panel your team opens every morning, built around the process instead of bolted onto it afterwards.
Mobile apps
iOS and Android from one codebase, submitted to both stores by us.
Websites and backends
Marketing sites, APIs, payments, and whatever glues your existing tools together.
Our own product, live on Google Play
Expenso: An expense tracker that works by voice, and keeps everything on the phone
FAQ
Questions we get before the first call
How does this start?
With a paid process audit. We spend a week watching how the work gets done, timing the steps and talking to the people doing them. You'll get a written report with hours and cost per process, a ranked list of what's worth automating, and a fixed quote for the first one.
What kind of work can you automate?
Anything repetitive that moves information between systems: reading invoices into accounts, turning emailed orders into records, sorting a shared inbox, chasing documents that never arrived, compiling the same report every week. If a person follows the same steps each time, it's a candidate.
Will this replace people on my team?
In our experience it moves them. The work we automate is usually the part nobody wanted, and the queue of real work is usually longer than the team can reach. We'll tell you honestly how many hours a week a process takes back. What you do with those hours is your call.
What if the automation gets something wrong?
Every field carries a confidence score. Anything below the threshold goes to a person instead of through. Steps touching money or a customer promise have an approval built in, and a failed run hands the item back rather than guessing.
What does it cost?
The audit is a fixed fee. Build work is a monthly rate sized to what's in flight, cancellable with 30 days notice. We price it against the hours a process takes back, so you can weigh it against a salary line.
Do you build apps and websites too?
Yes, and we ship our own products alongside client work. Automation often needs an interface or an internal tool around it, so the same team builds those. Have a look at what's live on the products page.
Contact
Tell us which task your team complains about
Name the process that eats the most hours. You'll hear back from the person who'd actually automate it, and the reply will have questions in it.
hello@zorizonlabs.com
A person reads every message that arrives here.