Marketing Content Engine
No content team and no shared knowledge base, so publishing was sporadic and the voice changed from piece to piece. We built a weekly cycle that produces 13+ content formats from one knowledge base.
The problem
No dedicated content team. Planning and writing took a disproportionate amount of time every week, quality depended on who was free, and every piece started from nothing. Publishing was sporadic and the voice changed from piece to piece.
What we built
A production system that generates 13+ formats from a single knowledge base: LinkedIn posts, blog articles, newsletters, case narratives, competitor audits, weekly industry scans, carousel posts, thread series, one-pagers, content calendars, event content, social reactions and content repurposing.
The weekly cycle:
- Automated monitoring collects relevant news and developments
- A prioritised digest goes to the team for review
- Approved topics run through the matching content skill
- A person reviews every draft before it is published
Stack: n8n · Claude · web scraping · Google Sheets · email
What changed
Planning became a two-hour job instead of two full days, and it runs the same way every week regardless of who is doing it. Update the knowledge base once and every format is written from the updated version.