The problem

Most teams don’t have an automation problem. They have a time problem that looks like a lot of small chores:

• A new hire waits two days for accounts, because setting them up is a checklist someone has to work through.
• Deployments happen on Friday afternoons, by hand, and only one person knows all the steps.
• Backups exist, probably, but nobody has tried restoring one.
• Servers were set up years ago and nobody is quite sure how, so nobody wants to touch them.

Each of these is a few minutes or a few hours. Together they add up to a part-time job, and they’re exactly where outages and security gaps come from.

What I automate

• Provisioning and configuration. Servers, cloud resources and services defined as code, so they can be rebuilt, reviewed and changed safely.
• Deployments. Push a change, and it ships. No checklists, no “it works on my machine”.
• Backups and recovery. Scheduled, off-site, and tested, so a restore is a routine operation rather than a crisis.
• Accounts and access. Onboarding and offboarding that happen in one step, with access removed when people leave.
• Routine maintenance. Updates, certificate renewals, monitoring and alerts that run without anyone having to remember them.
• Glue work. Small scripts and integrations that move data between the tools you already use.

How I work

I start by reading what you already have and asking which tasks cost you the most time or worry. Then I automate the ones worth automating, one at a time, in plain, well-known tools rather than anything exotic.

Everything I build comes with documentation and is handed over to you. The goal is that your team can understand it, run it and change it without me.

Get in touch

If something in your IT takes too long, breaks too often, or depends on one person remembering the steps, I’d like to hear about it. Write to hello@gunnarbachelor.com, or find me on X and GitHub.