J-01Finance
Invoice matching
Reads supplier invoices, matches them to purchase orders and receipts, and sends mismatches to a person.
AI systems for the work your team does by hand.
harmoni picks one workflow, like invoice matching or ticket triage, builds the system that runs it on your data, and hands it to your team. Measured before and after.
harmoni/[Client]/Invoice matching
Example dataLive
| Invoice | Supplier | PO | Status |
|---|---|---|---|
| INV-20418 | Northwind Supplies | PO-7731 | Matched |
| INV-20419 | Brightline Packaging | PO-7740 | Matched |
| INV-20420 | Kestrel Freight | PO-7702 | Sent to a person |
| INV-20421 | Alder & Finch | PO-7744 | Matched |
| INV-20422 | Northwind Supplies | PO-7745 | Matched |
| INV-20423 | Marlow Office | — | No PO found |
Read-out · last 30 days
Handled end to end[94]%
Sent to a person[6]% with a reason
Time per invoice[42] → [3] min
Built with operations teams at
[client][client][client][client][client]
What we build
A system that does the routine part and hands you the rest.
It reads the work as it arrives, does what follows your rules, and sends anything unusual to a person with the reason. Nothing is decided silently.
fig. 01 — the sorter
example · 16 sorted · 1 to a person
ReadsThe work as it arrivesInvoices, emails, PDFs, tickets and forms, in the tools you already use.
DoesThe part that follows rulesMatches, enters, routes and drafts, with a check on every step.
Hands overEverything else, with a reasonA person sees each exception and why it was set aside.
How a job runs
Four stages. Each ends with something you can check.
-
01[1] week
Measure
We sit with the people who do the work, time it, and collect real examples.
You get: the baseline and a fixed price.
-
02[4] weeks
Build
We build the system on your data, inside your tools, with a check on every step that can fail.
You get: a system tested on last month’s work.
-
03[3] weeks
Run alongside
It runs on live work next to your team. Every exception goes to a person.
You get: the before and after numbers.
-
04ongoing
Hand over
Your team runs it. Everything sits in your accounts.
You get: [30] days of us on call.
Jobs we build
High-volume work your team does by hand today.
We start with one, prove it, then take the next.
J-02Support
Ticket triage
Reads incoming tickets, tags and routes them, and drafts the first reply for an agent to send.
J-03Operations
Order entry
Turns orders that arrive by email or PDF into entries in your ERP.
J-04Ops, Finance
Weekly reporting
Pulls the numbers from your systems into the weekly operations report.
J-05Legal, Sales
Contract checks
Compares incoming contracts with your standard terms and lists every difference.
J-06Everyone
Internal answers
Answers staff questions from your own documents and links the source.
A finished job
Every job ends with a read-out you can check.
J-01 · Invoice matching
Before
[42] min
After
[3] min
- Sent to a person
- [6]%
- Built in
- [5] weeks
- Owned by
- Finance
Placeholder figures until the first job is finished.
“[One sentence from the client’s finance lead about what changed for their team.]”
[Role], [company]
How we work
Six rules for every job.
- 01One job at a time.We finish one workflow before we start the next.
- 02Built inside your systems.Your data, your tools, your accounts. Nothing runs on ours.
- 03Measured before and after.Week one sets the baseline. The read-out shows the change.
- 04A person sees every exception.When the system isn’t sure, it says why and hands it over.
- 05Your team owns it.Runbooks, tests and training, so you don’t need us to run it.
- 06No demos.If it doesn’t run on your real work, it isn’t done.
Studio
A small team that builds what it sells.
[The people on your first call are the people who build your job.]
[photo]
[Role]
[Founder name]
[One line on what you ran before.]
Checks: the baseline, and whether the job is worth doing.
[photo]
[Role]
[Founder name]
[One line on what you built before.]
Checks: every step that can fail, before it ships.
Questions
What people ask on the first call.
What if it doesn’t beat the baseline?
[We stop, and you pay for week one only.]
Does our data need to be clean first?
No. Week one shows what’s usable. We fix what the job needs and nothing more.
Who owns what you build?
[You do. Code, prompts, tests and documentation live in your accounts.]
Bring us one job.
Pick the workflow that takes your team the most hours. In 30 minutes we’ll tell you whether it’s a good first job, how we’d measure it, and a price range.
From [€—] per job, fixedWeek one starts within [2] weeks[hello@harmoni.sh]