Salesforce CRM Analytics pricing next to Tableau. Why many companies pay twice for the same dashboards.

CRM Analytics lists at $140 to $165 per user per month, and many companies pay it for people who also hold a Tableau seat for the same dashboards. Fixing that starts with an analytics unit price stated outside the bundle.

What does Salesforce CRM Analytics cost, and how does it compare with Tableau?

CRM Analytics lists at $140 per user per month for Growth and $165 for Plus, billed annually. Tableau Cloud runs from $15 for a Viewer on the Standard edition to $115 for a Creator on Enterprise. The gap matters most for people who only look at dashboards.

Why is a CRM Analytics viewer so much more expensive than a Tableau Viewer?

CRM Analytics has no published viewing tier. A sales manager who opens one pipeline dashboard a week still needs a CRM Analytics permission set license, and the lowest list price is Growth at $140. Tableau prices by role, so the same person on a Tableau Viewer seat costs $15 or $35 at list.

Which CRM Analytics edition do your users need?

Plus adds Einstein Discovery and raises the row limit. If a group builds no Discovery stories and its data fits inside 100 million rows, Growth costs $25 less per user per month.

Check the Intelligence bundles as well. Revenue Intelligence, Service Intelligence and Industry Cloud Intelligence each include a Plus license, so a separate Plus seat for the same person is a second charge inside Salesforce itself.

Where does Tableau Next fit?

Tableau Next is a third analytics product, listed at $40 per user per month. In September 2026 Salesforce announced Core, Advanced and Max editions for Agentforce Sales, Service and Industries, with Tableau Next among the bundled contents.

A renewal onto one of those editions can leave you with analytics entitlements in three places: CRM Analytics, Tableau and the Tableau Next seats inside the edition. None of them will carry a separate price unless you ask for one.

Why do companies end up paying for both CRM Analytics and Tableau?

They buy them years apart, sponsored by different teams, and the renewal never compares the two. CRM Analytics usually arrives with a Sales Cloud or Service Cloud program. Tableau often comes in through finance or a central data team, on its own order form and renewal date.

Each purchase was justified on its merits at the time, and after that both simply renewed. The analytics line was almost never reviewed at seat level before renewal, so the overlap grew with each new hire given both tools by default.

Does anyone inside the company notice?

Rarely. The person holding both seats opens whichever dashboard link arrived in their inbox and has no reason to know a second product exists. Finance sees two invoices from two budget lines. The Salesforce admin and the Tableau site administrator each manage their own user list, and neither list shows the other product.

What have we seen in Salesforce analytics renewals in 2024 and 2025?

Across roughly 30 to 40 Salesforce analytics engagements we benchmarked in 2024 and 2025, three patterns came up again and again. Each one is cheap to fix before the renewal is priced and hard to fix afterward.

• Overlap on dashboard use. Where a company ran both CRM Analytics and Tableau, 40 to 60 percent of seats overlapped on dashboard use. Each of those people cost two licenses for one set of dashboards.
• No unit price. Proposals that bundled analytics with Data Cloud and Einstein hid the analytics unit price in 8 of 10 cases. Without that number the two products cannot be compared with each other or with the market.
• Idle builder seats. Between 35 and 55 percent of assigned high tier seats showed little or no build activity in the trailing year. High tier analytics prices the ability to build, and most users consume what a smaller group built.

The bundle is what keeps the duplication alive. A line with no price cannot be benchmarked, cannot be set against the product beside it, and cannot be reduced if you consolidate. That is why we ask for the analytics unit price before any consolidation discussion starts.

You cannot remove a duplication you cannot price.

How much does paying for both products cost in practice?

In the hypothetical example below, removing the duplicate seats saves $168,000 or $672,000 a year at list, depending on which product the duplicate users give up. A negotiated discount shrinks every dollar figure in proportion but leaves the comparison between the options unchanged.

Worked example: 800 CRM Analytics seats and a Tableau Cloud Enterprise site

Say you hold 800 CRM Analytics Growth seats and a Tableau Cloud Enterprise site with 120 Creators and 680 Viewers. The export shows 400 people holding a seat in each product and only viewing. It also shows 50 Creators who built nothing in the trailing year.

Option B saves four times as much as Option A, because it removes the expensive seat. It also carries work: the dashboards those 400 people use must exist in Tableau, including any embedded in Salesforce record pages. Price that rebuild and set it against $672,000 a year.

The Creator correction is smaller and needs no migration. It takes a site role change for 50 users and a lower Creator quantity on the renewal order.

How do you find out who holds both products and who actually builds?

Pull one export from each system, match people on email address, and add usage for the trailing 12 months. Both the overlap analysis and the build activity analysis come from that same data, so running them together costs little more than running either one.

What to pull from Salesforce

