M-Files × Microsoft 365 Launch
A first-of-its-kind integration needed one story Product, Sales and Content could all sell. I built it on trusted AI content, unified compliance and return on existing Microsoft 365 spend.
Company:
M-Files
expertise:
GTM Strategy, Product Launch
My Role:
Launch Strategy & Sales Enablement
One partnership, four buyers, and one story every team could sell.
In July 2025, M-Files became the first document management system to store content natively inside Microsoft 365. Built on SharePoint Embedded, the integration connected M-Files’ AI-curated content to Microsoft 365 Copilot, Microsoft Purview and native co-authoring. The risk was that it would launch as a feature list. Product was focused on the storage architecture, Sales needed a reason for customers to act, and customers already invested in Microsoft 365 needed to understand how this worked alongside what they had, not instead of it.
I owned the go-to-market strategy for the launch. My job was to turn the Storage and Copilot roadmap into a commercial story, bring internal teams and Microsoft into alignment behind it, and build the launch plan and assets that carried it to market.
How I built the launch plan
I treated the launch as an alignment problem first and a content problem second. The assets were only as strong as the agreement behind them, so the plan started with people, then buyers, then the story, and only then the content.
Start with the stakeholders, not the assets
I ran working sessions with Product, Sales, Customer Success, Partnerships and Content to understand what each team needed the launch to do. Product needed the architecture explained accurately. Sales needed a reason to open a conversation. Customer Success needed a way to bring existing accounts onto the integration. Externally, I worked with Microsoft so the joint story held up from both sides of the partnership and a Microsoft voice could validate it in front of customers. Getting these needs on the table early meant the plan served every team, rather than asking them to adapt to it afterwards.
Map the buyers before writing a word
This was never a single-buyer launch. An integration like this touches the person who signs off on spend, the team that owns security, the people who work in documents every day and the people who automate processes. I mapped each persona to the question they would ask and the message that answered it (see the persona table below).
Persona | Their question |
|---|---|
Executive / economic buyer | Is our Microsoft 365 investment paying off? |
Enterprise IT, security & compliance | Can we scale AI and collaboration without adding risk? |
Business users and knowledge workers | Will this change how I work? |
Citizen developers | Can I build on top of it? |
Sequence the launch so each asset has one job
I planned the rollout to move each audience from awareness to understanding, to proof, to action. Every asset had a defined audience and a defined job, so nothing was created just to fill a channel.
Stage | Audience | Asset and its job |
|---|---|---|
1. Announce | Market, customers, partners | Launch announcement: M-Files and Microsoft announce strategic partnership. Set out the first-of-its-kind positioning and the three value pillars in one public story. |
2. Explain | All four personas | Partnership hub: M-Files & Microsoft 365. One home for the full story, with benefits broken out for IT, business users and citizen developers, plus availability and requirements. |
3. Prove | Business users and IT | Demo videos: Native co-authoring in M-Files Turned the most tangible everyday benefit into its own page, showing real-time collaboration, Copilot access and requirements. |
4. Validate | Enterprise decision makers | Webinar: M-Files & Microsoft 365, The Perfect Match. A joint session with speakers from M-Files and Microsoft, covering the business case, a live demo and open Q&A. |
5. Enable | Sales and Customer Success | Asset library: Executive narratives and a shared launch content So Sales and CS told the same story in enterprise and mid-market conversations. |
What the launch delivered
70%+ of launch content used in live sales cycles
12% of customers onboarded the integration
34 Essentials-to-Enterprise tier upgrades
5 enterprise accounts retained from churn risk within one month
A partnership launch has two audiences before it has any buyers: the teams inside your company and the partner on the other side. Getting both aligned on one story first is what made every asset easier to build, and easier to sell.
Amelia owned the full spectrum of customer marketing from go-to-market planning for new product launches to integrated B2B SaaS campaigns spanning email, web, social, paid media, and webinars. Her campaigns weren’t just creative; they were built on solid measurement frameworks, and she consistently used data to sharpen performance.
Sirpa Levola
Director, Customer Lifecycle Communications, M-Files
Related Projects
