Profile
Writing is not the problem. Deciding what to write about, and why, is.
The Content Briefer looks at the questions people ask, what you already have and where the gaps are.
The result is a brief: the topic, the questions to answer and how it connects to what is already there. The writing itself stays with a person.
What it does, step by step
- Gather questionsFrom search data, support tickets and what sales hears back.
- Audit existing contentWhat is already there, and does it really answer the question.
- Find the gapsQuestions without an answer, and pages that overlap.
- Write the briefTopic, audience, the questions to answer and the internal links.
- PrioritiseBy volume and by how close the question is to a buying decision.
Works with these systems
SharePoint
Confluence- Help centre
- APIs
- Databases
Zendesk- Freshdesk
Is your system not listed? We can connect any system, even if there is no standard integration. View all integrations.
What runs automatically and what does not
You stay in control.
Not every decision should be made automatically. For each workflow, we set out:
- What can happen automatically.
- What is put forward for approval first.
- When a person is brought in.
- What information is stored.
- How actions are logged.
Is this a fit for your organisation?
A good fit if
- Organisations that produce content as a matter of routine.
- Businesses with lots of existing pages and no overview.
- Situations where content is made on gut feeling.
Less of a fit if
- The writing itself: generated copy is exactly what you do not want to publish.
- Brand stories and opinion pieces.
What it can deliver
- Content that matches questions people actually ask.
- Fewer pages that overlap.
- A reasoned order of work instead of a wish list.
Directions, not promises. As soon as there is evidence from a client project, it will appear here as a substantiated result.
Frequently asked questions
Does this AI employee write the copy?
No, and that is a deliberate choice. Generated marketing copy is easy to spot and rarely produces anything you want to publish. It decides what needs writing and which questions need answering. The writing stays human work.
Where does it get the questions from?
From search data, from your own support tickets and from what sales hears back. The last two are usually more valuable than search volume alone, because they come from real conversations.
Can it see which pages compete with each other?
Yes. Several pages aimed at the same question compete with each other. It flags that, with a proposal to merge them or tell them apart.
Does this also help with visibility in AI answers?
It helps, because language models reward the same things a good reader does: a clear question with a concrete answer and a traceable source. A brief built around that works for both.
How to put this to work
- 1A short callTogether we look at your process and your systems, and whether this task is the best place to start.
- 2Set up on your rulesIntegrations with your own systems, and agreeing what may run automatically and what a person approves.
- 3Measure and adjustFirst alongside your team, only then on its own. We look at what it delivers and adjust.