A three-person marketing team cannot run a twelve-stage workflow designed for a newsroom. They also cannot run on improvisation forever. Missed interviews, week-long review loops, and orphan drafts are ops failures, not writer personality problems. The fix is a light system that makes constraints visible.
Ops is not bureaucracy for its own sake. It is how you prevent strategy from dying in Slack threads. If you still need the strategy artefacts themselves, start with what a B2B content strategy actually contains, then use the model below to execute it.
Define roles even when one person wears three hats
Name the functions even if the same human performs them on different days: intake owner, brief owner, writer/editor, SME coordinator, publisher, measurement owner. When roles blur without names, every task waits on the same overloaded person and nothing has a backup path.
- Intake owner: accepts or rejects requests against strategy.
- SME coordinator: books interviews and tracks promises.
- Editor: protects argument quality and claim accuracy.
- Publisher: handles CMS, internal links, and metadata.
- Measurement owner: updates the priority URL scoreboard.
Intake rules that stop random acts of content
Create a single intake form: requester, audience role, business job, deadline reality, SME needed, and success signal. Reject politely when the request is off-strategy or lacks an owner for review. Random executive ideas can still enter, but they must pass the same gate as everyone else.
| Work type | Typical monthly share | Why it exists | Hard constraint |
|---|---|---|---|
| Net-new evaluation or proof assets | 30 to 40% | Closest to pipeline jobs | Needs product/sales truth |
| Strategic educational / POV | 20 to 30% | Category narrative and early research | Needs SME or executive access |
| Refresh and consolidation | 20 to 30% | Stops library decay | Needs decision authority to prune |
| Distribution and enablement packaging | 10 to 20% | Gets assets into deals and channels | Needs sales feedback loop |
Percentages are guides, not dogma. A quarter spent mostly on audit and refresh can be correct after years of unchecked publishing. A launch quarter may tilt toward evaluation pages. The point is that net-new blog volume is not the default remainder of the calendar.
SME gates and interview logistics
No brief enters production without a named SME and a booked input method. That method can be a live interview, async answers, or a working session with product marketing. If the booking does not exist, the card stays in ready. This single rule prevents the most expensive failure mode: writing from public material and hoping review will invent the experience later.
- Confirm SME and schedule before assigning a writer.
- Send prompts early; keep sessions under 45 minutes.
- Capture recording and thesis confirmation the same day.
- Limit review rounds; escalate blockers on day three of silence.
- Credit SMEs internally when pieces perform in deals.
For leadership access specifically, use the playbook in getting executives to do interviews. Ops cannot invent willingness, but it can stop wasting cycles on phantom bylines.
Tooling that fits a small team
You need a source of truth for the backlog (Notion, Asana, Linear, or similar), a brief template, a CMS checklist, and a simple dashboard for priority URLs. You do not need five overlapping AI drafting tools and a digital asset manager with no owner. Prefer boring tools your team will update weekly.
AI can help with outline pressure-testing, summarising interviews (with human verification), and editing passes. It should not become an undisclosed draft factory. Technical claims still need SMEs. That boundary keeps ops honest when speed pressure rises.
The weekly ritual
Run a thirty-minute weekly ops meeting: blockers, interviews this week, pages stuck in review, refresh candidates, and one measurement highlight. Keep it operational. Strategy debates belong in a monthly or quarterly session, not in every stand-up.
Refresh queues are first-class work
Create a standing refresh list from analytics decay, sales complaints, and product changes. Assign owners. Celebrate republishing the same way you celebrate net-new URLs. Without this, the library becomes the silent tax described in how to audit a B2B content library.
When capacity is tight, prune more aggressively. A small team cannot maintain an infinite archive. Consolidation is an ops victory.
Document definition of done for every format. A blog post is not done at draft. It is done when claims are checked, internal links are placed, metadata is complete, the CMS preview was reviewed, and distribution tasks are assigned. A case study is not done at web publish. It is done when the one-pager exists, CRM tags are set, and sales was shown where to find it. Clear done states stop half-finished work from clogging the board.
When something slips, record the reason in public: SME cancelled, legal hold, brief incomplete, strategic kill. Patterns in those reasons tell you whether you have a writing problem or a company access problem. Ops exists to surface that distinction early enough to change the quarterly plan.
Working with agencies and freelancers without losing the system
External writers and agencies can extend capacity, but they cannot own your intake rules or SME relationships unless you give them that mandate. Hand them briefs that inherit strategy. Keep approval SLAs explicit. Decide who updates the CMS and who reports measurement. For the resourcing decision itself, see in-house vs agency vs freelancers.
If your ops system only works when nobody takes vacation, you do not have a system. You have heroics with a kanban skin.
Small-team ops succeeds when the calendar tells the truth about capacity, interviews are booked before drafting, refreshes are scheduled, and measurement looks at priority URLs rather than post count. That is enough structure to compound. More structure usually becomes avoidance.