Who should own automation after it is set up?
Automation is not finished when it is built. Someone has to watch the replies, test that it still works, and update it when prices or seasons change. Naming that person before switching anything on is the difference between a system that keeps working and one that quietly stops without anyone noticing.
The three jobs that continue
Watching for replies. An automated text that gets a reply into an inbox nobody monitors is worse than not sending it. This job is daily and it needs a named person per time window.
Testing that it works. Automation breaks silently — a plugin updates, an API key expires, a platform changes a format. Nothing alerts you. Somebody has to submit a real enquiry monthly and follow it all the way through.
Keeping the content current. Prices change, seasons shift, services get added. A sequence still quoting last year's offer costs credibility quietly.
All three need an owner. Unowned, they are exactly the jobs that do not get done.
What each option means
You own it. Cheapest, and it depends on someone in the business genuinely having the hours and the inclination. Works when the person who will do it is identified by name rather than assumed.
The provider owns it. Someone is accountable and it costs a monthly fee. Works when the arrangement explicitly includes testing and updates rather than only the build.
Split. Provider owns the technical maintenance and testing; you own the replies and the content updates. This is the arrangement most small businesses end up with and it works, provided the split is stated rather than assumed.
The question that settles it
Who submits the test enquiry each month?
Name the person. If nobody can be named, the automation will break and stay broken — usually noticed weeks later during a quiet month, and often mistaken for a marketing problem.
What to agree before switching on
- Who receives replies, by time window
- Who tests, and when
- Who updates content, and how often
- What happens if something breaks out of hours
- Where the documentation lives
That last one matters more than it sounds. Automation nobody can explain is automation nobody can fix, and it is common for a system to become unmaintainable simply because the person who built it left.
The ownership point
Separate from who maintains it: the accounts must be in your business name. The messaging provider, the CRM, the email platform.
A provider maintaining your automation inside their own accounts means the workflows end when the relationship does — including the missed-call text-back that has been quietly saving jobs for a year.
The realistic recommendation
Have it built properly, keep the accounts in your name, and agree a monthly test with a named owner before anything is switched on.
The test takes five minutes and prevents the most expensive silent failure a small business marketing setup has.
Where it sits
Ongoing workflow support and optimization reviews are part of the AI Marketing System — $8,500 setup, $2,500 a month. The accounts stay in your name.
Deciding
Name the person who will submit next month's test enquiry. If you cannot, that is the arrangement you need to fix.
Frequently asked questions
What jobs continue after automation is built?
Watching for replies daily, testing monthly that everything still works, and keeping the content current as prices and seasons change. All three need a named owner.
What is the question that settles ownership?
Who submits the test enquiry each month. If nobody can be named, the automation will break and stay broken — usually noticed weeks later and mistaken for a marketing problem.
Should the accounts be in my name?
Yes — messaging provider, CRM, email platform. A provider maintaining your workflows inside their own accounts means the automation ends when the relationship does.
What should be agreed before switching on?
Who receives replies by time window, who tests and when, who updates content, what happens if something breaks out of hours, and where the documentation lives.