Automate repetitive processes
Hours recovered every week
The manual steps your team repeats every week, turned into a process that runs on its own and tells you when something breaks.
The problem it solves
Someone copies data from one tool to another. Someone checks a list by hand every Monday. Someone sends the same email twelve times. Nobody defends these tasks, but they get done because there has never been time to sit down and remove them.
What I do
I measure first: how long each step takes today and how often it is done. Only then do I automate, starting with the process that offers the best ratio of hours saved to implementation effort.
I automate business processes (data moving between tools, reports, joiners and leavers, notifications) as well as systems tasks (deployments, server configuration, backups, credential rotation). The automation lives in your infrastructure, written in code you can read, with a log of every run and an alert when something fails. If a third-party tool is needed, the account is in your name: the process stays yours.
Scope
- Included: analysis of the candidate processes and automation of one or more of them, agreed in writing before we start.
- Not included: redesigning how your team works. I automate the process that exists; if it is worth changing first, I point it out and you decide.
Deliverables
- A map of the process as it is done today, with the measured time of each step and its exceptions.
- The automation in your repository and your infrastructure.
- A log of every run and an alert when something fails.
- An operations guide: how to start it, how to stop it and what to do if it fails.
- A handover session so your team can maintain it without me.
How it is measured
Hours of manual work per week before and after, measured on the same process. If the process produced errors or rework, also how many per week.
What I need from you
Someone to show me the process as it is done today, with its exceptions. The exceptions are the hard part and it pays to see them before starting.