How automation work gets learned here

Automation is the newest part of the practice and the fastest growing, which means most of the people doing it did not arrive already doing it. They came from support, QA or WordPress work, and moved across because a client project needed it and they were the one closest to the problem.

Where it starts

It usually starts on the support side, because that is where the failure cases are visible. Someone answering a client on why a form submission never reached their CRM ends up reading the workflow that was meant to carry it. Once you have read a few of those, building one is a smaller jump than it looks from outside.

The tools are n8n for workflow automation, Zoho and HubSpot on the CRM side, the WhatsApp Business API for client messaging, and AI models wired in where they earn their place rather than because they are available. Nobody is expected to arrive knowing all of it.

The work that changes things

The turn is always a live client build rather than a course. A client wants their enquiries routed, their quotes chased and their CRM updated without anyone retyping anything, and someone has to own that. The first one is done with a senior reviewing every step. The second one is done with a review at the end. The third is yours.

• Every recurring workflow gets an SOP, so the second implementation is not a rediscovery of the first.
• Reviews are written and specific, on the build rather than on the person.
• The client-facing thread stays with the project manager, so the build is not interrupted by scope conversations mid-task.

What it demands

Automation work is unforgiving about detail in a way design work is not. A workflow that is ninety per cent right silently drops the other ten per cent of a client's leads, and nobody notices for a fortnight. The people who do well at it are the ones who test the failure path before they ship the happy one.