Content calendar built on audience questions

Plan a month of content around real customer questions and business goals, mapped to formats, channels and effort.

Change note: Initial version

Prompt

Build a {{weeks}}-week content calendar for the business below.

Business: {{business}}
Audience: {{audience}}
Business goal for this period: {{goal}}
Channels I can realistically run: {{channels}}
Weekly capacity (hours and who does the work): {{capacity}}
Questions customers actually ask or topics sales and support hear: {{questions}}
Existing content to reuse (optional): {{existing}}

Instructions
1. Start with 3-4 content themes derived from the questions and the goal. Explain in one line how each theme supports the goal.
2. Create the calendar as a table: week, channel, format, working title, audience question it answers, funnel stage (awareness, consideration, decision), primary call to action, estimated hours.
3. Respect my capacity. Do not schedule more hours than I have; if the ideas exceed capacity, show what you cut and why.
4. Reuse: for each flagship piece, list 2 smaller derivatives (for example a post, a short email or a chart) so effort compounds.
5. Define one success metric per piece and one review checkpoint at the halfway mark.

Rules: do not promise rankings or specific traffic. Prefer fewer, better pieces over a full grid. Titles should be specific and concrete, not generic ("5 tips for success").

Variables

• {{weeks}}Number of weeksnumber

  Default: 4

• {{business}}Businesstext

  Default: Plotline, project planning software for small design studios

• {{audience}}Audiencetext

  Default: Studio owners and project leads

• {{goal}}Goaltext

  Default: Increase free trial signups from organic search and email

• {{channels}}Channelstext

  Default: Blog, email newsletter, LinkedIn

• {{capacity}}Weekly capacitytext

  Default: 6 hours per week, one marketer plus occasional founder input

• {{questions}}Customer questionslong

  Default: How do I know if my team is overbooked? What should a kickoff meeting cover? Can I switch from spreadsheets without losing data? How do I estimate design projects?

• {{existing}}Existing contentlong

Example output

## Themes
1. **Workload visibility:** answers "am I overbooked", the core product problem, so supports trial signups.
2. **Project setup:** kickoffs and estimates, high search demand among our audience.
3. **Switching tools:** removes the migration objection late in the funnel.

## Calendar (6 h/week)
| Wk | Channel | Format | Working title | Question | Stage | CTA | Hrs |
|---|---|---|---|---|---|---|---|
| 1 | Blog | Guide | How to tell if your design team is overbooked (and what to do) | Am I overbooked? | Awareness | Start trial | 4 |
| 1 | LinkedIn | Post | Three signs of an overbooked week | same | Awareness | Read guide | 1 |
| 2 | Blog | Template post | A 60-minute project kickoff agenda | Kickoff coverage | Awareness | Download | 4 |
| 2 | Email | Newsletter | Kickoff agenda plus the overbooking guide | | Consideration | Read | 1.5 |
| 3 | Blog | How-to | Moving from spreadsheets to a project planner in an afternoon | Switching | Decision | Import sheet | 4 |
| 4 | Blog | Estimation guide | Estimating design projects without guessing | Estimating | Consideration | Start trial | 4 |

## Cut for capacity
A fifth post on pricing models and a webinar idea.

## Reuse and metrics
Each guide yields a LinkedIn post and a newsletter blurb. Metric per piece: trial starts from the page. Midpoint check at week 2: which piece drove clicks.

Notes

Tying each piece to a real customer question keeps the calendar useful and keeps you from filling slots with generic topics. The capacity rule makes the plan something you can actually deliver.