This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Community Hub.
By Srini Raghavan, Vice President, Microsoft Teams Ecosystem
This is part five in a series of blogs where I'm sharing examples of how partners are innovating with Microsoft Copilot.
Microsoft Copilot has been generally available to enterprise customers for less than a year, and many independent software vendors (ISVs) are already discovering ways to use it to transform their business and enhance their offerings to customers. It’s thrilling to see such rapid progress from our partners.
At Microsoft, we share in the sense of excitement about advancing the potential of AI. But, as with any new tool, it’s crucial to plot the best path forward rather than simply adopting it to keep pace with industry trends. I recently spoke with a leader of one ISV in France who put it succinctly: Don’t build AI for the sake of AI. You must do it strategically and with intention.
It’s helpful advice, and it comes from Nicolas Humann, CEO, and co-founder of Witivio, a maker of apps and bots that improve employee experiences across HR, IT, internal communications, and more. Witivio has often served as an advisor to other French ISVs looking to integrate with Microsoft Teams. The company recently released their first Copilot extension, and they provided great insight for Microsoft partners looking to extend Copilot.
In this post, I’ll share Witivio’s experience, their guidance about what other developers can focus on during development, and their thoughts on getting the most out of Copilot.