Product ideas/suggestions

General Observation:There is some perceived overlap and emerging competition between ChatGPT, Microsoft Copilot, and to a lesser extent, Google Gemini. However, the use cases and user experiences differ significantly.1. Adoption & Usage PatternsShadow AI:Many organizations see employees using ChatGPT privately or professionally (so-called “Shadow AI”). This happens regardless of corporate policy and can affect Copilot adoption rates.Organizational Deployment:Some organizations experiment with a company-wide version of ChatGPT or a “local” deployment. This group is smaller but visible.2. User Experience DifferencesChatGPT:Perceived as better tuned to users — feels more natural and intuitive.Users appreciate that ChatGPT remembers context and history, which makes workflows smoother.The textual output quality (especially rewritten or summarized texts) is often considered more elegant and better phrased.Copilot:Users find it less fluid, as it doesn’t remember context beyond the immediate prompt — each item must be provided manually.The integration with Microsoft data (e.g., Outlook, Teams, SharePoint) is seen as a huge advantage, but still developing.The RAI principles and enterprise data safeguards make the product feel more secure and compliant, which users appreciate for corporate environments.3. Competitive LandscapeGemini:Some awareness of Gemini rising as another player, but limited direct experience or impact so far.Overall Perception:Users view ChatGPT as stronger in language generation and “creative” use cases, while Copilot is recognized as more governed, secure, and enterprise-ready, though still maturing in flexibility and contextual understanding.4. Individual Remarks“ChatGPT is textually stronger; its rewritten outputs are more beautiful and refined.”“Copilot still needs to build up the same level of contextual memory that ChatGPT already has.”“Integration between ChatGPT and Microsoft data is accelerating — in principle, it could soon do the same as Copilot.”

Previously, partners had access to a dashboard during the EA Security information for CSI workshops. This allowed them to track when a customer was ready for Milestone 2 and estimate potential earnings to plan the next steps in the customer roadmap. However, since CSI has been integrated with MCI, partners no longer have visibility into when a customer becomes eligible for Milestone 2.The guide needs to be updated to clarify what the trigger is whether it’s the customer’s signature, the assignment of licenses, or another event, especially since there can sometimes be a buffer period. Understanding this trigger is critical for partners to prepare the roadmap and avoid delays in moving to the next steps.