The catalogue

What we automate — and what we refuse.

Most agencies will tell you everything is automatable. Here is the honest version: what we build first, what usually comes second, and the things we turn down however much you offer.

55 automations

We build thisRecurring, countable, and a person can approve anything that matters.

Usually secondReal value, but a longer build or a fiddlier integration. Better once the first one is running.

We will push backSells easily and disappoints often. We will probably talk you out of it.

We will not buildNot negotiable, at any price. The reasons are below each one.

Before we quote anything

We score every request against four questions. Two failures and we will tell you it is not worth building, or suggest a smaller version that is.

Does it happen weekly or more? Automating a monthly twenty-minute job saves four hours a year.
Is the saving countable in hours or rupees? If nobody can name a number, nobody will value it in month three.
Can a person approve before anything irreversible happens?
Do you already own the tools? If it needs a migration first, that is a different and larger project.

When we will tell you not to automate

Some of the best calls we have end with us talking someone out of a project.

It happens rarely. The build costs more than it saves.
The process is still changing. You would be paying us to rebuild it every month. Wait until it settles.
The real problem is upstream. If the leads are bad, automating follow-up just processes junk faster.
One person does it and likes it. Automation that removes the interesting part of someone’s job gets quietly worked around.

Not sure which of these is yours?

Tell us what you are still doing by hand. We will tell you which of it is worth automating.

Show me what I can automate →