Automation for the work nobody should be doing.

Somebody in your business spends Thursday moving information from one screen to another. That is the work worth automating first.

A hand filling in a paper form on a clipboard with a gold pen

What we measure

  • Features built (not what we judge you on)
  • Tasks automated (not what we judge you on)
  • Hours returned

15 hrssaved a week · removals client

The process works. It works because three people hold it together with spreadsheets, copy and paste, and a reminder in somebody’s calendar.

  • The processWorks
  • The spreadsheetsFine
  • What happens when one of them is away?Unknown

One client, ten weeks

About 15 hours a week back from retyping quote requests.

Two people in a removals office spent most mornings copying details out of emails and web forms into a quoting spreadsheet. We sat with them for two days first, then built an assistant that reads each request and fills in the sheet, with a person checking every quote before it goes.

of office time saved each weekoffice time saved a week
15 hrs
average time to send a quote, down from 26to send a quote
3 hrs
more quotes turned into booked jobsmore quotes booked
+19%
Read the full case study
A warehouse worker scanning inventory with a handheld device

Filling in the quoting sheet

BeforeBy hand, from each email

AfterBy the assistant, checked

What changes

Measured in hours, not in features.

Each one is timed before the build and again after it.

  • You get

    Hours back, counted

    We time the task before and after. If the saving is not worth the build, that is a finding and we say it rather than building anyway.

  • You get

    Fewer things typed twice

    Every re-entry is a chance to introduce an error that somebody finds three weeks later, usually in front of a customer.

  • You get

    A process that survives a holiday

    Written down and running whether or not the one person who understands it is at their desk.

An office worker carrying a large stack of files and folders
The work nobody put a number onEvery hour of this is being paid for already. It is just being paid for in somebody's afternoon rather than in an invoice.

How it runs

Some of the work removed, the rest automated.

The third step is the one that saves clients the most money, and it is the one an automation supplier is least likely to offer.

Count it first

  1. Watch the work happen

    We sit with whoever does it and time it. Not a workshop about the process, the actual process, including the parts people are slightly embarrassed by.

  2. Count what it costs

    Hours a month, error rate, and what a mistake costs when it reaches a customer. Now there is a number to beat.

Then remove, then automate

  1. Delete before automating

    A surprising share of these tasks exist because of a report nobody reads or an approval nobody uses. Removing a step is cheaper and more reliable than automating it.

  2. Automate what is left

    The smallest thing that works, in front of the people who do the job, with a way to intervene when it gets something wrong.

Where it helps

The busywork we usually take off your desk.

  • Documents in, structured data out: invoices, orders, forms, applications
  • Systems that should talk to each other and do not
  • Reports assembled by hand every month by somebody senior
  • Sorting incoming enquiries and sending each to the right person
  • Checks that only happen when a person remembers to do them
  • A record of every automated action, so an error can be found and explained

FAQ

The questions we hear most.

Not in the work we take. The clients who get value from this are short of people and drowning in admin. If the brief is to cut a team, we are not the right studio for it.

Your turn

Bring the task that eats somebody’s Thursday.

Tell us what the task is and who does it. Within a working day we will tell you whether it is worth automating, whether some of it could simply stop, and whether we are the right people for it.