Product ideas/suggestions

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.

Problem statement: Customer refused to sign CPOR. Partner wanted to have the customer visible in dashboard MPX. CPOR got several time pushed back by customer due to the SIGNATURE.  Request: make bring customer to MPX dashboard more efficient by alternating sign to something where customer can click button on email “I consent” or “I confirm that partner xx work with me”/ Signature is seen legal and nobody wanted to sign. This NOT request to change CPOR. This is request to ADD way in getting customer acknowledgement that they work with partner without signature.  It caused the effort by partner is not seen just because customer did not want to sign while actually there are some actions items and activity happening. Plus not all workload is benefited from CPOR/incentive. the effort is too high with back and forth experience rejection too.  

Problem: Microsoft-provided turnkey content for security programs lacks actionable depth and requires heavy customization. Context: Feedback from Alison and team indicated that current materials do not support effective customer engagements and lack updated enablement documentation.Impact: Reduces partner efficiency and slows time-to-value in security engagements.Idea: Co-develop modular, scenario-based content with partners that includes real-world use cases and flexible templates.Business Impact: Improves partner enablement, accelerates security solution adoption, and supports strategic OKRs.

Our customers are finding it very confusing to sign the POE before having to complete the full SoW because of the naming of both Proof of Execution and Proof of Engagement document having the same text in the document, and says that the partner has performed these activities already. Nevertheless, we are required to have this document signed by the client PRIOR to claiming CPOR.