Marketing: Workflows
How a topic becomes published material that compounds, and the handoffs with Sales, Support, Research and Legal.
Markdown. No sign-up, no email.
What arrives#
| From | What | Becomes |
|---|---|---|
| Support | The questions customers actually ask | The best content briefs available |
| Sales | Objections heard in calls | The second best, because an objection is a question with money attached |
| Research and Innovation | Findings, including negative ones | Material nobody else can publish |
| Delivery | What we actually did, with permission | Case studies that survive checking |
| Search and competitor analysis | Demand and gaps | The ranked list of what is worth writing |
| Legal | What may be said | Constraints, applied before drafting rather than after |
Support tickets and sales objections beat every analytics tool in this list. They are real questions, in real language, from people who have the problem. Search volume tells you what is typed; an objection tells you what is doubted.
What leaves#
| To | What |
|---|---|
| The site | Published material, dated, owned, with a review date |
| Sales | Content that answers common objections, so a seller can send rather than explain |
| Search | Pages that rank and keep ranking |
| The audience | Newsletter, and whatever we said we would send |
| Knowledge Management | What performed, what decayed, and why |
The path#
The third lane is the one most marketing functions never build, and it is where compounding actually happens. Publishing is a beginning; a page that still earns traffic in a year was maintained, not just written.
Handoff contracts#
From Support. A weekly export of the questions asked. No analysis required from them; the questions themselves are the input.
With Sales. Objections in, content out. A seller who can send a page instead of explaining for twenty minutes is the clearest evidence marketing is working.
With Research. Research output becomes authority content. This is the strongest material available because nobody else can publish it, and it is worth more than ten trend articles.
With Legal. Constraints arrive before drafting. Legal review as a final gate produces rewrites; legal input as a brief input produces publishable drafts.
With Delivery, on case studies. Nothing about a named customer exists publicly without their written permission, and nothing claims a result the delivery record does not support.
Cadence#
| Weekly | Support questions in, what published, what converted |
| Monthly | Rankings, qualified sessions, attribution |
| Quarterly | Decay review, thin-content share, positioning check |
The failure this design is built against#
A content calendar met every week, a domain growing in page count and shrinking in authority, and a team measured on publishing rather than on anything compounding.
The brake is the brief gate at the front and the decay review at the back. Both are unglamorous, both are the first things cut when the calendar gets tight, and both are the reason the rest works.