• License counts. Setup, Company Information, Permission Set Licenses shows how many CRM Analytics Growth and Plus licenses you own and how many are assigned.
• Named assignments. A SOQL query on the PermissionSetLicenseAssign object returns each assignee and the license they hold. This is also where you catch a Revenue Intelligence user with a spare Plus seat.
• Viewing activity. If you license Event Monitoring, the Wave Change, Wave Interaction and Wave Performance event log files show who opened which CRM Analytics dashboard. The Event Monitoring Analytics app, a CRM Analytics template, turns those files into usage dashboards.
• Build activity. The created by and last modified by fields on dashboards, lenses, recipes and dataflows, available through the CRM Analytics REST API, show who builds.

What to pull from Tableau

On Tableau Cloud, Admin Insights gives you the TS Users data source with each user's site role, license type, last login date and counts of workbooks and data sources owned. TS Events adds sign in, publish and access events. On Tableau Server, the administrative views and the repository hold the same information.

Admin Insights keeps 90 days of history by default and 365 days with Advanced Management. On the default, start saving extracts on a schedule about 12 months before renewal, because history you did not keep cannot be recovered later.

How should each seat be classified?

Put every person in one of four groups and price each group at its current unit price:

1. Builders who need a high tier seat.
2. Consumers who only view.
3. Duplicates who hold both products.
4. Dormant users with no activity in either tool, the easiest seats to remove and the ones account teams contest least.

How do you get the analytics unit price out of a Salesforce bundle?

Ask for it in writing, early, as a condition of reviewing the proposal. Request a stated unit price for each analytics product and edition, separate from Data Cloud and Einstein, on the quote and later on the order form. Asking costs nothing, and every other correction on this page depends on having that number.

What will the account team say, and how should you reply?

• "Analytics is included in the bundle, so there is nothing to itemize." If it is included, showing its share of the total costs Salesforce nothing. You need a unit price per product to allocate cost internally and to plan reductions at the next renewal.
• "Itemizing means losing the bundle discount." Keep the total and the discount. Allocate them across the lines so each product shows what it costs you.
• "CRM Analytics and Tableau serve different users." Share the matched list of people who hold both. Ask which of them uses a capability only one product offers.
• "Move everyone to Tableau Next and the overlap goes away." Ask for the priced transition: which lines end, on which date, and whether you pay for three products while dashboards are rebuilt.

Which contract terms should you ask for?

• A stated unit price per line. CRM Analytics Growth, Plus and each Tableau role priced separately on the order form, so the renewal has a number to reduce.
• Role and edition changes at renewal. The right to convert Creators to Explorers or Viewers and Plus to Growth at the stated prices, without reopening the rest of the deal.
• Quantity reductions per line. The right to lower one analytics line at renewal without losing the discount on the others.
• One end date for both. Both products renewing on the same day, so the comparison happens in one negotiation.
• A written replacement plan for bundled analytics. If Tableau Next comes inside a new edition, a statement of what it replaces and the price of each line during the transition.

Do you have to consolidate onto one analytics product?

No. You need a priced decision for each group of users at this renewal, so that both products do not renew by default because no one looked at the line. Keeping both works when builders sit on the tool that suits their data and each consumer holds one seat.

Why we would not start with a platform decision

The usual advice is to choose one standard BI tool first and migrate everyone onto it. In our experience that debate stalls for months, since each product has a sponsor and the migration cost is unknown, and meanwhile both lines renew again.

Start with the seat classification and the unit prices instead. In the worked example above, the duplicate and idle Creator corrections are worth $216,000 to $720,000 a year at list without any platform decision, and the platform question can follow on its own timeline.

How does this change with company size?

A company with 500 Salesforce users and a few dozen analytics seats can finish the review in days with two exports and a spreadsheet, and the Creator and Plus corrections often matter more than the overlap. At 20,000 users the work is identity matching across several orgs, Tableau Server beside Tableau Cloud, and contracts held by different entities.

Larger reviews usually take in the Platform seat question from the Platform playbook and the ISV subscriptions in the AppExchange brief. The wider library sits in the Salesforce knowledge hub, with role prices in our guide to Tableau Creator, Explorer and Viewer pricing.

What to do next

1. Ask for the unit price. Request the analytics unit price stated separately from the Data Cloud and Einstein bundle, in writing, before you review the proposal.
2. Export seat assignments. Pull CRM Analytics permission set license assignments and Tableau site roles, then match people on email to find everyone holding both.
3. Pull build activity per seat. Use the same exports plus Admin Insights and Event Monitoring to see who built anything in the trailing year.
4. Classify and price every seat. Mark each person as builder, consumer, duplicate or dormant, and price each group at its current unit price.
5. Price the direction of consolidation. Compare removing the CRM Analytics seat with removing the Tableau seat for each duplicate group, including any rebuild work.
6. Take the classified list into the renewal. Negotiate from those counts before the renewal is priced, because neither correction is available once the analytics line is agreed inside a bundle. The Salesforce practice runs the overlap analysis with you.

Frequently asked questions