Role: Marketing Manager (fully remote, March 2023 – April 2024), working with leadership, product, and sales.
<aside>
The challenge: an engineering-led company describing a complex data product in technical terms, while its offer was still evolving.
What I did: moved the messaging toward customer problems, simplified the website, turned customer work into clear proof, and gave LinkedIn a consistent identity.
What changed: a clearer, smaller site and a story that showed what Mammoth helped people do.
</aside>
Mammoth Analytics is a B2B data and analytics platform with enterprise customers across different industries.
When I joined, the company was very product-led. Engineering had a strong influence on how Mammoth talked about itself, so the story often started with what the platform could do rather than why someone would want to use it.
At the same time, the offer was still evolving. Mammoth could be sold as a self-serve product, a managed service or something in between, and packaging and pricing were still open questions.
Most of the work came back to the same question: how do we explain Mammoth from the customer’s point of view instead of the product’s?
Before: the homepage spoke to engineers.
Mammoth could do a lot. That was part of the problem.
Internally, it was easy to talk about integrations, pipelines, automation, dashboards and technical capabilities. From the outside, that made it hard to see quickly what Mammoth was actually useful for.
Before: a menu built around everything the product could do.
I worked on moving the story closer to the problems customers already understood. Messy data. Hours spent preparing reports. Manual processes. Information scattered across different systems. Teams spending more time organizing data than using it.
That thinking shaped the website, landing pages, content and sales materials.
This took some convincing, partly because the company was still deciding whether to sell Mammoth as a product or a service. Support from the sales team helped make it possible to try something new.
The website was where those questions became tangible. I led the migration from Webflow to WordPress and worked on the structure, messaging and content, alongside a designer, a copywriter and a web developer.
One of the biggest changes was reducing the amount of information. The previous site reflected the complexity of the product, so we moved to a smaller, clearer structure where each page had one clear job. Instead of asking visitors to understand the technology first, the site showed what Mammoth helped people do.
