The problem
A global technology company's enterprise collaboration platform was creating a new category in workplace software. That meant the usual playbook didn't apply. The buyers who needed the product weren't necessarily searching for it by name, because nobody knew this thing existed yet.
The blog needed to do two jobs at once: attract people who were searching for broader workplace challenges, then connect those challenges credibly to what the platform helped teams achieve. Get the first part right and the second part wrong, and you've built a content engine that drives traffic with no commercial value. Get both right, and you've built a genuine acquisition channel.
What I did
Built the blog from scratch using SEO research, audience insight and product storytelling, rather than starting with what the product team wanted to say.
- Structured the strategy around eight product-relevant content pillars, including collaboration, productivity and the future of work
- Built supporting content clusters underneath those pillars with over 300 peieces of content. Each laddering from a recognisable workplace question up to the platform's bigger proposition
- Connected every high-performing piece of content to relevant offers and nurture journeys, so traffic became identifiable commercial interest rather than vanity metrics
- Kept the throughline consistent: helping teams communicate, collaborate and work more effectively, regardless of which specific pillar a piece of content sat under
What changed
The blog became a sustained inbound engine rather than a standalone editorial channel. It generated significant organic traffic on its own terms, but the more important shift was structural: content wasn't competing with paid channels for attention, it was feeding them, with more than £2m in attributed pipeline over the life of the programme.
The 347-cluster structure also meant the content programme kept compounding. New pieces didn't start from zero. They slotted into an existing architecture that was already earning trust and traffic, which is a large part of why the pipeline number kept growing rather than plateauing after the initial build.