Salesforce 2030 Revenue Target Hits $63 Billion, but AI Adoption Must Catch Up
Salesforce raised the stakes around its AI strategy by projecting $63 billion in revenue for the fiscal year ending in January 2030. The Salesforce 2030 revenue target exceeds Wall Street’s average estimate and presents a direct answer to fears that generative AI will weaken established software vendors.
The number is also more complicated than a simple vote of confidence in Agentforce. It includes Informatica, the data-management company Salesforce acquired last year. Salesforce must still prove that AI can accelerate its core business after the acquisition contribution is separated.
That challenge puts Salesforce opposite a growing replacement thesis. Anthropic, OpenAI, Microsoft, and other AI providers increasingly offer agents that can work across business applications. Salesforce is betting that those agents will make its customer data and workflows more valuable, rather than make its software unnecessary.
What the Salesforce 2030 Revenue Target Actually Changes
The new outlook turns Salesforce’s AI argument into a measurable financial commitment.
Robin Washington, Salesforce’s president and chief financial and operating officer, presented the outlook during the company’s September 16 investor session in San Francisco. The target covers the fiscal year ending in January 2030.
The projection exceeds the $61.4 billion average analyst estimate reported in the original fiscal 2030 outlook. That difference matters because Salesforce is not promising merely to preserve its existing business. It is telling investors that growth can continue while AI changes how enterprise software gets used.
Salesforce generated $41.5 billion in fiscal 2026 revenue. Reaching $63 billion implies an 11% compound annual growth rate from that base, according to its published financial framework.
The company had already raised its fiscal 2030 target to $63 billion in February. The September presentation reinforced that commitment after another quarter of improved bookings and expanding AI revenue.
That distinction is important. Investors were not hearing an entirely new number at Dreamforce. They were receiving an updated defense of a target that now carries more operating evidence.
The outlook includes Informatica, which Salesforce completed acquiring in November 2025. Informatica provides data integration, data quality, governance, and metadata tools for large organizations.
Those capabilities matter because enterprise agents depend on accurate and accessible business data. A capable model cannot complete a customer workflow reliably when records are fragmented, duplicated, or governed inconsistently.
However, including Informatica makes the headline target less useful as a direct measure of organic Salesforce growth. Part of the expected expansion comes from adding an acquired revenue stream.
Salesforce’s latest annual guidance illustrates that effect. The company expects fiscal 2027 revenue between $46.1 billion and $46.4 billion, representing growth of 11% to 12%.
Its second-quarter results say Informatica contributes slightly more than three percentage points to that annual growth rate. That leaves the underlying business growing more slowly than the consolidated headline suggests.
The $63 billion figure therefore establishes two tests. Salesforce must integrate Informatica successfully, and its existing products must return to faster organic growth.
Management says that organic revenue growth is on track to accelerate during the second half of fiscal 2027. Stronger bookings support that position, but bookings still need to become recognized revenue.
Current remaining performance obligation, or cRPO, measures contracted revenue expected within the next year. Salesforce reported 14% constant-currency cRPO growth in its latest quarter.
That indicator offers more substance than a distant forecast because it reflects signed customer commitments. Still, cRPO includes the wider product portfolio and does not isolate demand created by AI.
The Salesforce 2030 revenue target is consequently best understood as a companywide growth framework. Agentforce supports the argument, but acquisitions, core subscriptions, Slack, and data services all share the burden.
Why Salesforce Needs AI to Expand Software, Not Replace It
Salesforce’s central wager is that AI interfaces will increase demand for its data and workflows instead of bypassing them.
Generative AI has weakened an assumption that supported software-as-a-service companies for two decades. Businesses once expected employees to open separate applications for sales, service, analytics, and internal collaboration.
AI assistants can now become a common interface across those applications. A salesperson might ask an assistant to summarize an account, update a forecast, or draft follow-up correspondence without opening several dashboards.
That possibility creates an uncomfortable question for Salesforce. If users spend their time inside Claude, ChatGPT, Microsoft Copilot, or another agent, does the Salesforce interface lose strategic importance?
Salesforce’s answer is to separate its business value from a single interface. Its new AIforce architecture is designed to expose Salesforce data, permissions, business logic, and actions wherever customers choose to work.
The company introduced Claudeforce as part of that approach. It places Salesforce capabilities inside Anthropic’s Claude through a prebuilt Model Context Protocol server.
Model Context Protocol, or MCP, is a standard that lets AI systems connect with external tools and controlled data sources. The integration initially includes 37 sales skills, according to Salesforce.
Salesforce also announced Slackforce and Agentforce Coworker. Slackforce brings Salesforce context into Slack conversations, while Coworker operates within the company’s Lightning interface.
The product strategy accepts that no single vendor will control every AI interaction. Salesforce instead wants to remain the governed system behind those interactions.
That position turns Anthropic into both a potential threat and a distribution partner. Claude can sit between users and traditional software, yet Salesforce can supply the customer context and permitted actions.
Salesforce says its AIforce architecture also supports integrations involving Amazon Web Services, Google, OpenAI, and other builders. This model reduces dependence on any single AI provider.
It also protects Salesforce against rapid changes in model quality. Customers can adopt a stronger model without rebuilding every business record, permission, integration, and workflow.
That is the strongest strategic case behind the revenue forecast. Models can become interchangeable, while trusted enterprise context remains difficult to reproduce.
The risk is that AI providers may absorb more of the economic value. Customers could view Salesforce as infrastructure while spending their incremental budgets on models, agents, and specialized applications.
Salesforce must therefore show that its context layer produces revenue, not only relevance. It needs customers to buy more data capacity, workflow automation, agent usage, and higher-value application bundles.
The latest numbers show meaningful early traction. Agentforce and Data 360 annual recurring revenue reached nearly $3.9 billion in the second fiscal quarter.
Annual recurring revenue, or ARR, represents the annualized value of active recurring agreements at a reporting date. It indicates business scale but does not equal recognized revenue for the quarter.
Salesforce said the combined figure grew more than 210% from the prior year. Agentforce ARR exceeded $1.5 billion and grew more than 240%.
However, Salesforce expanded the Agentforce ARR definition during the quarter. It now includes AI offerings, Slackbot, and Headless 360, making historical comparisons less straightforward.
The broader definition does not invalidate the reported growth. It does mean readers should avoid treating every dollar of Agentforce ARR as revenue from one autonomous-agent product.
Salesforce also reported seven billion Agentic Work Units delivered through Agentforce and Slack. An Agentic Work Unit represents a discrete production task performed by an AI agent.
The company recorded 3.2 billion units during the second quarter, up 97% sequentially. That usage signal suggests customers are moving beyond isolated demonstrations.
Usage still needs interpretation. More completed tasks can support consumption revenue, but the value varies by task, contract, and product configuration.
For enterprise buyers, the relevant question is not whether agents execute billions of actions. It is whether those actions improve sales, service, and operational outcomes without adding excessive oversight.
That is why knowledge quality becomes central. Teams deploying workplace agents need governed information that can be searched, combined, and traced back to reliable sources.
A well-maintained AI knowledge base addresses the same underlying problem at a different scale. AI output improves when the system receives relevant, current, and permission-aware context.
Salesforce’s long-term target assumes enterprises will pay to solve that context problem inside their major customer workflows. The next few quarters must show that the assumption holds beyond enthusiastic early adopters.
Informatica Makes the $63 Billion Goal More Credible and Harder to Judge
Informatica strengthens Salesforce’s technical foundation, but it also blurs the line between acquired growth and AI-driven acceleration.
Salesforce needs enterprise data to support Agentforce. Informatica brings tools for integrating, cataloging, governing, and improving that data across systems.
This combination follows a familiar enterprise-software pattern. A vendor adds adjacent infrastructure, connects it with existing applications, and sells customers a broader platform.
The AI era makes that pattern more urgent. Agents must retrieve facts, interpret relationships, follow permissions, and update operational systems without corrupting records.
Poor data can produce plausible but incorrect answers. Inconsistent permissions can also expose information to users or agents that should not receive it.
Informatica helps Salesforce argue that it can govern the full path from stored data to automated action. Data 360, MuleSoft, Tableau, and Informatica each address part of that path.
Data 360 organizes customer information for real-time use. MuleSoft connects applications and services, while Tableau provides analysis and visualization.
Informatica adds broader integration and governance capabilities across complex enterprise environments. Together, these products can make Salesforce more difficult to replace.
The combined portfolio also introduces integration risk. Customers do not automatically receive value because a vendor owns several complementary products.
Salesforce must unify product experiences, identity controls, metadata, and commercial relationships. It must do that without forcing disruptive migrations or duplicating tools customers already use.
The fiscal 2030 target assumes Salesforce can manage that work while protecting margins. The company has paired its growth goal with a “Rule of 50” framework.
Under Salesforce’s definition, the framework combines constant-currency subscription and support growth with non-GAAP operating margin. Management wants those measures to total 50 by fiscal 2030.
Non-GAAP operating margin excludes several expenses recognized under standard accounting rules. Salesforce’s fiscal 2027 reconciliation excludes stock-based compensation, acquired-intangible amortization, and certain acquisition or restructuring costs.
That distinction matters when evaluating acquisition-led growth. Informatica can lift revenue while also creating integration expenses and intangible-asset amortization excluded from the non-GAAP figure.
Salesforce expects a 34.3% non-GAAP operating margin for fiscal 2027. Its GAAP operating margin forecast is 20.1%, leaving a sizable difference between the two measures.
Neither measure alone tells the complete story. Non-GAAP results help compare operating trends, while GAAP results capture costs that affect shareholder economics.
Salesforce also needs to balance investment with efficiency. Building agents requires model access, computing capacity, security controls, product development, and customer support.
Management argues that its platform can maintain attractive gross margins because most revenue remains ratable. Ratable revenue is recognized over a contract term rather than entirely when usage occurs.
Consumption models can change that profile. They tie more revenue to actual use, which can support expansion when adoption rises but add variability when demand slows.
The long-term framework projects an 11% revenue growth rate from fiscal 2026 through fiscal 2030. It also places the profitability target beside that expansion.
That pairing is central to the investor case. Growth would attract less enthusiasm if Salesforce needed to sacrifice much of its improved profitability to produce it.
The company’s latest forecast keeps operating cash flow and free cash flow growth between 4% and 5% for fiscal 2027. Those rates trail its expected revenue growth.
This gap does not settle the long-term question. Acquisitions, currency effects, and working-capital timing can affect annual cash flow.
It does create a useful checkpoint. A convincing path to $63 billion should eventually produce cash growth that supports the broader profitable-growth narrative.
Informatica therefore works in two directions. It supplies technical capabilities that enterprise agents need, and it contributes immediate revenue to the consolidated total.
Investors will need organic disclosures to distinguish those effects. Otherwise, acquisition contributions could make the headline target appear stronger than the underlying operating trend.
The AI Adoption Gap Remains Salesforce’s Hardest Test
Salesforce has stronger financial evidence, but enterprise AI adoption still trails the speed of product development.
Marc Benioff acknowledged that technology innovation has moved faster than customer adoption. That gap is common across enterprise AI because production deployment requires more than access to a capable model.
Businesses must prepare data, define permissions, test actions, manage errors, and decide when human approval remains necessary. They must also measure whether automation creates enough value.
These requirements favor Salesforce’s established position. The company already manages important records and workflows for many large organizations.
They can also slow the revenue conversion that Salesforce needs. A customer might run a successful pilot without expanding it across departments or committing a larger budget.
Independent reporting has highlighted this uncertainty. Some Salesforce partners have seen interest without the immediate production demand suggested by the most optimistic agent forecasts.
The concern is not that Agentforce lacks customers. It is that trials, bundled features, and initial projects may not translate into sustained organic acceleration.
Salesforce’s own numbers provide arguments for both sides. Nearly $3.9 billion in combined Agentforce and Data 360 ARR represents a substantial business.
Yet the figure remains below one-tenth of Salesforce’s current annual revenue outlook. It also combines AI, data, Informatica cloud revenue, and newly included products.
The company says net new annual order value grew at its strongest rate in four years. Net new annual order value measures new and expanded commitments after cancellations and reductions.
That signal supports management’s claim that demand is improving. It still needs to flow through recognized revenue across several reporting periods.
Analysts have responded more positively than they did a year earlier. Citigroup analyst Tyler Radke described Dreamforce conversations as more constructive, with greater confidence in Salesforce’s strategy and execution.
The market response to the investor session was restrained. Salesforce shares changed little in extended trading after closing at $250.54 on September 16.
One session cannot establish investor conviction. The muted reaction does suggest that the $63 billion commitment was already understood and partly reflected in expectations.
Competition also remains fluid. Microsoft can connect agents with Office, Teams, Dynamics, Azure, and its security products.
ServiceNow controls many information technology and employee workflows. Oracle and SAP hold financial, supply-chain, and human-resources data that agents can use for high-value actions.
Anthropic and OpenAI can build direct relationships with enterprise users. Specialized startups can focus on narrow workflows and move faster than a large platform vendor.
Salesforce’s open approach reduces direct conflict with model providers. It also admits that customers may prefer outside interfaces.
The company must remain valuable when users spend less time inside its traditional applications. That requires Salesforce records, rules, and actions to stay central behind every interface.
Security failures could damage that position quickly. An agent that summarizes a record incorrectly creates inconvenience, but an agent that changes it incorrectly creates operational risk.
Salesforce lists AI integration, security, service performance, infrastructure capacity, and third-party dependencies among the risks affecting its outlook. Those warnings deserve attention as agent autonomy expands.
The company’s new Trusted Enterprise AI Harness aims to govern models, agents, data, and actions. However, company claims about trust require evidence from real deployments and independent assessments.
Concrete deployments offer some encouraging signals. Salesforce says Live Nation uses Agentforce across 120 venue websites and could automate more than 300,000 annual inquiries.
It also says Agentforce Coworker attracted 100,000 activated users during its first 35 days. Activation measures initial reach, but recurring usage and measurable outcomes matter more.
Salesforce reported that Slackbot users increased more than 150% sequentially. Slack also produced its fastest quarterly net new annual order value growth since Salesforce acquired it.
That connection could be important because Slack offers a familiar surface for human-agent collaboration. Workers can review context, discuss recommendations, and approve actions within existing conversations.
Still, rapid percentage growth can come from a small base. Salesforce has not provided enough detail to connect every usage measure with durable, incremental revenue.
The skeptical case does not require believing that AI will destroy Salesforce. It only requires growth to remain slower than the fiscal 2030 framework assumes.
A few points of annual underperformance would compound across the remaining years. Salesforce could then rely more heavily on acquisitions, bundling, or commercial changes to protect the target.
The bullish case is equally concrete. Improved cRPO, faster order growth, rising agent usage, and expanding AI ARR can become recognized revenue as deployments mature.
Salesforce’s problem is therefore execution, not conceptual relevance. The company has identified a defensible role as the context and action layer for enterprise agents.
Now it must show that customers assign enough economic value to that role. Revenue quality, retention, and expansion will provide clearer evidence than product announcements alone.
Salesforce Versus the AI Replacement Thesis
The $63 billion promise rejects the idea that AI will collapse application software, but it does not yet disprove it.
The strongest version of the replacement thesis says AI agents will perform work across systems, reducing demand for traditional application interfaces and licenses.
Salesforce offers a different interpretation. Agents need customer records, business rules, permissions, workflows, and audit trails before they can complete useful enterprise work.
Under that view, AI expands the value of Salesforce. More automated activity means more requests for data, more workflow execution, and more governed actions.
The result is not a simple competition between Salesforce and Anthropic. It is a contest between two possible distributions of value.
One distribution places most economic value in the model and user-facing assistant. Enterprise applications become interchangeable data sources behind that layer.
The other keeps value inside the systems that hold verified context and execute transactions. Models become flexible reasoning components connected to those systems.
Salesforce is organizing its strategy around the second outcome. AIforce makes its architecture available across outside interfaces, while Agentforce supplies specialized agents within its platform.
This strategy resembles how cloud software responded to mobile computing. Valuable services became available through new interfaces without abandoning their underlying data models and workflows.
AI is more consequential because an agent can decide and act, not only display information. That capability places greater importance on governance and accountability.
It also gives model providers more room to control the customer relationship. A general assistant can recommend tools, route tasks, and determine which application receives a request.
Salesforce’s partnership with Anthropic is therefore strategically useful and structurally tense. Claudeforce can expand Salesforce usage while making Claude the interface that users remember.
The company accepts that tradeoff because refusing outside interfaces would create a larger risk. Customers are unlikely to confine every AI workflow to one application.
Salesforce can defend itself by making integration easy and action reliable. It can also use Slack as a collaborative surface where users already discuss work.
The strategy requires genuine interoperability. Customers will resist an “open” platform that functions best only with Salesforce-controlled models, storage, or applications.
Salesforce says its Headless Toolkit exposes platform capabilities through MCP servers, application programming interfaces, plug-ins, skills, and developer tools. That architecture supports multiple interfaces.
The commercial question is whether openness expands the market faster than it weakens lock-in. Salesforce needs partners to bring activity onto its platform without capturing all incremental spending.
Enterprise buyers will make that decision use case by use case. They may favor Salesforce for customer service while selecting different agents for coding, research, finance, or procurement.
That fragmented outcome would still support growth. It would not necessarily support every part of Salesforce’s broader platform ambition.
The Salesforce 2030 revenue target assumes the company can remain a primary control point across enough valuable workflows. Its customer base offers a strong starting position.
However, installed software does not guarantee AI leadership. Customers can preserve Salesforce as a system of record while directing new investment toward other platforms.
That possibility explains why organic growth matters more than consolidated growth. Acquired revenue can increase scale without proving that Salesforce is winning incremental AI budgets.
It also explains the importance of usage-based evidence. Active agents, completed tasks, data consumption, renewal rates, and customer expansion reveal whether the platform is becoming more central.
Headline ARR growth provides an early indication. Stable definitions and clearer product-level disclosure would make that indication much stronger.
Salesforce does not need to own the best general-purpose model. It needs to make the best models safer and more useful inside customer workflows.
That is a credible business position. Whether it produces $63 billion in annual revenue remains an open execution question.
Three Signals Will Determine Whether Salesforce Reaches $63 Billion
The next phase depends on organic acceleration, production usage, and measurable expansion from AI customers.
The first signal is second-half fiscal 2027 organic revenue growth. Salesforce has repeatedly said that its underlying business will reaccelerate during that period.
Investors should separate organic growth from contributions made by Informatica, Contentful, Fin, currency movements, and any additional acquisitions. Consolidated growth alone cannot verify management’s central claim.
A sustained improvement would show that stronger bookings are converting into revenue. Flat organic growth would weaken the connection between AI momentum and the fiscal 2030 outlook.
The second signal is the relationship between Agentforce usage and recurring revenue. Salesforce has reported rapid growth in Agentic Work Units, Slackbot users, and AI ARR.
Those metrics become more persuasive when they rise together. Usage without revenue can indicate experimentation, while revenue without usage can reflect bundling or unused capacity.
Customers expanding from one production workflow into several would provide particularly useful evidence. That pattern would show that early deployments create repeatable demand.
Retention also matters. AI products can grow quickly from a low base while concealing churn, reduced commitments, or weak renewal economics.
Salesforce should provide consistent definitions for Agentforce ARR and related usage measures. Its expanded second-quarter definition makes future comparability more important.
The third signal is the performance of Informatica inside Salesforce’s platform. Investors should watch whether integrations create customer expansion beyond acquired revenue.
Successful cross-selling would support the company’s argument that governed data drives AI adoption. Slow integration would make the $63 billion target more dependent on the acquired business alone.
Margin and cash-flow trends will reveal the cost of that integration. Salesforce must fund product work, sales capacity, computing needs, and customer deployment support.
The company’s AI growth assessment points to stronger bookings, consumption, Informatica, and acquisitions as contributors to the long-term target. Each component carries different implications for business quality.
Organic subscription growth demonstrates demand for Salesforce’s existing portfolio. Consumption growth shows expanding activity, while acquisitions can add capabilities and revenue more quickly.
No single quarterly result will settle the argument. The fiscal 2030 goal spans several years, and enterprise technology deployments rarely progress in a straight line.
However, the next two earnings reports can show whether management’s promised reacceleration has started. They can also clarify how much growth comes from Informatica.
Enterprise buyers should watch the same signals for practical reasons. Salesforce’s strategy will influence where organizations store context, govern agents, and design automated workflows.
Developers should examine whether AIforce offers meaningful model choice and stable interfaces. Administrators should evaluate permission enforcement, auditability, and the effort needed to prepare data.
Knowledge workers should focus on outcomes rather than activation statistics. Useful agents must retrieve accurate context, complete intended tasks, and expose their reasoning to appropriate reviewers.
Teams can also strengthen their own knowledge workflows before committing broad authority to agents. Organized context reduces the gap between an impressive demonstration and dependable daily work.
The $63 billion forecast has given Salesforce a clear scoreboard. Revenue must rise, organic growth must accelerate, and AI usage must become durable customer spending.
Salesforce has produced stronger evidence than it had one year ago. Its bookings, cRPO, AI ARR, and production activity now support a plausible growth case.
The remaining uncertainty is conversion. Can Salesforce turn agent adoption into recurring expansion while outside AI interfaces become more influential?
Watch organic revenue, Agentforce expansion, and Informatica cross-selling over the next two quarters. Together, those signals will show whether the Salesforce 2030 revenue target reflects operating momentum or an ambitious destination.
