TTableau provides data visualization and business intelligence software that helps people see and understand their data so organizations can make informed decisions. The product connects to multiple data sources and uses a drag‑and‑drop interface to build dashboards and visualizations, which can be run on‑premises or in the cloud and published to Tableau Server/Tableau Online. It earns revenue through software licenses and subscriptions plus professional services such as training and consulting. Tableau differentiates itself with a user‑friendly interface and powerful visualization capabilities, a strong enterprise footprint, and an ecosystem that includes tight integration with Salesforce (which acquired Tableau in 2019). Its goal is to enable a wide range of customers—from small businesses to large enterprises and public sector organizations—to turn data into actionable insights and drive data‑driven decision making.
Work here?Claim your company
Industries
Company Size
1,001-5,000
Company Stage
IPO
Headquarters
Seattle, WA
Founded
2003
See people who can refer or advise you
Help us improve and share your feedback! Did you find this helpful?
Total Funding
$269M
Above
Industry Average
Funded Over
4 Rounds
Presentations.AI launches AI Sales Enablement Deck Generator with Salesforce to PowerPoint automation, live Presentation Refresh, Editable PowerPoint export and a presentation API at $0.10 per slide. Revenue teams can now generate prospect-specific sales decks from one approved master and connected CRM records, automate presentation updates from Salesforce, HubSpot, Pipedrive, Looker, Tableau, Mixpanel, Google Sheets, Snowflake and BigQuery, govern changes through three approval modes, and create branded PowerPoint files through a REST API priced at $0.10 per slide with a 50% launch discount for three months. San Francisco, Oct. 31, 2026 (GLOBE NEWSWIRE) - Presentations.AI, an AI-native presentation platform backed by Accel and Together Fund, today announced expanded sales enablement capabilities that let revenue teams generate prospect-specific presentations from approved master decks, personalise content using connected CRM information and automatically refresh presentations as business data changes. For more information visit https://www.presentations.ai/solutions/sales The platform combines AI sales deck generation, CRM integrations, patented Presentation Refresh, proprietary Brand Sync and native editable PowerPoint export in a workflow designed for sales representatives, account executives, sales operations teams and revenue enablement leaders. With integrations spanning Salesforce, HubSpot, Pipedrive, Looker, Tableau, Mixpanel, Google Sheets, Snowflake and BigQuery, Presentations.AI connects sales presentations with the business systems used to manage opportunities, customers and commercial performance. The workflow replaces the two steps that consume most of a seller's deck time: copying the standard deck and editing it for the account, and then chasing the latest numbers before the call. It addresses the operational work of preparing the right sales presentation for each customer and keeping it current throughout the sales cycle. AI Sales Deck Generator: One Approved Master, Personalised for Every Prospect Sales teams maintain standard presentations containing company information, product capabilities, customer examples, pricing and competitive positioning. Individual representatives then adapt those presentations for different prospects, industries and deal stages. The process creates repetitive work and makes it difficult for enablement teams to ensure every presentation contains current, approved information. Presentations.AI lets organisations build one approved master sales presentation on the platform, or upload an existing .pptx, and identify the sections that should change for each prospect: the prospect's company name and logo, industry, relevant product capabilities, customer case studies, pricing, integrations and competitive context. Each tagged section is mapped to a CRM field or a data source. The platform uses connected CRM information and configured content rules to generate a prospect-specific version. The result is a branded, editable PowerPoint file that representatives review and refine before a meeting, without opening the master. Salesforce to PowerPoint: Generate Sales Presentations From CRM Records Presentations.AI connects Salesforce opportunity information directly with presentation generation. Enablement teams configure presentation templates around the information maintained in Salesforce, including account details, industry, opportunity stage and relevant commercial fields. When an opportunity reaches a configured stage, a webhook-driven automation initiates generation. The platform retrieves the applicable CRM record, combines it with the approved presentation structure, inserts the prospect's logo through Brand Sync and generates a prospect-specific deck. An enterprise software company can maintain one approved product presentation while generating different versions for financial services, manufacturing and healthcare prospects, each emphasising the relevant capabilities, approved customer examples and commercial information. Representatives receive an editable PowerPoint presentation rather than duplicating and manually revising the master deck. HubSpot and Pipedrive Sales Presentation Automation The same approach extends to sales organisations using HubSpot and Pipedrive. A HubSpot-based team can generate presentations reflecting a prospect's industry, company information and stage in the buying process. A Pipedrive-based organisation can create sales presentations associated with specific deals and configured pipeline stages. CRM-driven generation reduces repeated copying and editing while keeping presentation creation connected to the systems revenue teams already use. Update Sales Decks Automatically With Presentation Refresh Prospect personalisation addresses the initial creation of a sales deck. Maintaining accurate information becomes more important as an opportunity progresses, because pricing, product capabilities, customer usage, commercial assumptions and business metrics change between the first meeting and the final proposal. Presentation Refresh lets organisations connect selected presentation content to supported business data sources and regenerate the presentation when an update is required. Slides carrying pipeline, usage or ROI figures link to live sources: Salesforce, HubSpot or Pipedrive for deal data, Looker or Tableau for dashboards the account team already uses, and Mixpanel, Google Sheets, Snowflake or BigQuery for product and finance metrics. Refresh runs daily, weekly, monthly, on demand or on supported event-based triggers, so a deck built on Monday is accurate on Thursday. A team preparing for a customer meeting refreshes the presentation using the latest connected information rather than checking and rebuilding every relevant slide by hand. Looker to PowerPoint and Automated Business Reporting Sales presentations frequently include business metrics maintained in analytics and reporting systems. Connected reporting workflows across Looker, Tableau, Mixpanel, Google Sheets, Snowflake and BigQuery supply product adoption, customer activity, revenue performance, usage trends and other operational measures. An account management team can prepare a quarterly business review using current customer usage and commercial metrics. A sales engineering team can incorporate product or operational data into a prospect presentation. A revenue operations team can generate management presentations from current pipeline and performance information. Presentation Refresh maintains those recurring slides as the underlying data changes. Automated Approval, Version Control and Sales Content Governance Sales enablement leaders need to control which information appears in customer-facing presentations. Presentations.AI supports workflows in which an approved master provides the foundation for prospect-specific decks, with review and approval requirements configured around updates. Three approval modes are available: Automated refresh with final sign-off: updated presentations are generated and routed for approval before distribution. Slide-level approval: selected content is refreshed automatically while designated sections require reviewer approval. Full review: all changes are held for review before an updated presentation is released. Version tracking and audit logs show which version of the master each prospect deck was built from and record subsequent updates, which matters when pricing, product claims or commercial terms change mid-quarter. Brand Sync Keeps Sales Presentations Consistent Brand Sync identifies company branding from a website URL, detecting logos, colours and fonts, and applies that identity across every generated presentation. Enablement teams establish a consistent presentation identity while allowing appropriate account-level personalisation. Role-based access control lets enablement set which sections representatives can edit and which are fixed. For agencies and sales teams working with multiple customer brands, Brand Sync simplifies the preparation of branded presentations for different organisations. Brand Sync, SSO/SAML and role-based access control are available on paid Presentations.AI plans. Native Editable PowerPoint for Sales Teams Sales presentations move between representatives, managers, sales engineers, customers and procurement teams, and recipients often need to revise content, update commercial information or incorporate slides into other presentations. Presentations.AI provides native editable Microsoft PowerPoint export on every paid plan, alongside Google Slides workflows and PDF, PNG, JPEG, HTML and JSON export. Editable PowerPoint output lets representatives continue refining presentations in the software their organisation already uses, combining automated generation with the flexibility to make final adjustments before customer meetings. Sales Enablement Use Cases Prospect-specific sales decks: generate account presentations using relevant CRM information, industry context and approved sales content. Product demonstrations: prepare materials that emphasise the capabilities and integrations relevant to a particular prospect. Sales proposals: combine approved commercial content with account-specific information. Quarterly business reviews: update customer presentations using connected business and usage metrics. Account-based marketing: generate presentations tailored to named accounts or target industries. Channel and partner enablement: maintain reusable presentation structures for partners while controlling approved product and brand content. Revenue operations reporting: create recurring management presentations using pipeline and commercial performance information. A REST API lets developers incorporate AI presentation generation into external applications and automated workflows, with OAuth 2.0 authentication, role-based access control, audit logs and webhook-triggered operations. Sales enablement platforms, CRM applications, revenue intelligence products and AI agents can initiate presentation generation from their own interfaces. A CRM application can offer a "Generate Sales Deck" action associated with an opportunity. An enablement platform can generate a prospect-specific presentation from approved content and structured account information. A customer success platform can produce recurring account-review presentations from connected business data. The API also supports bulk presentation generation and export across supported output formats. Presentations.AI API Pricing and 50% Launch Discount Presentations.AI offers credit-based API pricing for developers, software companies, sales enablement platforms and AI agents. The standard reference price is $0.01 per credit, with a typical slide requiring 10 credits, equivalent to $0.10 per generated slide before discounts. That works out to $10 per 100 slides and $100 per 1,000 slides at the standard rate. To mark the API launch, Presentations.AI is offering a 50% discount for three months, reducing the effective reference cost to $0.005 per credit, or $0.05 per slide: $5 per 100 slides and $50 per 1,000 slides. Monthly API packages start at $49, with volume discounts of 20% to 50% depending on the selected package. Package-specific pricing and discount eligibility are governed by the applicable commercial terms. API pricing is separate from individual and Team subscriptions. API credits do not carry over between billing periods, and API pricing does not use country-based purchasing-power adjustments. To learn more, visit https://www.presentations.ai/solutions/sales. White-Label Presentation Generation for Agencies and Software Platforms White-label presentation output is available for agencies and software companies incorporating presentation generation into their own products, through the Growth tier and higher commercial arrangements. Organisations can generate customer-facing presentations under their own brand while using Presentations.AI's generation and automation capabilities. Subscription Pricing for Sales Teams Presentations.AI offers individual and team subscriptions. A free Starter plan includes 100 credits. Pro is $240 a year with 5,000 annual credits, equivalent to $20 a month. Gold is $1,200 a year with 50,000 annual credits, equivalent to $100 a month. The Team plan is $720 a year with unlimited seats and 30,000 shared annual credits. All plans are billed annually and subscription pricing varies by country. Standard presentation generation consumes 10 credits per slide. Presentation Refresh consumes 10 credits per slide on each refresh, including slides that remain unchanged. Enterprise pricing, API access and white-label tiers are available on request. Presentations.AI does not use customer content to train its models and is GDPR compliant. The sales enablement workflow is available today. Making Sales Presentations More Useful Throughout the Revenue Cycle "Every seller adapts the company deck for the customer in front of them. The challenge is keeping those changes relevant, accurate and consistent with what the company has approved," said Sumanth Raghavendra, CEO and co-founder of Presentations.AI. "By connecting presentation generation with CRM information and business data, we are reducing the repetitive work involved in preparing sales decks. Representatives can spend more time on the customer's needs and the commercial conversation." Presentations.AI's product direction focuses on helping business users complete presentation tasks, from initial generation through editing, branding, export and recurring updates. For revenue teams, this means making sales presentations easier to personalise, maintain and deliver. Frequently Asked Questions What is an AI sales enablement deck generator? An AI sales enablement deck generator creates sales presentations using approved content, customer information and business context. Presentations.AI generates prospect-specific presentations from master decks and connected CRM data. Can Salesforce automatically generate PowerPoint presentations? Yes. Presentations.AI supports Salesforce-connected presentation generation. Teams use CRM information and configured workflows to create prospect-specific PowerPoint decks when an opportunity reaches a defined stage. Can I automatically update a sales deck for each prospect? Yes. Presentations.AI supports prospect-specific generation and Presentation Refresh for updating connected content as business information changes. Can Looker dashboards be converted into PowerPoint presentations? Presentations.AI supports Looker-connected workflows that incorporate reporting information into business presentations. Supported dashboard and chart behaviours depend on the configured integration. Does Presentations.AI integrate with HubSpot and Pipedrive? Yes. Presentations.AI supports CRM-connected presentation workflows involving HubSpot and Pipedrive. How much does the Presentations.AI Team plan cost? The Team plan is $720 a year with unlimited seats and 30,000 shared annual credits. Can sales enablement platforms generate presentations through an API? Yes. Presentations.AI provides a REST API with OAuth 2.0, role-based access control, audit logs and webhook triggers for incorporating presentation generation into external applications and automated workflows. How much does the Presentations.AI API cost? Reference API pricing is $0.01 per credit, with standard generation consuming 10 credits per slide, equivalent to $0.10 per slide before discounts. A 50% launch discount applies for three months. Monthly API packages start at $49 and provide discounts of 20% to 50%. Does the API have the same pricing in every country? Yes. API reference pricing does not use purchasing-power adjustments. Subscription pricing may vary by country. Can presentations be refreshed automatically? Yes. Presentation Refresh supports recurring updates from connected business information. Each refresh consumes 10 credits per slide, including unchanged slides. Can sales decks be exported as editable PowerPoint files? Yes. Native editable PowerPoint export is available on every paid Presentations.AI plan. Does Presentations.AI support approval workflows for sales content? Yes. Three approval modes are available: automated refresh with final sign-off, slide-level approval and full review, with version tracking and audit logs. About Presentations.AI Presentations.AI is an AI-native presentation platform used by more than 12 million users worldwide to create professional business presentations from prompts, documents, data and websites. Founded by Sumanth Raghavendra, Dhruv Saxena, Biju Abraham, Ravi Kasthuri, Saravanan Govindaraj and Ezhilkumar, the company is backed by Accel and Together Fund and headquartered in Singapore. The company develops AI-powered presentation generation, automatic branding, native editable PowerPoint export, business data integrations and recurring presentation automation. The platform serves sales, marketing, consulting, finance and executive teams across organisations ranging from startups to enterprises. Capabilities, pricing and user figures in this release are as reported by the company as of the release date.
A playground for Every analyst, peace of mind for Every admin: introducing Exploratory Orgs in Tableau Next. Audience: business leaders and analytics teams familiar with TableauNext and Data 360 Introduction. Tableau Next shipped a capability that quietly rewrites a decade-old tradeoff in enterprise analytics: the Exploratory Org, generally available with the September 2026 release. Before Salesforce Blogger get into what it does and why it matters, it's worth stepping back - because the problem it solves has been slowly getting worse across the data world, and most teams have stopped noticing it's there. In this post, Salesforce Blogger'll walk through the tension every analytics team is living inside, what Tableau Next is and how it fits into the Salesforce ecosystem, and then the five concrete moves an analyst can make inside an Exploratory Org. By the end, you'll have a clear picture of whether this is the shape of self-service analytics your team has been waiting for. The tension every analytics team knows. Every analytics organization lives inside the same quiet war. Analysts want speed. A new CSV from a partner. A fresh metric for Monday's exec review. A hypothesis they want to test before the trail goes cold. Admins want trust. One source of truth. Controlled access. No half-finished dashboards drifting into executive decks. For a decade, enterprises have accepted this as a tradeoff. Lock things down and analysts find workarounds. Open things up and governance erodes. Pick a side. Tableau Next changes the terms of that fight. What Tableau Next is. Tableau Next is a modern data connectivity platform with data prep and semantics built in, powered by Data 360. Four things set it apart: * Best-in-class visualization, analytics, and data prep from Tableau * Unified access to production and personal data through Data 360, including true self-service scenarios * A Semantic Layer that translates data into business meaning and generative insights * A reimagined end-to-end analyst experience inside the Tableau Next Workspace Deeply integrated into the Salesforce ecosystem, Tableau Next empowers every level of user to explore, experiment, and act without friction. The result: faster decisions, broader adoption, and analytics embedded into daily workflows instead of siloed reporting. Meet the Exploratory Org. The feature that resolves the agility-versus-governance tension has a name: Exploratory Orgs (previously referred to as Personal Orgs - same capability, newer name). An Exploratory Org is a dedicated workspace for a Tableau Next analyst or a group of analysts, provisioned by an admin from a production org. It gives analysts the freedom to explore and build in a safe, IT-supported environment with full Tableau Next capabilities, while keeping production governance intact. Three design choices make it different from anything the market has today: * Its own Data 360 tenant - real infrastructure, not a sandbox toy * A live, zero-copy link to production data - governed assets flow in without duplication * A controlled promotion path back to production - nothing lands in prod without admin review Analysts move fast inside it. Admins stay in control around it. Both get what they need. What it is not. Scope discipline is what keeps this model clean. An Exploratory Org is not: * A general-purpose Salesforce sandbox * A data activation environment * A platform for enterprise reporting It exists for one job: Tableau Next analytics work - building and testing semantic models, transforms, visualizations, and dashboards. The five moves an analyst can make. Move 1 - Reuse governed data from the production org. Every Exploratory org experience starts with creating a Workspace. Reference production SDMs, DMOs, and Calculated Insights directly. Zero copies. Zero drift. Permanently read-only. When reuse happens, only metadata flows into the Exploratory Org; the data always stays in production. When production evolves, a one-click sync pulls the latest. One version of the truth, intact. Move 2 - bring your own data. CSV, Excel, Snowflake, S3 - upload or connect, scoped to the Exploratory Org only. The vendor file, the partner export, the hand-built table nobody wanted to productionize - all of it blends with trusted data without ever touching production. Move 3 - Build new insights. Create new semantic models, calculated fields, and metrics. Extend production SDMs; extensions inherit updates automatically. Build visualizations and dashboards against reused and personal data on the same canvas. Move 4 - collaborate with teammates. Share the workspace with three clear roles: * Editor - create and edit visualizations, dashboards, and SDMs. Cannot create DLOs, data connections, or run transforms * Viewer - read-only access to dashboards and visualizations Move 5 - promote to production. When something is ready for the enterprise, it moves through a controlled gate: Exploratory Org | Dev Sandbox | UAT | Production. Data 360 assets promote via Datakits and the Salesforce CLI. Lightweight cases - a CSV-based DLO paired with Tableau Next assets - can use the UI promotion flow. Reused assets don't duplicate; they reconnect to the source in production. Admins approve. Analysts ship. Governance stays intact. Exploratory Org in action: meet Alex, the analyst. Alex is a marketing analyst at ACME Technologies, responsible for the North-East region. He has a new lead list from a partner event and wants to find overlap with ACME's existing accounts - fast, before next week's pipeline review. Here's how Alex works inside his Exploratory Org: * Uploads the partner leads file (CSV) as a Data Lake Object * Builds a Semantic Data Model on top of the file * Reuses the Account DMO from the production org - zero-copy, read-only. Data stays in production; only metadata flows into Alex's org * Creates visualizations and a dashboard combining both sources * Shares the workspace with a teammate for peer review * Promotes the dashboard to production once his admin approves The details worth knowing. * Licensing - Exploratory org owners need a Data 360 license plus Tableau Next Creator (Platform Analyst, Self-Service Analyst, or TN Admin). Tableau Next Consumer licenses become eligible as viewers starting Feb '27 * Availability - Exploratory Orgs are generally available to all customers with the March 2026 release * Region - same as production * Pod / release train - not guaranteed to match production, so an Exploratory Org may run on a different release * Data 360 scope - Segmentation, Activation, and real-time pipelines are not in scope. They aren't needed for analytics work * Starting state - created empty. An Exploratory Org is not a copy of the production org The bigger picture. The agility-versus-governance tradeoff isn't a law. It's a legacy of tooling built for a world where analysts and admins shared one environment and fought over the same objects. Tableau Next gives each side its own ground, with a bridge in the middle. Analysts move at the speed of curiosity. Admins ship with the confidence of a reviewer. The business gets both. That's the shape of enterprise self-service analytics the AI era actually requires. Ready to see it in action? Watch a demo, talk to your Tableau Next admin, and start thinking about which analyst teams in your organization are ready to move first. Resources: Full Tableau-filtered sessions catalogue from Dreamforce 2026 [Unlock Actionable Data Insights with Tableau Next] - main end-to-end trail, ~1.5 hrs, 1,100 points. Covers setup, metrics, dashboards, AI analytics, and Slack collaboration. [Prepare for Your Salesforce Tableau Next Consultant Exam] - deeper certification-prep trail, ~7h 55m, ~2,700 points. Covers data strategy, semantic modeling, permissions, workspaces, dashboards, and Tableau Agent. How useful was this post? Click on a star to rate useful the post is! I bring 20+ years of product management, sales development, and consulting experience with intimate knowledge of Salesforce Data Cloud, Salesforce Marketing Cloud, Service Cloud, and Sales Cloud. I'm 6X Salesforce certified. Prior to Salesforce, I worked for Oracle and SAP.
Claude Dashboards vs. Power BI and Tableau. All three tools can contribute to the same analytics process, but their capabilities and levels of maturity differ. | Aspect | Claude Dashboards | Power BI / Tableau | | Initial creation | Conversational generation from instructions | Development using modeling and visualization tools, with AI capabilities depending on the product | | Ad hoc exploration | Fast way to ask and refine questions | Supports exploration of existing models and reports, as well as creating new analyses | | Metric definitions | Depend on instructions and the logic available in the source | Can be centralized through semantic models, measures, and governed data sources | | Technical inspection | SQL visible per chart when using a supported source | Calculations and queries can be inspected depending on each tool's capabilities | | Security | Depends on the source, effective identity, and access configuration | Includes permission and governance mechanisms; Power BI supports row-level security (RLS) | | Ongoing operations | In beta; operational requirements must be verified for each use case | Established platforms for publishing, administering, and maintaining reports, depending on configuration | | Recommended use | Quick questions, prototypes, and initial hypotheses | Recurring reports, shared metrics, and governed analytics solutions | This table simplifies differences that depend on each organization's architecture and configuration. Using Power BI or Tableau alone doesn't guarantee that a report is well designed or governed. The difference lies in how modeling, security, and administration capabilities are used to maintain consistent results. One more detail is worth noting: at the time of the research, direct integration between Claude Dashboards and Tableau was listed as coming soon. I wouldn't assume that integration is already available. My recommendation is to evaluate Claude as another way to explore data and compare its results with the BI solution the organization already uses. Before replacing any part of the process, you need to check which requirements it actually meets. What I'd check before connecting real data. Before adding Claude Dashboards to a business workflow, I'd check four areas. Data freshness. In my test, I was able to schedule updates when the CSV was stored in Google Drive. With a manually uploaded file, the data remains tied to the upload. For data warehouse connections, Claude lets you check when each chart was last updated, but the sources reviewed don't establish a general guarantee for update frequency, scheduling, or latency across all scenarios. I'd also test what happens when the source schema changes, a column disappears, or invalid records are added. JenniferMiraballes need to know whether the dashboard fails, excludes data, or keeps showing results without warning. Security and sharing. Claude Dashboards lets you share artifacts with permissions such as Viewer, Commenter, and Editor. The access model depends on the source type and configuration. When you use a file, sharing the artifact may also mean sharing the data it contains. With connectors, results may depend on each viewer's permissions, so two people could see different figures. In Power BI, row-level security (RLS) restricts which records a user can query based on the roles defined in the model. If you build multi-client solutions, I'd test each client's isolation using their effective identity and credentials before allowing access to real information. Privacy. Before connecting business data, I'd review the plan's terms, the organization's settings, and the applicable policies. Anthropic states that chats and coding sessions from its commercial Team, Enterprise, and API customers are not used to train its models by default. That information isn't enough to determine the applicable data handling for Pro and Max, which also have access to Dashboards. Training is only one part of the analysis. Data retention, confidentiality, permissions, and the organization's compliance requirements also need to be reviewed. For initial tests, I'd use synthetic or anonymized data. If the use case requires real data, I'd send it through a security review first. Cost and behavior. I'd also measure query execution times, the cost of running queries in the data warehouse, and how the dashboard responds as data volumes grow or tables change. The beta doesn't yet provide enough evidence to assume these aspects are fully addressed in every scenario. A practical test before moving to production. If I wanted to evaluate Claude Dashboards for a team or client, I'd prepare a small test using controlled data and reference results. These are the checks I'd apply: * Definitions: Document what each metric means and how discounts, returns, and credit notes are handled. * Results: Compare totals against a reference query or a validated Power BI measure. * Granularity: Review relationships, duplicates, null values, and filters. * Dates: Check the periods being compared and any calculation that depends on the current date. * Updates: Modify the source and test what happens when the schema changes or invalid data is introduced. * Access: Repeat the test with users who have different permissions. * Maintenance: Assign an owner and decide when the dashboard will be reviewed or retired. One additional detail deserves attention: date-based logic can work today and fail a few weeks later. In a test published by Max Nardit on October 9, 2026, the figures from a CSV matched the data, but the author identified logic for the "last complete month" that depended on the current date. With a file ending on October 8, that logic could produce incorrect comparisons by November. This is a case documented by another author, not a test I conducted myself. It illustrates why validating today's numbers isn't enough to guarantee future behavior. I'd also establish a promotion rule: an exploratory dashboard can move into operational use once its metrics are defined, its results are validated, its permissions are reviewed, and its maintenance owner is assigned. If the analysis requires a shared semantic model, row-level security, controlled distribution, and ongoing maintenance, I'd consider moving it to Power BI or the governed BI platform the organization already uses. Claude could change how JenniferMiraballes access BI. I expect more people to start their analyses in the assistant they already use for work. Asking about sales, generating an initial visualization, and digging deeper through conversation is an appealing experience. The evolution of assistants toward Excel, PowerPoint, and other work tools points in the same direction. Claude Dashboards fits that trend, although it's still too early to know how far it will go. For those of JenniferMiraballes who build analytics solutions, this could change how the work is divided. If prototypes take less time to create, JenniferMiraballes can spend more attention on understanding business needs, defining metrics, and validating results. At the same time, JenniferMiraballes'll need to manage more analyses created by users who may not understand the implications of each calculation. That's why I still see an important role for the semantic model, whether it lives in Power BI or in the data warehouse. Metrics need shared definitions, and the tools that consume them must respect those definitions. Sales, an active customer, and margin should mean the same thing to the people making decisions based on them. My test produced a very concrete result: two well-presented dashboards, two different totals, and a difference caused by how credit notes were interpreted. Resolving it required reviewing the metric definition, not changing the design. I'd start by using Claude Dashboards to explore questions, test hypotheses, and speed up prototypes. Then I'd decide which analyses deserve to become permanent reports and what controls they need. BI is still necessary for consistent metrics, controlled access, and solutions that can be maintained over time. Claude could become another entry point to that data; defining the data and validating the results will remain part of the analytics team's job. If you already have a semantic layer powering your Power BI reports, you should start asking yourself what conditions you'd require before letting users explore those same metrics through an AI assistant. Jennifer miraballes. Data Analysis & Power BI Expert
Salesforce to acquire AI analytics startup Loops. 13 Oct 2026: Salesforce has signed a definitive agreement to acquire Loops, an artificial intelligence (AI) analytics startup. The acquisition is intended to strengthen Tableau, Salesforce's data analytics business, as the enterprise software company moves towards AI systems that can analyse business performance and help teams act on their findings. "Tableau's mission has been helping people see, understand and act on data. Loops accelerates this mission, using powerful agentic AI to uncover the drivers behind business performance and surface where teams and agents can take action in real time," said Mark Recher, EVP & GM, Tableau. "Following close, we look forward to bringing these capabilities to Tableau and helping customers turn insights into action faster." The financial terms have not been revealed. Dealroom has reported an estimated transaction value of approximately $30 million. Salesforce expects to close the transaction in early November 2026, subject to customary closing conditions. Once completed, Loops' technology and specialised team will be integrated into Tableau. The company has not provided a detailed timetable for bringing specific Loops capabilities into Tableau products. "We built Loops around a simple idea: analytics should help businesses understand what drives their results and decide what to do next," said Tom Laufer, CEO and Co-Founder of Loops. "Salesforce and Tableau share our vision for making actionable analytics accessible for every organization. Together, we'll have the opportunity to bring what we've built to customers at an entirely new scale." Founded in 2020, Loops is an analytics company built around product and business growth. Its founding team includes Tom Laufer, its chief executive, and Ido Adiv, its chief technology officer. Its product, Scout, allows users to ask questions about business performance and receive analytical data through Slack, Microsoft Teams and email. The system can also monitor KPIs and send alerts when it identifies significant changes or anomalies. Tableau's AI strategy is moving beyond dashboards. Salesforce acquired Tableau in 2019 for approximately $15.7 billion in an all-stock transaction. The acquisition strengthened its position in business intelligence, data visualisation and analytics, adding a platform used by organisations to explore information across business functions. Tableau's role is now expanding as Salesforce develops AI systems that can interpret business information and support decisions. On May 5, 2026, Salesforce announced Tableau's Agentic Analytics Platform, a strategy built around combining data with business definitions, relationships, rules and other context that AI systems need to produce reliable answers. The company argued that access to raw data alone is insufficient for AI agents that are expected to make decisions or trigger actions. Salesforce's Tableau platform announcement. That distinction helps explain the Loops acquisition. An AI assistant can answer a question about a sales report, but enterprise analytics involves a wider set of requirements. The system must understand how the company defines a sales-qualified lead, which revenue figures are recognised, how customer segments are constructed and what constitutes a significant change in performance. Without those definitions, even a technically competent model can produce an answer that appears plausible but does not correspond to the organisation's actual business rules. Tableau is attempting to establish the trusted data and analytical foundation for this work. Loops adds capabilities focused on investigating metric changes and identifying potential explanations. The intended combination would allow users to move from observing a result to examining the factors behind it without treating every investigation as a separate manual exercise. The acquisition therefore fits a specific direction in Salesforce's product strategy: making analytics more proactive and connecting findings to the places where business decisions are made. In November 2025, Salesforce announced an agreement to acquire Spindle AI, a company specialising in agentic analytics, machine learning and modelling business scenarios. Salesforce subsequently completed that acquisition on November 21, 2025. Spindle AI's technology was intended to help businesses model possible outcomes, forecast return on investment and optimise decisions involving areas such as pricing, product packaging and sales strategy. Salesforce placed the team within its Agentforce organisation, with an emphasis on agent observability and self-improvement. Loops product centres on monitoring business metrics, investigating why they change and identifying opportunities for improvement. Salesforce plans to integrate it into Tableau, rather than announcing it as another addition to the Agentforce organisation. The two transactions suggest that Salesforce is building capabilities across different parts of the analytical process. Loops is aimed at understanding business performance, while Spindle AI was acquired to support forecasting, scenario modelling and the measurement and optimisation of AI-powered systems. Loops previously raised $14 million in a seed funding round announced in November 2022. Scale Venture Partners led the round. Deepa Sharma is CXOVoice's Managing Editor, overseeing coverage of technology, cybersecurity, banking, and financial services. She can be reached at [email protected].
Evolving Tableau touts tools to fuel AI-powered analytics. Proactive BI and a natural language-powered app development tool show progress toward an AI-powered platform, while tight integration with Salesforce provides differentiation. Published: 21 Sep 2026 The latest tools from Tableau show that the vendor is transforming its platform from a place for traditional BI to one for agentic AI-powered analytics. Tableau's aim is to enable business users to observe, understand and act on data in real time, according to general manager Mark Recher, who spoke during the Tableau Keynote address at parent company Salesforce's annual Dreamforce user conference. Toward that end, Tableau's bedrocks for enabling enterprises to build and benefit from agentic AI-fueled analytics capabilities include empowering each user to be an application developer, AI-powered analytics that surface and deliver insights to users in their workflows rather than forcing them to visit a BI environment, and enabling users to create trusted data foundations for their data and AI products. New features designed to provide users with those bedrocks include Tableau Studio where analysts can vibe code via natural language to create applications, Proactive Intelligence to deliver insights within user workflows, and Tableau Knowledge to provide a context layer for AI and analytics to draw upon. "They're a logical evolution of the platform," Mike Leone, an analyst at Moor Insights & Strategy, told TechTarget. "Back in May, Tableau introduced its knowledge layer, which keeps a company's business definitions in one place. [Application development] and Proactive Intelligence draw on those definitions." However, rather than distinguish Tableau from competitors such as Microsoft Power BI, Qlik and ThoughtSpot, the new features show that Tableau is undergoing the same repositioning as other analytics specialists adjusting to the burgeoning era of AI. "Tableau continues to be a leader, but the whole market is moving in this direction," he said. "They're building a lot of the same pieces, from semantic layers and agents to connections into AI assistants. One of Tableau's biggest advantages is Salesforce, which is so deeply embedded in businesses that Tableau can go from spotting a problem to acting on it without switching systems." Evolving from BI to AI. With AI now enabling almost any business user to query and analyze their organization's data using natural language, Tableau and other traditional BI vendors have had to transform to remain relevant to their customers. All, in their own ways by repurposing existing capabilities and adding new ones, have prioritized providing users with a trusted foundation for analytics and AI as a means of staying essential. Tableau is doing so by making its longstanding semantic layering capabilities - including the data products and business logic organizations have used semantic models to build - a crucial part of Tableau Knowledge, which it first unveiled in May. The additional new capabilities Tableau is touting, all of which are scheduled for general availability by the end of October, are designed to work with the knowledge layer to form a complete agentic analytics platform, according to Recher. "You become an agentic analytics enterprise by taking probabilistic intelligence, and the speed and power of that, and marry that with your trusted data foundation," he said at Dreamforce. Meanwhile, the new features show that the vendor is meeting the needs its customers as they change by enabling them to transform their analytics operations into an AI-powered workflow, according to William McKnight, president of McKnight Consulting. In addition to Tableau Studio, Proactive Intelligence and Tableau Knowledge, Tableau introduced Data Apps, which extends Studio's application development capabilities to third-party environments such as ChatGPT and Claude. "Tableau's role is expanding from end-user dashboarding into headless, embedded, and conversational analytics infrastructure," McKnight told TechTarget. "The new capabilities mark a significant addition by empowering non-technical users to build micro-applications through natural language while deploying an autonomous 'always-on analyst' that pushes proactive recommendations into operational tools." Like Leone, he added that while Tableau is in line with its competition as BI vendors race to build agentic analytics platforms, its integration with Salesforce is one of the ways Tableau is differentiated. "Tableau is responding to an industry-wide race toward agentic analytics here but brings some uniqueness with its Salesforce ecosystem integration, its installed user base, and allowing external AI models like Claude to safely access governed metrics," McKnight said. Context as a critical element. While Tableau's aim is to "see, understand and act on data at the speed of thought," according to Recher, whether the capabilities highlighted at Dreamforce truly enable insight generation at that rate remains to be seen. When integrated with other agentic AI capabilities from Salesforce, the new Tableau features do seem appropriately designed to help enterprises generate insights and take actions based on their data, according to David Menninger, an analyst at ISG. "Coupled with other Salesforce agentic capabilities, these Tableau enhancements help enterprises achieve the goal of seeing, understanding and acting on the data," he told TechTarget. "I'll reserve judgment on the speed of thought comment... but for the information that is available, analyses and actions can certainly be accomplished more quickly and more consistently." Toward that end, Tableau Knowledge is perhaps the most significant of the new features, Menninger continued. "Context will be the most critical element to ensure that agents are making the right decisions and taking the right actions," he said. Like Menninger, Leone noted that the features Tableau touted at Dreamforce advance Tableau's aim of enabling users better to see, understand and act on data. But Studio, which he called the most valuable of the new features, and Data Apps could lead to complications, he cautioned. "The capabilities that Tableau talked about put them in a good spot to deliver on their whole speed-of-thought mission," Leone said. "The bigger issue is that when anyone can build an app in minutes, companies can end up with piles of near duplicates. And then folks are slowing down because they can't tell which app to trust." Enabling system administrators to certify the data sources used to build applications in Studio and Data Apps could minimize the potential problem, he added. One early adopter of Tableau's evolving platform is CrowdStrike, a cybersecurity provider based in Austin, Texas. Tableau's platform has the technology CrowdStrike has used build the dashboards that enable it to oversee its accounts, according to Jacob Schlan, CrowdStrike's vice president of AI, data and analytics. Now, however, CrowdStrike's aim is to provide its employees with a common, trusted data foundation that they can use to not only analyze data but also build assets. "The trusted data foundation is a non-negotiable," Schlan said. "If you're trying to use raw, uncontextualized data and pointing an LLM or your agent at that, you're never going to be happy with your result." Using Tableau, CrowdStrike created curated datasets that include a context layer, he continued. "That's been the true unlock for us in getting the correct analytics," Schlan said. "It's governed data, the same every time, that allows us to continue on the self-service analytics path." Where Tableau could continue to improve. McKnight suggested that the vendor could further serve the needs of its users and stand out from the competition by adding more governance capabilities to control agents in action. "To succeed as an agentic analytics platform, Tableau must build native logic arbitration and collision detection to manage conflicting actions when multiple autonomous AI agents query its Knowledge Layer," he said. "It could also integrate real-time data quality and observability guards to prevent bad data from causing automated operational failures." Menninger, meanwhile, advised Tableau to concentrate on improving the knowledge layer that he called the highlight new feature. Agents need knowledge layers, and the more context such capabilities can help deliver, the better agents will perform in production. "The industry needs a comprehensive knowledge layer if agents are going to succeed broadly," Menninger said. "That requires robust metrics definitions that can be shared and exchanged among all the parts of an enterprise's information architecture." Eric Avidon is a senior news writer for Informa TechTarget and a journalist with more than three decades of experience. He covers analytics and data management. Related resources.
Find jobs on Simplify and start your career today
Don't see your dream role? Check out thousands of other roles on Simplify.Browse all jobs
Industries
Company Size
1,001-5,000
Company Stage
IPO
Headquarters
Seattle, WA
Founded
2003
Find jobs on Simplify and start your career today
Don't see your dream role? Check out thousands of other roles on Simplify.Browse all jobs