Skip to content
All servicesBuild

Automation

Repetitive work handled automatically, on a schedule.

  • Scheduled tasks
  • Data collection
  • Integrations
  • Internal tools

What this is for

Work that repeats, in the same steps, to the same schedule. Anything a person does the same way every time is a candidate: moving records between systems, producing the same report, checking whether something arrived. It is worth doing where the steps are stable and the volume is real, and worth avoiding where the task changes every time. The gain is not only time — the automated version does not skip a step on a busy day.

What it covers

  • Scheduled tasks

    Jobs that run on their own to a schedule, with a record of each run and an alert when one fails.

  • Data collection

    Information gathered from the systems and sources it already lives in, on a schedule, into one place it can be used from.

  • Integrations

    Two systems that do not talk to each other made to, so the same information is not entered twice by hand.

  • Internal tools

    Small interfaces for the people who trigger or supervise the automated work, so running it does not require a terminal.

What you end up with

  • The job running to a schedule

    Running unattended in your own environment, rather than on somebody’s laptop.

  • An alert when a run fails

    Reaching a person who can act on it. Automation that fails silently is indistinguishable from automation that has stopped.

  • A record of every run

    What ran, when, and what it changed — so a disputed result can be traced rather than re-argued.

  • The manual version retired

    Switched off deliberately once the automated one has been checked against it, rather than left running alongside indefinitely.

What we need from you

  • The current steps, in order

    As they are actually performed, including the checks people do without thinking of them as steps.

  • Access to the systems it touches

    Accounts or keys for each one, issued to the automation itself rather than borrowed from a person who might later leave.

  • What should happen when it goes wrong

    Whether a failed run should retry, stop, or hand back to a person — and which person that is.

Who works on it

How it runs

  1. DiscoveryFirst

    We work out what you need, what it has to do, and what it will cost.

    • Scope written down
    • Fixed quote
    • Agreed timeline
  2. DesignBefore the build

    You see the site before it is built, on desktop and phone, and approve it before the build starts.

    • Designs to approve
    • Mobile and desktop
    • Final copy
  3. BuildThe build

    The design is built to its measurements, on a link you can open at any point during the build.

    • Live preview link
    • Progress you can see
    • Content loaded
  4. LaunchHandover

    Domain, hosting and email pointed at the new site. Checked on real devices, handed over in your name.

    • Live on your domain
    • Accounts in your name
    • Support after launch
  5. SupportAfter launch

    Updates, fixes and changes for as long as the site is live.

    • Updates and fixes
    • Monitoring
    • A number to message

Questions people ask first

  • With a conversation about what you actually need, and then a written scope with a price against it. Nothing is built until you have agreed both, and that scope is what the work is measured against for the rest of it.

Also under Build

Get in touch

Every one of these reaches us directly, and is answered by a person.

11:15Triple A