About Me

What I work on

Automation architecture, integration reliability, operating models for low-code systems, and practical release controls.

In practice, that means helping teams move from ad-hoc workflows to automation they can trust — without losing the accessibility that made low-code appealing in the first place.

What I write about

How to make visual automation maintainable in real organisations: version history, environment promotion, and clear accountability for change.

Much of what I write is informed by seeing the same patterns repeat — both in small businesses and large enterprises — when automation grows faster than the structure around it.

Background

I first started using low-code automation tools while running my own e-commerce business.

During Covid, when restrictions made it impossible to hire support, automation became the only way to scale. Tools like Make.com allowed me to keep orders flowing, systems connected, and operations running — without a technical team.

That experience shaped how I think about automation:

It has to be practical.

It has to work with limited resources.

And it has to be understandable by the people running the business.

After selling the business, I moved into backend engineering roles within the banking sector, working on Java-based systems, APIs, and enterprise integration.

There, I saw the other extreme: automation at scale, with governance, change control, and reliability treated as non-negotiable.

My work now sits between those two worlds — combining the pragmatism of small-team automation with the discipline required in regulated environments.

Topics I'm exploring

• How to version control Make.com automations
• How to manage changes in low-code workflows without breaking production
• Best practices for scaling automation in small teams
• Introducing external backups for visual automation tools
• When and how to upgrade governance practice when using low-code systems