How to co-sell with Microsoft using MCEM: The ISV's complete guide

TL;DR

• Microsoft Customer Engagement Methodology (MCEM) for partners is the five-stage framework Microsoft uses to structure co-sell engagements between ISVs and its field sellers, from discovery through post-sale expansion.

• The five stages: Listen and Consult, Inspire and Design, Empower and Achieve, Realize Value, Manage and Optimize. The first four align with Partner Center's opportunity lifecycle through Won status; Stage 5 covers post-sale relationship management and can initiate a new customer decision cycle.

• Microsoft's marketplace-first co-sell model now recognizes co-sell credit through Marketplace Billed Sales, which means your marketplace transaction readiness directly affects how you execute MCEM Stages 3 through 5.

• SaaSify brings co-selling across Microsoft, AWS, and Google Cloud into a common CRM environment with AI-assisted opportunity enrichment, configurable workflows, and consolidated reporting.

Microsoft Customer Engagement Methodology (MCEM) for partners is a five-stage framework that gives ISVs and Microsoft's field sellers a shared set of deal stages and deliverables for co-selling customer opportunities together. Partner Center has its own deal stages that correspond to MCEM stages, though Microsoft explicitly allows partners to use different internal sales stages while maintaining alignment through the shared framework. The result is that both sides can track the same deal milestones without requiring the ISV to abandon its own sales methodology.

• Shared context with Microsoft sellers: MCEM helps both teams maintain deal context as the opportunity progresses, even when they use different internal sales processes.

• Referral quality and visibility: A referral structured around MCEM stages is easier for a Microsoft seller to evaluate than one using only the ISV's internal terminology.

• Internal consistency: Shared stages make co-sell results coachable and measurable across your team, instead of every AE running the motion differently.

• Cyclical expansion: It also helps identify renewal and expansion opportunities that can initiate a new MCEM cycle, beginning with Listen and Consult.

Stage 1: Listen and consult

Discovery and qualification: The ISV and Microsoft account team research the customer's business objectives and Azure consumption patterns to determine whether the opportunity warrants Microsoft seller engagement.

• Research the customer's Azure consumption and whether they have committed cloud spend through a MACC agreement before the first meeting.

• Build the referral around the customer's business requirement, the proposed solution, the expected deal value, and the specific support you need from Microsoft.

• Microsoft validates referral quality at submission against five inputs: Solution area or play, deal value, expected close date, customer need, and customer contact or consent.

• API-based referrals require additional fields, including the mandatory Marketplace Intent field (three accepted values: Yes, No, and Have not decided), required on IP co-sell referral API submissions.

Required output: A Qualified Opportunity created in Partner Center and shared with Microsoft sellers.

Stage 2: Inspire and design

Joint solution architecture: The ISV and Microsoft team design a solution together and present it as a unified offering, with co-branded collateral mapped to Azure consumption. For ISVs with Azure IP Co-sell Eligible solutions, Microsoft field sellers receive incentives tied to co-sell deals, which means framing your solution around Azure consumption directly affects seller motivation.

• Create joint collateral mapped to the customer's Azure estate and consumption patterns.

• Keep the Partner Center referral updated as the opportunity progresses so the Microsoft account team is working with accurate deal information.

• Confirm that the referral's deal type reflects the level of Microsoft seller involvement needed. Update it if the engagement changes.

Required output: A joint solution design presented to the customer and a Partner Center opportunity reflecting the current deal stage.

Stage 3: Empower and achieve

Proof of concept and commitment: Depending on customer requirements, the joint team may use a proof of concept, pilot, or demonstration to validate the solution. This stage ends when the customer commits and deal terms are locked.

• Have your marketplace transaction infrastructure production-ready before the customer commits. Under the marketplace-first model, marketplace transactions are the primary mechanism for co-sell credit recognition. Waiting until after verbal commitment to set up your listing, metering, or private offer creation introduces risk.

• For deals involving channel partners, multiparty private offers (MPOs) are available across 36+ markets. ISVs managing custom contract lengths and renewals should have these configured in parallel with the proof of concept.

Required output: Customer agreement signed, with the Marketplace transaction ready for execution.

Stage 4: Realize value

Implementation and value delivery: In Partner Center, an opportunity can be marked Won once the customer has executed the agreement and deployment can begin. A deal marked Won means the agreement is in place, but the customer may not yet be operational.

• Align with the customer and the Microsoft account team on implementation responsibilities and adoption milestones.

• Define measurable success criteria before go-live so there is a shared understanding of what "operational" means.

• Track usage metrics from the start. Adoption data is what makes Stage 5 expansion conversations substantive.

Required output: Successful implementation with customer satisfaction and agreed outcomes with metrics in place.

Stage 5: Manage and optimize

Post-sale engagement and expansion: By the midpoint of a contract, the customer has real usage data, a working relationship with both teams, and a reason to expand if the engagement has delivered.

• Identify expansion opportunities early, while the customer's satisfaction is measurable and the Microsoft account team is still engaged.

• Coordinate post-sale responsibilities: Who monitors adoption, who initiates the renewal conversation, and how usage signals reach your sales team.

• Marketplace-transacted expansions contribute to your co-sell track record under the marketplace-first model.

