Why a SAAS marketing operating workflow needs owners, not tools

What to take away

Why does a workflow fail when the tools are fine?

Most stalled work is a decision problem, not a software problem. A draft sits with no named approver. A brief waits on a stakeholder who was never told they owned sign-off. The tooling works; the ownership map does not.

Write your stages in order: brief, build, review, publish, report. Next to each, one person's name. Not a team name.

Add two rules per stage: what triggers it, and what counts as done. A brief is done when audience, offer and success measure are written down. A review is done when the reviewer approves or returns it with comments.

Two owners means no owner. Split the stage or merge it. This is the discipline set out in our wider SAAS marketing operations and delivery guide, which maps the surrounding planning cycle.

Who owns each stage of the workflow?

Ownership gets skipped, then rebuilt badly after a missed launch. Assign five roles, even if one person holds two in a small team.

The demand lead owns the brief because they own the reason for the campaign. The marketing lead reviews because they carry brand and compliance risk. Small teams can merge the two, but say so in writing.

Where a channel is new to the team, training is the fix, not a workflow rewrite. The CIM runs digital marketing training courses covering B2B channels, which suits a specialist picking up an unfamiliar stage.

A worked example with typical day counts: a launch stalls because the brief carries no success measure. Demand lead adds the measure on day 0. Channel specialist builds on days 1 to 3. Marketing lead returns the assets on day 5 with comments.

Channel specialist republishes on day 8. Analyst sends the numbers on day 15. Your days will differ with channel count and review load.

What rhythm keeps the workflow moving?

A weekly slot does more than any dashboard. Hold 30 minutes with the five owners and walk the same list: what moved, what is stuck, who is unblocking it.

Stuck items get one action and one name. Stuck twice means the brief was weak, not the person, so send it back a stage.

Google's guidance on Google Ads best practices puts account structure and ongoing optimisation ahead of one-off setup. The rhythm, not the launch, does the work.

Monthly, review the workflow itself. Cut any stage that has not changed a decision in three months. Add one only when a real failure shows the gap.

How do you keep quality consistent across handovers?

Handovers are where quality leaks. Write one line per handover: what is passed, in what format, to whom.

Checklist for each handover:

Copy the one page workflow below and keep it where the team works:

SAAS marketing operating workflow, one page

Stage   | Owner              | Trigger          | Done when
Brief   | Demand lead        | Campaign request | Audience, offer, measure written
Build   | Channel specialist | Approved brief   | Assets match the brief
Review  | Marketing lead     | Build complete   | Approved or returned with comments
Publish | Channel specialist | Review approved  | Live and logged
Report  | Analyst            | Seven days live  | Numbers sent to the brief owner

Handover: what is passed, in what format, to whom
Rhythm: 30 minutes weekly, same list, five owners
Review: monthly, cut a stage that has not changed a decision in three months
Measure: average days from brief to publish

For the checks themselves, use a fixed list rather than personal judgement. Our SAAS marketing quality checklist sets out the recurring items worth testing before anything goes live.

How do you review and improve the workflow?

Review quarterly. Ask three questions: which stage caused the most delays, which handover caused the most rework, which rule was ignored most often. Each answer points to one change.

For paid social, skills gaps show up as weak targeting and copy. LinkedIn's advertising certifications cover B2B campaign set-up, a reasonable fix when review keeps returning the same faults.

Common questions

How long should the workflow be?

One page. One page is read; ten pages are filed. Anything longer is exceptions, so move those to an appendix.

Can one person own two stages?

Yes, in small teams, but write it down. Undeclared doubling-up is how approvals get skipped when that person is on leave.

How often should the workflow change?

Quarterly at most. One change per quarter, driven by a named delay or rework cause, keeps it honest.

What if a stage keeps stalling?

Check the brief before blaming the owner. Repeated stalls usually mean the input was unclear, so fix the previous stage first.