Your team isn’t slow.
Your Tuesday is.
We come to your screen, watch the worst part of your week, and tell you honestly whether AI can fix it. Two hours. No slide deck.
*If it can't be fixed, that's a useful answer too — and it's cheaper than finding out later.
Symptoms
There is a difference between a week that was busy and one that was effective. You can’t tell which one you had from how tired everyone is — only from what actually finished. Open any line below to see what it usually costs.
The Monday report is four exports and a prayer.
Typical cost4–6 hours typicalestimate from our own engagements — not your number
What’s usually underneath: Data trapped in systems that won't talk to each other without a human bridging them.
Our invoices live in a spreadsheet only one person understands.
Typical cost2–4 hours typicalestimate from our own engagements — not your number
What’s usually underneath: Finance processes built on manual entry instead of structured data extraction.
We copy-paste customer details across three different tools to onboard them.
Typical cost5–8 hours typicalestimate from our own engagements — not your number
What’s usually underneath: Missing joins between your CRM, billing and provisioning.
Triage means someone reads every ticket just to assign it.
Typical cost6–10 hours typicalestimate from our own engagements — not your number
What’s usually underneath: Uncategorised inbound streams that need a person to work out where they go.
Nobody is sure which copy of the client list is the real one.
Typical cost1–3 hours typicalestimate from our own engagements — not your number
What’s usually underneath: Two or three systems each holding their own version of the same record.
We retype into the invoice what we already typed into the quote.
Typical cost2–5 hours typicalestimate from our own engagements — not your number
What’s usually underneath: Documents generated by hand instead of out of data you already have.
Month-end is three people and a weekend.
Typical cost4–8 hours typicalestimate from our own engagements — not your number
What’s usually underneath: Reconciliation done by eye at close, because the numbers never arrived joined up.
Most of this is one knot, not seven problems.
The wall above reads as seven separate problems, with seven separate budgets to find. It usually isn’t. The exports, the spreadsheet and the copy-paste are the same missing join, seen from three different desks. Untie it once and the symptoms fall together.
The Check-up
Five questions. No email, no call, nothing stored — the answer is yours the moment you reach it.
Step 1 of 5 · first one already answered
The answer
estimated hours lost per week
No JavaScript? Score it yourself.
The five questions, with their points, and the bands underneath. Add up the points for the answers that sound like you, then read the band you land in. Nothing leaves this page.
Roughly how many hours a week does someone spend moving data between tools by hand?
How often do mistakes slip through because a step is done by hand?
If the one person who understands the worst process went on leave tomorrow, what happens?
How much of the week goes on reading text just to decide who should handle it?
What are you actually looking for?
| Total points | What we would say |
|---|---|
| 0 | There is no problem here to sell you anything for. Nothing you told us describes work being lost. We would rather tell you that than find something to quote for. |
| 1–2 | This is a script, not a project. You do not need an engagement. We will send you the formulas or the small script that removes it, free. Charging for that would be silly. |
| 3–8 | Someone has built a job out of a missing join. There is real work here, and it is narrow work. A short automation takes most of it back — nothing needs rebuilding for that. |
| 9 and up | Good news: this is a two-week job, not a platform. This is the shape we are built for: one process, two weeks, a fixed scope, and it stops needing a person. |
| Answered “a platform” on question 5 | We are not the right people for this one. You want the work moved onto a new platform. We connect the tools you already have, and replacing them is a different and much bigger job. Better to say so now than in a proposal. |
How a house call works
Three steps, real durations, and exactly what you get at each one.
Breathe — we’ve done this before.
The Check-up
We sit down with the person who actually does the work. We watch them do it, find where the process breaks, and tell you exactly what AI can (and cannot) fix.
You get: An honest verdict, a real estimate, and if it’s just a spreadsheet problem, we give you the formulas and leave.
The Treatment
We build the automation layer. No massive enterprise rollout, no replacing your tools. We connect what you have so the data moves itself.
You get: The knot untangled. A process that runs quietly in the background without needing a human to carry the data.
On Call
When APIs change or edge cases break the flow, we fix it. You don’t have to hire an engineer to maintain the automation.
You get: Peace of mind. We monitor it, we maintain it, and you never think about it again.
What a returned week looks like
Our own project, not a client story. Travel Ruter takes trip requests and builds itineraries, and somebody used to read each request and route it by hand.
Hours returned to the team0of 9
Read and routed by hand Sorted on its own
Drag across the week, or use the arrow keys. Home and End jump.
Nine filled blocks, about an hour each — nine hours in a week, from one process. The hours are an illustration of the shape, drawn from our own project rather than a client result. Yours would be measured before we quoted anything.
What we won't do
- Sell you a platform.
We build connective tissue for the tools you already use. If you want to migrate everything to a new enterprise system, we are the wrong people.
- Rebuild what already works.
If your spreadsheet does the job, keep the spreadsheet. We only touch the parts that are actively hurting you.
- Charge for a script.
If your problem is a $20 script or a Zapier template, we’ll send you the script and the formulas, free. Charging for that would be silly.
- Bait and switch the team.
There are two of us. We do the check-up, we write the code, we answer the emails. No juniors, no hand-offs.
Price
There are two of us, so we plan to take on two engagements at a time. That limit is the whole reason the work can be good.
The Check-up
Two hours of forensic review of your worst process.
- System architecture review
- Data flow mapping
- Honest feasibility verdict
- Credited toward Treatment if we proceed
The Treatment
One to three weeks to build the automation layer and remove the knot.
- The automation layer, wired into the tools you already use
- Reading and sorting the text that currently needs a person
- Tested against your own historical data before it goes live
- Handover notes your team can actually read
The $500 Check-up is credited against this. A Treatment is only booked after one — we don’t quote from a description.
On Call
Optional. We stay on call so a changed API or a new edge case doesn’t quietly break what we built.
- API change monitoring
- We fix it when an outside service changes under us
- Rules re-tuned when the real world drifts
- We aim to answer within one working day
- No lock-in. Cancel any month and keep everything
Starts after a Treatment. Cancel any month and keep everything we built.
ILLUSTRATIVE ONLY. NOT AN OFFER. These are modelling figures — the shape of the three steps, not a published rate card. The first real number you get comes after a Check-up, in writing, and it’s the one we hold to.
What this doesn’t cover
- No new system to log into. If the answer is “buy a platform”, we’ll tell you which one and don’t expect to be paid for the opinion.
- No hosting bill from us. The automation runs on infrastructure you already pay for, in your name. We don’t become a dependency you rent.
- Nothing before the Check-up. We don’t quote a Treatment from a description. The figures above are our modelling, not a quote to you — yours is fixed only after we’ve watched the work.
- Not a team. There are two of us. If you need six people and a project manager, we’ll say so in the first call.