Chip Stein

One of the distributors that is integrating ASPX with the APIs has suggested that along with the Teir 2 reseller name that we should include the Partner ID or the tier 2 reseller MPN ID in the feed. This will help with their integration into their internal tools and marketplaces.

Its becoming more apparent that in many cases the purview and Copilot conversations are intertwined. Is there a way to identify the tenants that have whitespace opportunities that overlap in those to workloads? Otherwise downloading and running an agent may be the solution??

During a joint alignment call with Ingram Micro’s MCSA team, several key themes emerged regarding Copilot adoption, the transition from Chat to Paid Copilot, and competitive pressures. Discussion included Copilot Business vs. Paid Copilot positioning, partner enablement gaps, and the need for clearer GTM and enablement motions for distributors.🔹 FeedbackPartners express ongoing confusion between:Copilot for Microsoft 365 (paid)Copilot ChatCopilot for BusinessThey perceive “fine print” and functionality differences that are not yet well understood.Repeated partner trainings are not sticking, especially for Copilot Business.High repetition needed for messaging to land.Distributors report that their current Copilot offerings are basic and not competitive, especially around:Pre‑sales motionsAdoption planningCustomer ROI guidancePartners acknowledge customer excitement for AI but say customers lack clarity on HOW to start. 🔹 Challenges1. Transition from Copilot Chat → Paid Copilot is weakIngram sees high Copilot Chat interest but very low conversion to paid seats.Partners say customers love experimenting with various AI tools (Gemini, GPT, Copilot), but interest does not translate to purchase.2. Copilot Business confusion slows momentumPartners report mixed messaging, confusion about feature differences, and concerns that Copilot Business is “limited.”3. Competitor: Gemini entering aggressivelyIn Mexico, Gemini is undercutting pricing by 20%, including bundles.Competitor offers are easy for customers to compare, contributing to deal friction.4. Distributor Copilot offerings are not matureMany are selling Copilot as a license-only motion.Need stronger:Pre-sales frameworksAdoption servicesDeployment playbooksROI conversation guides5. ROI is unclear for final customersCustomers know they “need AI” but don’t know:What business outcomes to targetHow to operationalize adoptionWhat the implementation path looks like6. Distributor operational constraintsIngram Mexico and others operate as multiple independent country organizations, forcing partner managers to treat them as multiple separate distributors.Nexsys is significantly behind in innovation and cloud-readiness.

It would be great to be able to filter on the Tier 2 reseller name in the ASPX UI

Distributors have customers assigned to resellers via CSP licensing and sometimes those customers also have EA agreements. The Copilot Whitespace is based on all licenses to that customer regardless of purchasing vehicle. It is requested that when we filter it based on CSP, that the whitespace totals also adjust. The tier 2 reseller feels that that may not have an opportunity to fill all of the whitespace associated with the customer as they cannot have an effect on the EA licenses. being able to filter the whitespace based on vehicle will give the tier 2 reseller a true view of their opportunity.