Overview
A lightweight campaign planning SOP for SaaS teams, covering stages, roles, notes, review rhythm, and workspace ownership. It turns the campaign planning workflow into a repeatable operating habit without forcing SaaS teams into a heavyweight process.
Page-specific fit
Why this resource exists
SOP audience: SaaS founders, product marketers, customer success leads, and operators.
Workflow object: campaign execution.
Operating cadence: weekly product-ops review plus launch-specific readiness checks.
Trust signal: release readiness, feedback follow-up, support handoff quality, stale launch work, and customer-facing blockers.
Purpose of the SOP
This SOP exists to make campaign planning work repeatable for SaaS teams. The goal is not to document everything. The goal is to reduce the specific failure mode where strategy, creative, channel operations, deadlines, and post-campaign reporting are planned in separate surfaces.
The SOP should help a teammate understand what stage the work is in, who owns the next move, which note explains the context, and when the next review happens.
Roles and ownership
The workspace needs to preserve product decisions, customer evidence, launch tasks, and internal ownership without spreading them across a tool stack. That means every SOP needs clear role boundaries without creating a governance layer nobody wants to maintain.
Use one accountable owner for each active item. Collaborators can contribute, but the workflow should never depend on a vague group owner.
- Workflow owner: maintains stages and review rhythm.
- Card owner: owns the next action and status accuracy.
- Reviewer: approves or requests changes by a visible date.
- Context owner: keeps notes, decisions, and references current.
Procedure
Start with Strategy, Creative, Build, Review, Launch, Report. These stages are enough to describe the work without turning the board into an admin project.
The SOP should state what must be true before work enters each stage and what must be true before it leaves. If the rule cannot be explained in one sentence, simplify it.
- Strategy: define the owner, input, output, and review signal for this stage.
- Creative: define the owner, input, output, and review signal for this stage.
- Build: define the owner, input, output, and review signal for this stage.
- Review: define the owner, input, output, and review signal for this stage.
- Launch: define the owner, input, output, and review signal for this stage.
- Report: define the owner, input, output, and review signal for this stage.
Workspace setup
In Kanvly, the board handles movement and the note layer handles durable context. Audience, message, channel, asset owner, launch date, measurement, and learning need to stay connected.
For SaaS teams, this is especially useful because release context, customer feedback, enablement work, support follow-up, and recurring operations move together. The SOP should tell people where to update status, where to write context, and where to review blockers.
Review and improvement
Review the SOP during weekly product-ops review plus launch-specific readiness checks. Use the review to inspect stale work, owner gaps, blocked items, and repeated exceptions.
Measure release readiness, feedback follow-up, support handoff quality, stale launch work, and customer-facing blockers. If the SOP reduces those issues, keep it. If it creates extra admin without better decisions, shorten it.
- Name the workflow owner.
- Define stage entry and exit rules.
- Clarify one owner per active item.
- Link the notes that explain decisions.
- Set a review cadence and improvement rule.