Three kinds of work, each with an example.
Each block comes with something you can touch instead of a description: a document being read, a screen with the state of play, an order you can place yourself. All with made-up data — no client work is shown on this site.
Work that's the same every week doesn't have to be done every week.
The most expensive manual work in a company is rarely complicated. It's someone going through the same list on a Thursday afternoon: opening attachments, copying amounts, updating a list, sending an email to say it's done.
Work like that can be handed to a system — and that now goes much further than it used to, because a computer can read free text. Below is what that means in practice.
Filed in the bookkeeping, linked to the right job
Reading documents and messages
Invoices, delivery notes, enquiries by email, photos of receipts. What you need is pulled out, even when every supplier uses a different layout.
Passing data on without retyping
What arrives in one place is ready in another. Accounting, CRM, planning, a folder on the server — it doesn't matter where it has to go.
Watching and warning
A message in WhatsApp, Slack or email the moment something gets stuck or looks off. You don't have to check whether it ran; you hear about it when it didn't.
What we use this for ourselves: our own quotes, enquiries and follow-ups run through a chain like this. We don't build anything we don't run ourselves — which is also why we can be honest about where it goes wrong.
When no package fits the way you work.
At some point it isn't one thing that's stuck, it's the whole. Planning in a spreadsheet, jobs in the inbox, documents in a folder, and the overview in one person's head. Each piece on its own is manageable; together they aren't.
Then we build the system around it. Not a standard package you bend your work towards, but the structure and the fields you already use.
Five places where the work sits now — and where it's heading.
What goes into a system like this
AI is in there where it demonstrably saves time — reading documents, connecting data, suggesting the next step — and nowhere else. No chatbot on the side because it looks good.
One screen with the state of play
Jobs, planning, people, equipment and outstanding items side by side — in the layout you work in, not a standard package's.
- Live status per job
- Roles and permissions per employee
- Reports you no longer have to make
Documents that read themselves in
Invoices, receipts and signed forms are read automatically and attached to the right job. Anything doubtful lands in a review list, not quietly in the books.
- Amount, number and supplier recognised
- Attached to the job automatically
- Anything uncertain goes to a person
Connections to what you already use
Your accounting package, calendar, inbox and existing systems stay where they are. We build the layer around them so data is entered once.
- No migrating everything at once
- Existing packages keep working
- Extendable step by step
Not a package you bend towards. The other way around.
Standard software forces a way of working that is rarely yours. We start with how things run at your company and build around that — including the exceptions that fit no package.
Example view with invented data — not a customer system.
What runs by itself, and what's waiting for you.
Not everything has to pass your desk. Most of it can run on; the occasional case needs a judgement no computer should make. This is that difference, made visible.
- Enquiries: Enquiry — Bakker & Zn — From the contact form, 6 min ago
- Enquiries: Enquiry — Meijer Group — Asks for a date that's already full
- Enquiries: Email — confirmation sent — Answered and scheduled automatically
- Enquiries: Enquiry — De Wit BV — Recognised as an existing customer, linked
- Enquiries: Quote request — 14 lines — Lines read out, prices fetched
- Enquiries: Email — question about lead time — Answered from the planning
- Enquiries: Enquiry — urgent, Saturday — Outside the standard window, needs approval
- Enquiries: Email — change of address — Processed in the customer file
- Jobs: Job 4182 — Scheduled for Wednesday, crew assigned
- Jobs: Job 4179 — Confirmation sent to the customer, nothing to do
- Jobs: Job 4171 — big one — Two people short on Thursday
- Jobs: Job 4168 — Updated after a change by the customer
- Jobs: Job 4160 — On the way, arriving around 14:20
- Jobs: Job 4155 — Marked complete from the phone
- Jobs: Job 4152 — Waiting for a signature on site
- Execution: Crew 2 — on the road — Three stops left today
- Execution: Receipt — materials collected — Photographed, linked to 4179
- Execution: Vehicle 12 — inspection — MOT expires in 9 days
- Execution: Hours — 6 staff — Booked to the job automatically
- Execution: Work sheet 4160 — Photos in, waiting to be closed
- Execution: Stock — 4 items — Written off and added to the order list
- Invoices: Invoice 2026-0391 — Drawn up from the work sheet, sent
- Invoices: Purchase invoice — €4,120 — Amount differs from the order
- Invoices: Invoice 2026-0388 — Paid, matched automatically
- Invoices: Invoice 2026-0384 — Reminder ready for Friday
- Invoices: Receipt — fuel — Scanned and booked to the trip
- Orbit
- the stream the work sits in
- Angle
- how far along it is, clockwise from twelve
- Size
- how big the item is
- Colour
- what it needs right now
Example view with fictional data — not a client system.
What your customers see, and where they can do something.
A site that only says who you are is a brochure. It gets interesting when something happens in it: a customer placing an order, an enquiry that arrives complete, a portal where someone finds their own documents.
Think of an ordering screen where a regular customer adjusts quantities and checks out, or a customer portal where someone finds their own invoices and jobs. Built in code, connected to what you already use — not a separate island next to it.
A screen like that, for your customers
- An ordering app for regular customers
- A customer portal where people find their own documents
- Works as well on a phone as on a screen in the office
Built, not clicked together
No theme with fifteen plugins on top. It loads faster, lasts longer, and you're not tied to someone's subscription.
Works on your customer's phone
Most of your visitors are on a device in their hand. That's what we design for, not as an afterthought.
Connected to the rest
An order that comes in doesn't have to be retyped. It lands straight in the planning or the administration you already have.
First, let's see whether it fits.
Half an hour, no obligation. Mostly we ask questions about how the work runs today. If it fits, we come in for phase one. If it doesn't, we say so right away.
Rather look for yourself first? Take the AI scan — a few minutes, no appointment.
info@xonuz.com- A short intake: where in your process does most of the manual work sit?
- An honest estimate of what there is to gain — and what there isn't.
- Advice on existing packages, even when that costs us the job.
- No sales talk, no deposit, no obligations.