Newsletter Sponsor Ops

Build and manage the sponsor pipeline from prospecting through fulfillment handoff.

Core Rule

Use connected sponsor history, audience analytics, issue inventory, and recap history when available. Do not invent metrics, sponsor interest, pricing history, testimonials, or guaranteed performance.

Inputs

• Newsletter category, audience, geography or market
• Subscriber, open, click, reply, and source metrics if known
• Sponsor goal: first sponsor, recurring sponsors, package design, media kit, outreach, follow-up, renewal pipeline
• Available inventory: issue dates, placements, social add-ons, event/community add-ons, exclusivity rules
• Categories to include or exclude
• Existing rate card, media kit, sponsor list, or connected records if available

Workflow

1. Define sponsor fit by audience, category, timing, budget likelihood, trust risk, and offer relevance.
2. Review current sponsor assets: audience proof, packages, rate card, inventory, outreach, IO/payment process.
3. Build or improve the pipeline stages from prospect to renewal.
4. Create a qualified lead list or lead criteria if live prospecting is not requested.
5. Draft short outreach and follow-up that matches the sponsor type and newsletter category.
6. Add asset, approval, payment, fulfillment, and recap requirements.
7. Save or hand off sponsor records, pipeline status, outreach notes, and inventory notes for the connected workspace.

Output Format

When a reusable artifact is useful, follow templates/sponsor-pipeline.md.

Include:

• Sponsor strategy assumptions
• Sponsor-fit criteria
• Pipeline table
• Package or rate-card gaps
• Outreach and follow-up sequence
• Asset/payment/approval checklist
• Connected-workspace handoff notes

Pipeline table columns:

Lead table columns, when prospecting:

Guardrails

• Do not recommend sponsors that conflict with explicit exclusions or reader trust.
• Do not claim guaranteed clicks, conversions, sales, or ROI.
• Separate audience proof from speculative sponsor benefits.
• If pricing data is missing, present package options as hypotheses to test.
• Do not send outreach, sign IOs, collect payment, or publish sponsor copy without explicit approval.