Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
Python & Django

Where to Start

Last updated:

Four criteria

  1. Happens often — daily or weekly, so the saving is visible quickly
  2. Well understood — someone can describe every step
  3. Low consequence if it gets something wrong
  4. Wanted by whoever currently does it
The fourth matters more than people expect. Automation imposed on someone who did not ask for it gets worked around; automation someone wanted gets defended.

Good first candidates

  • The report assembled from several systems every week
  • The file that arrives daily and gets reformatted
  • The data re-keyed between two systems
  • The check somebody performs manually
  • The routine notification somebody sends

What to avoid first

  1. Anything customer-facing without review
  2. Anything financial without a validation layer
  3. A process nobody can fully describe
  4. Something the business is about to change
  5. The exception cases rather than the routine ones

Measure before you start

RecordWhy
Time per occurrenceThe baseline
FrequencyThe annual value
Error rate todayWhat improvement means
Who does itWhose time is freed
What they would do insteadWhether the saving is real

Two weeks of measurement before building costs almost nothing and it is the only baseline you will get.

Then the second one is easier

The first automation builds the monitoring pattern, the deployment approach and the organisational confidence. The second costs less and can be more ambitious for the same reason.

That compounding is the real argument for starting with something small and finishing it properly.

Frequently asked questions

How much should a first automation cost?

£1,500–£6,000 for something real. Much more than that for a first project is a large bet on an unproven approach.

How long before we see the benefit?

Within weeks for a daily process. That immediacy is why frequency is the first criterion.

What if it does not work?

You will know cheaply, and the monitoring and deployment work carries forward. That is a much better outcome than a large project failing slowly.

Should we tell the whole team?

Tell whoever is affected, before it goes live. Discovering an automation from its output is a poor introduction.

Keep reading

Not sure where to start?

Tell us the three most repetitive tasks in your business and we will tell you which one to automate first.

Book a free 30-minute call Get a project estimate WhatsApp us

Related services

What we build for problems like this one

Custom Software DevelopmentWeb DevelopmentMachine Learning