Do I need technical staff to run automations?

You do not need a developer on staff. You do need to answer one question before launch: who owns this?

What running an automation actually involves

Once live, a well-built workflow is mostly invisible. The real ongoing work is:

• Noticing when the output looks wrong. Automations rarely fail loudly. They fail quietly, by processing something incorrectly for a fortnight before anyone checks.
• Handling the exceptions it escalates. Any sensible system pushes the unusual cases to a human. Someone has to be that human.
• Knowing when something upstream changed. A new field in the CRM, a renamed spreadsheet column, a supplier changing their invoice layout. These are business changes, not technical ones, and the person closest to the process spots them first.
• Holding the credentials. Accounts, API keys and access should sit with you.

None of that requires code. It requires someone who cares whether it works.

Why the owner should not be technical

The best owner is usually the person who did the task manually. They know what a correct result looks like, which is the only reliable way to catch a system quietly going wrong. A developer who has never seen the process cannot tell a plausible wrong answer from a right one.

What a proper handover includes

When we finish a fixed-fee build you get documentation of what runs, when it runs, what it touches and how to change the parts designed to be changed. You keep the accounts. Fixed-fee projects include 30 days of support after launch, which is deliberately the window when the real edge cases surface.

We build for handover on purpose. The aim is a business that can run its own systems, not one that has swapped a manual dependency for a dependency on us.

When ongoing support is worth it

A retainer from £2,500 a month makes sense when you have several live systems, when the business changes often enough that workflows need regular tuning, or when nobody internally wants to own the monitoring. It covers watching the systems, fixing what breaks, and building the next thing.

It is not compulsory. Plenty of clients take the handover, run the system themselves and come back when they want something new built.