01 / Approvals
Approval routing
Requests that route themselves, chase themselves, and record who decided what.
8 steps 1
Solutions
Twenty things we build, shown as the steps they delete.
Every one of these is a real process that someone performs by hand today. The struck lines are the parts that stop happening. What is left is the part that needed a person all along.
Process
Industry
20 solutions
02 / Approvals
Spend approval
Requests that approve themselves under the limit, and route to the right person over it.
8 steps 1 Branches
03 / Approvals
Leave and absence
Requests approved in the chat window they were asked in, with the team calendar and the morning digest updated behind them.
7 steps 1 Branches
04 / Approvals
Contract renewals
Renewals that surface months before they lapse, with the decision already prepared.
6 steps 1
05 / Onboarding
Starter setup
Accounts, licences, equipment and access, all from one form on the day someone starts.
8 steps 1
06 / Onboarding
Leaver offboarding
Access removed on the last day, not whenever somebody gets round to it.
7 steps 1
07 / Invoices
Invoice capture
Documents read on arrival, matched against the order, filed and queued for payment.
7 steps 1
08 / Invoices
Three way match
Invoice, order and delivery checked against each other, with only the disagreements reaching a person.
7 steps 1 Branches
09 / Invoices
Statement reconciliation
Supplier statements checked against the ledger, with only the differences surfacing.
6 steps 1
10 / Reporting
Recurring reports
The same report, built the same way, sent at the same time, by nobody.
7 steps 1
11 / Reporting
Data hygiene
A weekly audit that tells each person what is theirs to fix, rather than telling everyone the data is bad.
6 steps 1
12 / Reporting
Exception alerts
Being told when a number moves, instead of reading a report to find out.
6 steps 1
13 / Handovers
Team handover
Work moving between teams with its context attached, so nothing is re-explained.
6 steps 1
14 / Handovers
Legacy system bridge
Work moving into a system that has no API, driven the way a person would drive it, without a person doing it.
6 steps 1
15 / Handovers
Case escalation
Work that has waited too long moves up on its own, with its history attached.
6 steps 1
16 / Requests
Expense claims
Claims checked against policy on submission, so only the exceptions need a manager.
7 steps 1 Branches
17 / Requests
Document generation
Quotes, contracts and letters assembled from the request, not from last time’s copy.
7 steps 1
18 / Requests
SLA escalation
A clock on every ticket, set by how bad it is, that escalates itself rather than waiting to be noticed.
7 steps 1 Branches
19 / Requests
Lead capture
Enquiries read as they arrive, checked against who you already know, and answered before anyone has opened the inbox.
7 steps 1 Branches
20 / Requests
Request intake
Intake that captures what is needed first time, and tells the requester where it is.
7 steps 1
Nothing matches both of those yet. Widen one of them, or ask about a process that is not listed, most of what we build was not on a list first.
Yours will not match any of these exactly.
They never do. Describe it in a sentence and we will tell you which parts can go.