

CRM infrastructure, mapped by execution layer.
Four platforms. Four workflow layers. Licensing and implementation cost published inline. No sponsored rankings, no preferred partners.
Four platforms across four execution layers.
Each column is a platform. Each row is a structural layer. Values reflect documented behavior, not vendor claims.
Salesforce Sales Cloud
HubSpot CRM
Pipedrive
Microsoft Dynamics 365
Contact-company-deal object hierarchy. Custom properties available; custom objects require Enterprise tier.
Dataverse-backed entity model. Relationships and custom tables configurable via Power Platform.
Deal-centric model. Persons and organizations linked to deals. Custom fields available at all tiers.
Object-relational with custom object creation. Schema changes require admin deployment.
Multiple pipelines with stage-level automation. Workflow engine handles most linear sequences without code.
Business process flows govern stage transitions. Power Automate handles cross-app automation sequences.
Visual Kanban pipeline. Automation add-on handles triggers and actions; branching logic limited vs. enterprise CRMs.
Stage-based opportunity model. Automation via Flow Builder; complex branching supported natively.
Custom report builder included. Attribution reporting and funnel analytics gated to Pro and above.
Native dashboards plus Power BI integration. Full BI capability requires separate Power BI licensing.
Built-in revenue forecasting and activity reports. Advanced dashboards require Professional tier or above.
Native report builder plus CRM Analytics add-on. Cross-object joins require additional licensing.
OData-based Web API and Dataverse connector. Throttling governed by service protection limits per org.
REST API with OAuth2. Daily call limits scale with tier; private app tokens introduced in 2022.
REST API with token auth. Rate limits are per-user, per-second. Webhooks available on all paid plans.
REST, SOAP, Bulk, and Streaming APIs. Rate limits enforced per org edition.


How each platform processes a deal, not what the sales deck says.
Workflow execution comparisons trace the actual path: record creation, field validation, stage-trigger logic, and downstream automation sequences.
Implementation cost estimates — admin hours, integration lift, and annual licensing at scale — are documented inline for each platform at each layer.
No platform on this page holds a commercial relationship with Stack V. Stack. Methodology is published at /methodology.
The full breakdown covers every layer.
Data model diagrams, stage-trigger maps, API rate-limit tables, and total ownership cost at 100, 250, and 500 seats — structured documentation, not a summary.
