Plan a Quarter of Content Your Sales Pipeline Can Feel
Turn one goal, three customer problems and your real weekly capacity into a 13-week content plan — monthly themes, repurposing paths, distribution steps and kill criteria.
When to use it: When your software or B2B service business publishes sporadically and you want a quarter mapped out that answers objections and feeds the pipeline, not a random blog calendar.
You are a content strategist for a business-software company selling to Australian businesses. You plan content that sales can use, and you cap plans at what the team can actually produce.
<context>
Product and who buys it: [PRODUCT — e.g. rostering software; buyers are operations managers in aged care]
The quarter's business goal: [GOAL — e.g. 30 demo bookings from organic and email]
The three customer problems we solve best: [PROBLEMS — e.g. compliance evidence takes days; last-minute shift gaps; agency cost blowouts]
Proof we hold: [PROOF — e.g. two written case studies, product screenshots, a 2025 customer survey]
Objections sales hears most: [OBJECTIONS — e.g. 'we already use spreadsheets and it's fine'; 'switching is risky mid-contract']
Channels and real capacity: [CAPACITY — e.g. blog + LinkedIn + monthly email; one marketer 2 days/week]
</context>
Before planning, assign each month of the quarter ONE theme drawn from my three problems, ordered so the quarter builds toward my goal — and state the logic in two lines.
<task>
1. A 13-week table: week | pillar piece (working title + format) | funnel stage (problem-aware / comparing / ready) | channel | repurpose cutdowns (each pillar becomes at least three smaller pieces) | the distribution step, because publishing is not distribution (e.g. send to segment X, post with a question, sales shares with 5 open opportunities).
2. At least three pieces across the quarter that answer my stated sales objections head-on — mark them.
3. Every piece must be feasible inside my stated capacity; show the weekly hours estimate and leave 20% slack for reactive content. If my goal needs more than my capacity produces, say so and show what to cut first.
4. Proof placement: where each of my listed proof assets gets used — case studies and survey data slot into specific weeks; no piece may rely on proof I don't hold, and any stat slot becomes [NEEDED: source].
5. Measurement per funnel stage — leading indicators for weeks 1-6 (qualified traffic, replies, saves), lagging for the quarter (demos influenced) — and the fortnightly 15-minute review ritual.
6. Kill criteria: the mid-quarter signals that justify dropping a theme or format, and what replaces the freed capacity.
7. Weeks 1 and 2 in full detail: titles, outlines (3-5 bullets each), and the distribution checklist per piece.
</task>
<output_format>Theme logic; the 13-week table; capacity maths; measurement; kill criteria; weeks 1-2 detail.</output_format>
Rules: use only my product facts and proof; no invented statistics, customer names or benchmark claims.
Copy the block above straight into Claude — anything in [BRACKETS] is yours to fill in.
Want it tuned to your business? Bring it to the free weekly call and we'll adapt it live.
Join the free callMore au business & compliance prompts
Plain-English Contract Summariser
Understand what you're signing before you sign it — and know what to ask a professional
Set Up Redirects and Caching on an Apache Site
Get a ready-to-paste .htaccess block with redirects, HTTPS forcing and caching, plus install, test and undo steps.
Script a Hard Conversation Before You Have It
Turn a dreaded workplace conversation into a short, direct script with openers, key lines and responses to likely reactions.