Set up on request
Where it would sit in Microsoft Dynamics 365
Dynamics 365 Sales supports custom Power Apps component framework (PCF) controls embedded on the Opportunity form. The competitor read would render as a PCF panel on the Opportunity form, same information as the HubSpot card.
What win/loss would need from Microsoft Dynamics 365’s data model
A lost Opportunity in Dynamics 365 is closed with a Status Reason — the standard values are Canceled and Out-Sold, and most orgs extend that option set with their own loss reasons. Competitors are linked via the standard Competitor entity, surfaced as a Competitors sub-grid on the Opportunity, which is the cleanest data model of any CRM on this list for this use case.
Win rate per competitor would read closed Opportunities joined to the Competitor sub-grid where available, or the mapped custom field otherwise, split by won/lost, with loss reasons grouped from the org’s loss-reason option set.
What your reps would see
A few examples of how a competitor card on the Microsoft Dynamics 365 record would play out, using a real IndustryLens-tracked move from Apollo.io (Nov 2026) to show what “our read” and “how to win” would actually say.
An Opportunity form shows Apollo.io in the standard Competitor sub-grid.
Our read on ApolloNext’s consolidation push and the How to win line on category difference.
Positions the deal around competitive intelligence as a separate line item, not a GTM-stack replacement decision.
A Status Reason of Out-Sold is set on a closed Opportunity, with Apollo.io noted as the competitor.
The dated Nov 2026 move and a link to the full Apollo.io battlecard.
Brings the specific ApolloNext launch into the loss debrief instead of a generic "they had more features" note.
A rep is scoping a multi-stakeholder deal where one buyer already runs Apollo.io for prospecting.
The full Our read / How to win pair on the Opportunity form sidebar during the call.
Frames IndustryLens as sitting alongside Apollo.io’s prospecting stack rather than against it.
What works today without it
You don’t need a Microsoft Dynamics 365 integration to use IndustryLens. Every battlecard is available on your IndustryLens dashboard already, the weekly briefing lands by email regardless of CRM, and the MCP connector gives any AI assistant your team uses live access to the same competitor data — none of that waits on a Microsoft Dynamics 365 build.
Want IndustryLens for Microsoft Dynamics 365?
Tell us how your team uses Microsoft Dynamics 365 and we'll scope the build.