Dynamics 365 vs HubSpot: the per-seat cost of an enterprise CRM at 500 seats

What the published pricing pages actually commit to

Salesforce's pricing page sells the estate in two ways. It lists product families across sales, service, marketing, commerce, data and platform, and it offers a route where a buyer enters the company's specific needs and receives custom pricing details. The page also describes flexible ways to buy Salesforce consumption services, from experimentation to transformation. What it does not do is print a per-user number a procurement team can multiply by 500.

That matters because the reader arriving from the newsletter was promised a per-seat comparison at 50 and at 500 seats. The honest version of that comparison starts with a finding: none of the three vendors' supplied pages publishes the figure. Salesforce points at custom pricing. The Informatica page, supplied as a cross-check, prices in Informatica Processing Units rather than seats, with consumption calculated per scaler based on usage including Secure Agent, CDI-e and Data Mass Ingestion volume.

So the first job before any renewal conversation is to convert the public pages into a like-for-like request. Ask each vendor for a written quote at 50 named users and at 500, with the automation and reporting features a sales team actually uses switched on, and with the term stated. Without that document, any per-seat figure in a business case is an assumption wearing a number's clothes.

Why the seat count is the wrong unit for two of the three

A per-seat model is linear and therefore easy to budget: seats times price times term. Salesforce's page shows it does not sell only that way. Consumption services sit alongside the product families, and the custom-pricing path exists precisely because the company-specific mix changes the number. A 500-seat estate that leans on data and platform products is not the same purchase as 500 sales seats.

Informatica's page makes the split explicit. IPUs give customers access to eligible cloud services listed in the Cloud and Product Description Schedule, and the same units cover master data management on a per-domain records basis. The administrator can control which user has access to each service, monitor usage through a dashboard and set consumption limits. That is a governance model for spend, not a seat count.

The practical consequence for a buyer comparing Dynamics 365 and HubSpot is that the seat count is the stable part of the bill and the feature mix is the variable. Two teams of 500 can sign contracts an order of magnitude apart on the same vendor's page because one bought the reporting and automation modules and the other did not.

How the shortlist compares on the published terms

The table below holds only what the supplied pages state. Where a cell would need a per-seat figure, it says the number is unpublished, because that is the finding a procurement lead needs to carry into the call.

Read the price model column first. Salesforce publishes product families plus a custom-pricing route and consumption services. Informatica publishes a consumption model in IPUs per scaler. Neither page gives a seat price, and the supplied material contains no HubSpot or Dynamics 365 pricing page at all, so their per-seat figures are unpublished here too.

The term column is where the negotiation sits. Salesforce's page does not state contract lengths on the pricing page, and Informatica's page describes swapping services as needs change rather than fixing a term. Ask both for the minimum commitment and the true-up rule in writing.

The add-ons the pages do not itemise

The newsletter summary promised to name the seat count where the pricing model inverts. The supplied pages do not support that arithmetic, and inventing it would be worse than saying so. What they do support is the mechanism by which the inversion happens: features that a sales team treats as core are sold inside product families or as separate services, so the effective price per seat rises faster than the seat count.

Salesforce's page lists its apps by function, including sales, service, marketing, commerce, IT and more, and places AI agents and data on the same platform. A buyer who needs reporting across those functions is buying more than a seat. Informatica's page describes the same shape from the data side: multiple services on one platform, with the IPU model giving room to test new applications and address different use cases.

The question to put to each vendor is therefore not what a seat costs but what the 500th seat includes that the 50th did not. Ask for the feature list attached to the quote, and ask which of the automation and reporting capabilities the sales team uses daily sit outside the quoted tier.

What to ask for before the renewal date

Ask for a written quote at 50 and at 500 named users, on the same feature set, with the term and the true-up rule stated. Ask which services are metered rather than seated, and for the measurement guide that defines the meter, since Informatica's page points to a Measurement Guide for how each scaler is measured. Ask for the dashboard or report that shows consumption against the limit, because Informatica's page states an administrator can monitor usage and set consumption limits, and a buyer should see that screen before signing.

Ask Salesforce to put the custom pricing in writing against a named feature list rather than a product family name, and ask whether consumption services are part of the deal or a separate purchase. The page separates them, so the contract should too.

Ask all three vendors for the renewal uplift clause and the notice period. None of the supplied pages states either, which means the answer is in the contract and nowhere else.

The decision rule

Choose Salesforce if the estate needs sales, service, commerce and data on one platform and the team will accept a custom-priced contract, because the published page sells breadth and a quote rather than a per-seat list. Choose Informatica if the spend is driven by data integration and master data management volume rather than headcount, because its published model meters consumption per scaler and gives the administrator a usage dashboard. Wait if the business case depends on a per-seat number at 500 users that no supplied page publishes, because signing before the written quote at both seat counts exists means budgeting on an assumption. The next decision after the quote is the term, and that is the page to read before the renewal call.