Skip to content

Article

Where AI actually belongs in a marketing stack

7 min read

Use plain code for anything rule-based, use a language model only where the input is unstructured language and judgement genuinely beats rules, and keep a human on any decision that spends money. Most of what is sold as AI marketing automation is ordinary scheduled automation, which is fine, because that is where most of the value is.

The useful question is not what AI can do in marketing. It is which parts of your current work are rules, which are judgement, and which are just assembly. Answer that and the automation plan mostly writes itself, and a fair amount of it turns out to need no AI at all.

Automate assembly first, because it is pure gain

Assembly is the exporting, formatting, joining, and chasing that fills a reporting week. It is entirely deterministic, it requires no judgement, and it is where the fastest return is.

  • Scheduled pulls from each ad platform and analytics into one place, so the monthly report stops being a manual export exercise.
  • Threshold and trend alerts on spend, conversion volume, and tracking health. This is the automation that pays for itself soonest, because it shortens the time between a tracking failure and a person noticing from weeks to hours.
  • Automated account checks for disapproved ads, budget capped campaigns, feed errors, and conversion actions that stopped recording.
  • Report assembly, where the numbers, the period comparison, and the charts are generated and a person writes only the interpretation.

None of that needs a language model, and putting one in the loop makes it worse. A model asked to do arithmetic will be right most of the time, which is the worst possible reliability profile, because it hides its failures inside plausible output.

Where a language model genuinely earns its place

The pattern is consistent: models are good where the input is unstructured language and the task is interpretation rather than calculation.

  • Classifying inbound enquiries by intent, urgency, and fit, so routing happens before a human reads them.
  • Finding themes across a large search terms report. A person reading two thousand queries misses patterns; a model grouping them into intent clusters gives the person something to actually judge.
  • Summarising sales call notes into the objections that keep recurring, which is the best source of landing page copy most companies already have and never use.
  • Generating first-draft variations for ad copy and feed descriptions, where volume matters and a human edits before anything serves.
  • Drafting structure for content briefs, which is genuinely useful and still needs an editor who knows the subject.

What should not be automated

Every competing article on this subject lists wins only. The limits are the part worth reading, because they are where automation projects cause damage rather than merely disappoint.

Unsupervised spend decisions

Do not give a model autonomous control of bids or budgets. The failure mode is not a slightly suboptimal decision, it is a large amount of money spent quickly on a bad data feed, and there is no upside that justifies that risk. Automated recommendations with a human approval step capture nearly all the value with none of the exposure.

Publishing without an editor

Generated text fails in a specific way: it produces confident sentences with no checkable claim inside them. That is exactly the quality that makes content worthless to readers and uncitable by answer engines. The edit pass that removes hedging and adds specifics is the part that creates the value.

Processes nobody has written down

Automating an undefined process makes it faster and less predictable at the same time. If the workflow cannot be expressed as steps and rules, the automation project is premature, and writing it down often removes the need for the project entirely.

How to actually build it

  1. Write down the manual process, step by step, including the steps people do without thinking.
  2. Label each step as a rule or a judgement. Rules become code. Judgements stay with a person, or get an AI assist behind an approval gate.
  3. Build the smallest useful version and put it into production. Platform-wide automation projects that launch all at once tend never to launch.
  4. Instrument it so it fails loudly. Automation that fails silently is worse than none, because people stop checking the thing it replaced.
  5. Review on a schedule and switch off what nobody reads. Unused workflows are maintenance debt, not assets.

That ordering is the whole method: deterministic where rules work, models where language needs interpreting, and a person wherever money moves. It is how we scope ai marketing automation, and it depends on the measurement layer being correct first, which is marketing analytics services.

AI marketing automation

Most of what gets sold as AI marketing automation is ordinary automation, and that is fine, because ordinary automation is where most of the value is. Pulling data on a schedule, checking it against thresholds, and alerting a human is deterministic work that should never involve a language model. We use AI where judgement genuinely beats rules, and plain code everywhere else, which is faster, cheaper, and does not invent things.

Read about ai marketing automation

Want this done on your account?

This is the method we use, written out in full so you can run it yourself. If you would rather not, that is what the audit engagement is for.

Start with an audit

Send us the account and what is bothering you about it. You get a written findings document either way, whether or not we work together afterwards.