License the Salesforce analytics layer without paying twice. CRM Analytics and Tableau seat tiers, the Data Cloud and Einstein bundle, and the renewal levers that bring the seat count back to real usage.
Salesforce CRM Analytics and Tableau both report on your data, and many enterprises pay for both without ever splitting who uses which. This playbook sets out the licensing, the seat tiers, and the buyer side levers that cut the bill at renewal.
CRM Analytics is the native analytics layer inside Salesforce, once branded Einstein Analytics and then Tableau CRM. Tableau is the standalone platform Salesforce acquired in 2019. The two overlap, and the overlap is where money leaks.
This guide covers the CRM Analytics pricing model, the Tableau role tiers, the Data Cloud and Einstein bundle, and the renewal moves that work.
Read the related Salesforce services practice, the Salesforce knowledge hub, and the Salesforce Renewal Negotiation Guide.
Key takeaways.
CRM Analytics is the analytics platform that lives inside Salesforce. It builds dashboards and predictive models on CRM data without leaving the record. Salesforce prices it per user per month, billed annually, as an add on to a core CRM license.
CRM Analytics splits into two tiers. Growth covers dashboards and self service exploration. Plus adds larger Einstein Discovery model capacity and higher data row limits. The published rates sit in the low hundreds of dollars per user per month before any enterprise discount, as set out on the Salesforce CRM Analytics pricing page.
Tableau prices by role, not by a single seat type. The role you assign decides the price, and the gap between roles is wide. Most overspend starts here.
Tableau roles descend in price from Creator to Explorer to Viewer, as published on the Tableau pricing page. The buyer side move is to match the role to behavior, not to assign the top role by default.
Tableau role to behavior map.
| Role | What it does | Right fit user | Overspend risk |
|---|---|---|---|
| Creator | Builds data sources and dashboards | Analysts and report authors | High when assigned to viewers |
| Explorer | Edits and queries existing content | Power users and team leads | Medium |
| Viewer | Consumes published dashboards | Most of the business | Low |
A healthy estate is mostly Viewer seats with a thin layer of Creator and Explorer. When the mix inverts, the bill climbs fast. Pull the role assignment report and compare it against actual build activity.
Salesforce now positions Data Cloud as the data foundation under analytics and Agentforce, and frequently bundles all three. The bundle is convenient for the seller and opaque for the buyer.
Salesforce reports analytics, data, and AI as core growth drivers in its investor relations filings, which is why the bundle is pushed so hard at renewal.
Ask for each product on its own line with its own meter and its own rate. If the seller will only quote a single blended number, that is the signal the bundle is hiding the analytics unit price. Read the Salesforce editions and pricing overview to separate the core CRM cost from the analytics add on.
The strongest lever is documented usage. The second is the role mix. The third is the bundle split. All three work best at the renewal date, not mid term.
Salesforce sets out its product direction in its company newsroom, and the direction is consistent: more data, more AI, more bundling. The buyer side counter is to keep every meter visible and every seat justified.
The standard account team pitch is that bundling CRM Analytics, Tableau, Data Cloud, and Einstein delivers the best unit economics. We disagree. In most of the estates we reviewed, the bundle hid the analytics unit price and locked in seats that usage never justified. The real economics depend on how many people build versus view, and on whether your data lives inside or outside Salesforce. The buyer side move is to demand a per product rate, hold the analytics seat count to documented activity, and treat any blended number as a negotiation that has not happened yet.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Two products that do the same job, billed twice, reviewed never. That is the Salesforce analytics line in most enterprises until someone pulls the usage report.
Salesforce CRM Analytics is priced per user per month, billed annually, on top of a core CRM license. The platform splits into Growth and Plus tiers, with Plus adding Einstein Discovery model capacity. Most enterprise buyers anchor the per user rate against their Sales Cloud and Service Cloud discount, not against the list rate.
CRM Analytics is the native Salesforce analytics layer that lives inside the CRM, while Tableau is the standalone visualization platform Salesforce acquired in 2019. CRM Analytics suits dashboards embedded in Salesforce records. Tableau suits cross source enterprise reporting. Many estates pay for both without a clear split of who uses which.
Not always. The two overlap heavily for dashboard reporting inside Salesforce. The buyer side test is whether your analysts need data sources outside Salesforce. If reporting stays inside the CRM, CRM Analytics alone often covers the need. Run a seat by seat usage review before renewing both.
Tableau licenses split into three roles priced in descending order. Creator builds data sources and dashboards. Explorer edits and queries existing content. Viewer consumes published dashboards only. The common waste pattern is buying Creator and Explorer seats for users who only view, which inflates the bill by a wide margin.
No, CRM Analytics runs on Salesforce CRM data without Data Cloud. Salesforce increasingly positions Data Cloud as the data foundation for analytics and Agentforce, and bundles all three in renewal proposals. Treat each as a separate line with its own meter and refuse to let a bundle hide the unit price of any one product.
Enterprise CRM Analytics cost is driven by seat count, the Growth versus Plus split, and any Einstein Discovery capacity. Published per user rates start in the low hundreds of dollars per month before discount. The effective rate after an enterprise discount is the number that matters, so benchmark it against your wider Salesforce agreement.
Yes, when the contract is structured to allow it. Salesforce default terms resist downward true forwards mid term, so the lever sits at renewal. Pull active usage for the trailing twelve months, identify dormant analytics seats, and bring a documented reduction target to the renewal rather than accepting the prior count as the floor.
The most common overspend is paying for high tier analytics seats for users who only view dashboards. Across the estates we review, a large share of assigned analytics licenses show little or no build activity. Match the license role to actual behavior and the saving usually pays for the review several times over.
Redress is independent. Buyer side. Industry Recognized. Five hundred plus enterprise software engagements. $2B in client spend under advisory. Eleven vendor practices. One hundred percent buyer side. Read the related About Us page, the management team page, and the contact page.
A buyer side framework for the Salesforce renewal cycle. The uplift framework, the true forward framework, the shelfware review, the price hold language, the edition mix model, and the competitive levers across the Salesforce estate.
Used across more than five hundred enterprise software engagements. Independent. Buyer side. Built for Salesforce customers running the next renewal cycle.
Independent. Buyer side. The advisory firm enterprise software vendors do not want you to hire.
Salesforce analytics signals, CRM Analytics and Tableau seat trends, Data Cloud and Einstein bundling signals, and the renewal levers that cut the Salesforce analytics bill.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
