- Industry
- IT Company
- Department
- Content
- Team
- Content Planning
- Kind
- Decision-maker
- Approver
- Content Lead
- Code
- CON-08
It sets the content topics for the next quarter from buyer demand: search interest in cloud, data and software topics, pre-sales questions logged in the CRM, recurring support tickets on the SaaS products and gaps in the library against the services the company sells. It proposes a ranked topic plan that fits writer and subject-matter-expert capacity and, once approved, creates the topics as planning items.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the CRM: pre-sales questions, lost-deal reasons and open opportunities by practice for the last two quarters..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Content Lead with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the project management tool: it creates the approved topics as planning items for the quarter. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The content strategy: the practices and SaaS products to grow, target industries and personas, the existing library by topic, subject-matter experts and their availability, and topics the company will not cover.
Reads from
the CRM: pre-sales questions, lost-deal reasons and open opportunities by practice for the last two quarters.
Acts in
the project management tool: it creates the approved topics as planning items for the quarter.
Hands back
A list of topics in rank order, each with topic, practice, persona, demand_score, demand_origins (a list), format, sme (or null), sme_hours and reason.
Asks a person when
The plan needs more than 6 subject-matter-expert hours on a topic, drops a business priority, or exceeds capacity.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Most topics per quarter | 10 | The plan holds at most this many topics. |
| Least independent demand signals | 2 | A topic needs demand from at least this many different origins to be planned. |
| Weight on pre-sales and lost-deal signals (%) | 40 | How much pre-sales questions and lost-deal reasons count in the ranking, against search and support signals. |
| Most subject-matter-expert hours per topic | 6 | A topic needing more billable-engineer time than this needs the approver, since it costs utilisation. |
| Topics it never plans | unannounced products, client incidents, politics, pricing comparisons | Comma-separated topics left out of every plan. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Plan at most 10 topics and no more than the team's capacity in pieces.
- Plan a topic only when it has demand from at least 2 different origins.
- Weight pre-sales questions and lost-deal reasons at 40 percent of the ranking, so topics that help win deals rise.
- A topic needing more than 6 hours of a billable engineer's time needs the Content Lead, because it takes them off client work.
- Never plan a topic in unannounced products, client incidents, politics, pricing comparisons.
- Every business priority gets at least one topic, or the plan says why not.
See the Content Strategy Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.