Marketing OS
Approval and publishing controls
The boundaries that keep public marketing work attributable, consent-aware, on-brand, and subject to named human release authority.
Derived from the Project Marlow service brief and public operating model. Customer scope, enabled channels, connected tools, approval owners, and cadence are agreed per engagement.
What requires approval
Public posts, prospect-facing messages, spend outside agreed caps, and new commitments require a named human approval. Approved work is treated as immutable until a new review is requested.
Verification before release
A pre-ship check reviews factual support, recency, brand voice, visual quality, confidentiality, audience fit, and channel readiness before a release package reaches the human approver.
Consent and contact boundaries
Marketing activity uses agreed business channels and recorded permission. The operating model does not add people to mailing lists without consent or treat personal addresses as a marketing channel.
Proof of action
Material sends and approvals are recorded with their context, owner, timing, and outcome. The record makes it possible to distinguish a proposed item, an approved item, and something that actually shipped.
Marketing OS
Move from the guide to a discovery conversation
Review the public Marketing OS page for the executive overview, then bring one accountable outcome, audience, channel, and approval owner to the discovery conversation.