Required output: Proactive expansion or renewal conversation initiated, with qualified opportunities feeding into a new MCEM cycle at Stage 1.

The deal type you select when creating a referral in Partner Center shapes your MCEM execution from Stage 1 onward. It determines whether Microsoft sellers actively engage with your opportunity, whether the deal earns co-sell credit, and whether it builds the track record that influences how sellers prioritize your future referrals:

• Co-sell with Microsoft sellers: You request active help from the field team, and the seller has 14 days to accept. Submit complete referral data that explains the customer need and where Microsoft’s involvement adds value.

• Partner-led: You work the deal yourself, but it is visible to Microsoft sellers and eligible for co-sell credit.

• Private deal: Hidden from Microsoft sellers until you share it. No co-sell credit until you upgrade the deal type.

• Partner-to-partner (P2P): Collaboration with other Microsoft ecosystem partners, often connected to multiparty private offers.

Partner-led and co-sell deals can qualify for Azure IP co-sell deal registration when they meet Microsoft’s eligibility criteria. Private deals must first be upgraded to an eligible type. Consistent referral reporting through these deal types also helps Microsoft understand your pipeline and contributes to seller engagement over time.

Deal registration itself is a separate process with its own criteria: The opportunity must be marked Won in Partner Center, involve an Azure IP co-sell eligible solution, meet a minimum deal value of $25,000 with a Microsoft-managed customer account, and include a contract that identifies both the ISV and the eligible solution. For co-sell deals, Microsoft seller acceptance is required where applicable. On timing: Allow 72 hours between referral creation and marking the deal won, and register within 60 days of contract signing.

Microsoft's marketplace-first co-sell model recognizes co-sell credit through Marketplace Billed Sales (MBS), replacing the broad use of PRACR (Partner Reported Azure Consumed Revenue). Under PRACR, ISVs reported their own Azure consumed revenue and waited for validation. Under MBS, Microsoft uses Marketplace transactions as its primary recognition mechanism, subject to the applicable program requirements.

This directly changes how ISVs execute MCEM:

• Stage 3 readiness: Your marketplace infrastructure needs to be production-ready before deals reach the commitment stage. Under PRACR, ISVs could close deals off-marketplace and self-report the revenue afterward. That route is no longer the standard mechanism.

• Stage 5 compounding: Renewals and expansions that transact through the marketplace contribute to your co-sell track record, making post-sale engagement more consequential for long-term co-sell momentum.

• Co-sell status tiers: Co-sell Ready is the baseline, requiring your solution to be published on the Marketplace with co-sell collateral. Azure IP Co-sell Eligible is the tier where your solution becomes MACC-eligible and Microsoft field sellers receive incentives tied to your co-sell deals. Qualification involves meeting specific revenue and technical requirements, which include but are not limited to marketplace transaction activity.

Frontier Accelerate for Marketplace reinforces this direction by consolidating ISV Success, Marketplace Rewards, and Azure IP co-sell into a single program organized around marketplace activity.

The framework is not complicated. The challenge is running it reliably as your pipeline grows, because several operational dependencies compound:

• CRM-to-Partner Center sync: When a deal advances in your CRM but the Partner Center referral is not updated, the Microsoft account team is working with outdated information. At low volumes this is a discipline problem. At scale, it becomes a systems problem.

• Referral quality at volume: Microsoft validates referral completeness at submission against five quality inputs, and API-based submissions require the mandatory Marketplace Intent field. The combination of field requirements, completeness checks, and entry volume tends to outpace manual processes as the pipeline grows.

• Private offer complexity: Multiparty private offers across 36+ markets, custom contract lengths, and customer-initiated offer requests all arrive at Stage 3, when your deal team is focused on closing.

• Disconnected post-sale data: Stage 5 expansion depends on usage data and renewal timing being visible where your alliances team works, which is usually a CRM. If that data lives only in Partner Center, expansion opportunities surface too late to act on.

Partner Center and Microsoft's CRM connectors already support core referral-management workflows, including bidirectional Salesforce synchronization for co-sell referrals. SaaSify builds on these capabilities by bringing co-selling across Microsoft, AWS, and Google Cloud into a common environment, with configurable CRM workflows, AI-assisted opportunity enrichment, and consolidated reporting.

• Co-sell referral automation: Extends CRM-to-Partner Center integration with configurable field mapping, CRM-triggered referral actions, and inbound referral routing from Microsoft into Salesforce, HubSpot, or other supported CRMs. For ISVs selling across multiple cloud marketplaces, co-sell workflows for AWS and GCP run through the same CRM interface.

• Private offer and MPO workflows: Handles offer creation, multiparty structures, and marketplace transactions from inside your CRM, across Microsoft, AWS, and GCP, so your deal team is not switching between systems when a customer is ready to commit.

• AI agents for pipeline operations: Addresses the volume challenge with pipeline hygiene, listing optimization, and co-sell opportunity creation at the scale where manual work across multiple partner portals stops being viable.

Talk to a Microsoft co-sell specialist from SaaSify to review your current Partner Center setup, identify where sync gaps or manual steps are creating friction, and map your pipeline to MCEM stages.