Salesforce Adds an Oracle Veteran as COO, Complicating the Oracle Salesforce Rivalry

Salesforce has promoted Miguel Milano to chief operating officer, adding an Oracle veteran to a role already embedded in Robin Washington’s title. The move gives CEO Marc Benioff two senior leaders with operating responsibilities as Salesforce tries to turn its AI ambitions into repeatable revenue. It also adds a new layer to the oracle salesforce rivalry.

Milano will retain his responsibilities as president and chief revenue officer, according to the initial appointment report. Washington will remain president and chief operating and financial officer. Her title is not changing, which makes this more than a routine promotion.

The structure appears to divide operational leadership between commercial execution and financial discipline. Milano brings direct ownership of Salesforce’s revenue organization, along with earlier experience at Oracle. Washington continues to oversee finance and broad corporate operations.

That arrangement can tighten coordination between product adoption, sales, and financial planning. It can also create ambiguity when a major decision crosses those boundaries. The test is whether two operating chiefs produce sharper accountability or another layer of executive negotiation.

Milano’s Promotion Changes More Than His Title

Salesforce is moving the executive responsible for revenue closer to the center of companywide execution.

Milano joined Salesforce for a second time in August 2023 as president and chief revenue officer. In that position, he led the global organization responsible for converting Salesforce’s product portfolio into customer contracts and renewals.

His promotion extends that commercial remit into broader operations. It places the person closest to sales execution in a stronger position to influence how Salesforce allocates attention, talent, and resources.

Salesforce had not published a detailed division of responsibilities between Milano and Washington when the appointment was reported. That missing detail matters because Washington already holds an operating title.

Washington became president and chief operating and financial officer in March 2025. Salesforce described the position as a newly created role covering profitable growth, operational execution, and financial strategy.

The company’s current leadership roster previously listed Milano as president and chief revenue officer. It listed Washington as president and chief operating and financial officer. The new arrangement preserves Washington’s title while elevating Milano.

Milano’s history makes the commercial logic understandable. He served in Salesforce leadership positions from 2011 through 2020, including responsibility for major international regions. He later became chief revenue officer and co-owner at process-mining company Celonis.

Salesforce brought him back during an earlier management reshuffle. At the time, the company faced pressure to improve growth, margins, and operational discipline after a period of rapid expansion.

The company’s annual filing says Milano previously held leadership positions at Oracle, i2 Technologies, Telefónica, and McKinsey. It also confirms his earlier Salesforce and Celonis roles.

His Oracle experience is particularly relevant. Oracle remains one of Salesforce’s largest rivals in enterprise applications, databases, infrastructure, and customer management software. Milano has now operated within both sides of that competition.

The reporting structure also represents a reversal for Milano. His original 2023 Salesforce employment agreement placed him under then-COO Brian Millham. Milano has now moved from reporting into an operating organization to holding the COO title himself.

Millham retired in 2025 after 25 years at Salesforce. Washington inherited a broad operating mandate, while also replacing Amy Weaver as the company’s senior finance executive.

Milano’s promotion effectively separates part of the old commercial COO function from Washington’s combined operations and finance role. Salesforce has not said that Washington is losing responsibilities. Instead, it appears to be adding a second operating center around revenue.

That distinction should guide how customers and investors interpret the move. This is not a direct replacement. It is an expansion of Milano’s authority within a leadership structure that remains unusually layered.

Why the Oracle Salesforce Rivalry Matters Here

Milano’s background connects Salesforce’s operating strategy to a competitive model he already knows from the inside.

The oracle salesforce contest started with customer relationship management, but it now covers a much wider enterprise technology stack. Both companies want to own the applications, data, automation, and infrastructure surrounding daily business work.

Salesforce built its identity around delivering business software through the cloud. Oracle responded by moving its application portfolio toward cloud subscriptions while expanding Oracle Cloud Infrastructure.

The companies now meet across sales automation, customer service, marketing, analytics, integration, and enterprise data management. Their AI strategies increase that overlap because useful business agents require access to applications and trusted corporate data.

Milano does not define Salesforce’s technical architecture. His role is still rooted in revenue. However, revenue leadership shapes which products receive the strongest sales incentives and which customer problems dominate field execution.

His Oracle experience can help Salesforce navigate large accounts that use products from both companies. Enterprise buyers rarely replace every system from one vendor with an entirely different stack. They add, consolidate, integrate, and renegotiate over several years.

A customer might use Oracle for finance, databases, or infrastructure while using Salesforce for sales and service. AI agents make those boundaries more important because an automated workflow often crosses several systems.

The winning vendor does not necessarily need to replace every competing product. It needs to become the interface through which users and agents retrieve information, make decisions, and execute work.

Salesforce is trying to make Agentforce that interface. Agentforce is the company’s platform for configuring AI agents that can reason over authorized business data and perform defined tasks.

Oracle is pursuing a related opportunity through AI features and agents embedded across its cloud applications. The competitive question is therefore shifting from software ownership toward operational control.

Milano can bring a useful understanding of how Oracle sells broad, strategic agreements. Oracle has long combined applications, databases, and infrastructure in negotiations with large organizations. Salesforce now has a similarly wide portfolio after years of acquisitions and internal expansion.

That portfolio includes Slack, Tableau, MuleSoft, Data 360, Agentforce, and industry applications. Informatica adds another major data-management component.

Breadth creates an opportunity for larger agreements, but it also makes sales execution harder. Representatives need to connect several products to a coherent customer outcome. Customers need evidence that the pieces work together after the contract is signed.

Milano discussed that challenge during Salesforce’s May earnings call. He described multiple approaches to AI monetization, including upgraded user access, new user groups, and customer-facing agent deployments.

Those approaches require coordination beyond a traditional sales organization. Product teams must package the capabilities clearly. Customer-success teams must support deployment. Finance must measure contract quality and revenue durability.

Promoting Milano gives the commercial organization greater authority over that coordination. It also makes him more accountable if Agentforce interest does not translate into production use and expanding contracts.

The Oracle connection should not be overstated. Milano’s promotion does not prove Salesforce is adopting Oracle’s organization or strategy. His Salesforce tenure is longer and more recent than his time at Oracle.

Still, his career provides an uncommon perspective on enterprise purchasing behavior. That knowledge becomes more valuable as the oracle salesforce rivalry moves from individual applications toward integrated AI operations.

Salesforce Needs AI Demand to Become Durable Revenue

The promotion arrives when Salesforce must connect strong AI activity metrics with sustained organic growth.

Salesforce reported first-quarter fiscal 2027 revenue of $11.1 billion, a 13% year-over-year increase. The total included $444 million from Informatica, so the headline growth rate does not show Salesforce’s underlying expansion by itself.

Subscription and support revenue reached $10.6 billion. Current remaining performance obligation, which represents contracted revenue expected within the next year, reached $33.6 billion and increased 14%.

The company’s quarterly results also showed a 21.1% GAAP operating margin and a 34.8% non-GAAP operating margin. Those figures illustrate the balance Washington must protect.

Salesforce reported $1.2 billion in Agentforce annual recurring revenue, up 205% year over year. Combined Agentforce and Data 360 annual recurring revenue approached $3.4 billion, including Informatica Cloud.

It also reported 3.8 billion Agentic Work Units delivered across Agentforce and Slack. An Agentic Work Unit is Salesforce’s measure for certain agent activity consumed through its products.

Bookings for Agentforce One Edition and Agentforce for Apps grew nearly 60%. More than half of Agentforce and Data 360 bookings came from existing customers.

These figures support the company’s argument that customers are buying its AI products. They do not settle whether usage will produce durable, high-margin expansion.

Annual recurring revenue is a useful indicator, but it is not identical to recognized revenue. Bookings measure contracted business, while usage metrics measure activity. Each captures a different part of commercialization.

Milano now sits closer to all three. As revenue chief, he already owned the selling motion. As COO, he has a stronger mandate to connect contracts with implementation, adoption, and renewal.

That connection is crucial for AI products. A conventional software seat can generate subscription revenue even when an employee uses the product lightly. Consumption-based AI revenue depends more directly on recurring activity.

Salesforce is using several monetization models to address that difference. Some offerings package AI capabilities into broader editions. Others apply consumption measures to agent activity or data services.

The mix can expand Salesforce’s addressable opportunity. It also complicates forecasting for customers and the company itself.

Enterprise buyers want predictable costs, access controls, and evidence that automation improves a specific workflow. Salesforce wants growing usage without discouraging experimentation.

Milano’s sales organization must bridge those objectives. It needs to move customers from demonstrations and limited deployments into systems that handle meaningful work.

A practical example is customer service. An organization can deploy an agent to categorize requests, retrieve approved account information, and prepare responses. That process touches the service application, customer data, governance policies, and usage controls.

The sales team can secure the initial commitment. Operational teams determine whether the agent works reliably enough to remain in production. Finance then evaluates the revenue and margin created by that usage.

This is why the appointment matters beyond executive succession. Salesforce is assigning more operating authority to the leader responsible for closing the gap between AI demand and realized business.

The company forecasts organic revenue acceleration during the second half of fiscal 2027. That commitment creates a clear measurement window for Milano’s expanded role.

If core growth strengthens while Agentforce usage and renewals rise, the dual-COO structure will look aligned with the business problem. If growth relies heavily on acquisitions, the promotion will appear less consequential.

Two Operating Chiefs Create an Accountability Test

The new structure can combine commercial urgency with financial control, but only if Salesforce makes decision ownership clear.

Washington’s position was designed to combine operations and finance. When Salesforce announced her appointment, it said she would lead profitable growth, operational excellence, and financial strategy.

Her background supports that assignment. Washington previously served as chief financial officer at Gilead Sciences and Hyperion Solutions. She also held senior finance positions at PeopleSoft before Oracle acquired that company.

She had served on Salesforce’s board since 2013 before joining management. That history gave her a long view of the company’s strategy, governance, and financial commitments.

The original Washington appointment placed significant authority in one office. It joined cost discipline, operating priorities, and financial reporting under a single executive.

Milano’s promotion introduces a second COO without removing Washington’s operating title. Shared titles are not automatically a problem, but they create questions that formal job descriptions usually answer.

Who controls resource allocation when sales priorities conflict with margin targets? Who resolves a disagreement between product packaging and field demand? Who owns customer outcomes after a contract moves from sales into deployment?

Salesforce can answer those questions internally without publishing an organizational chart. Employees, partners, and investors will still infer the answers from decisions.

The most plausible division places Milano over revenue execution and Washington over finance and corporate operations. That would give Milano authority across sales-related functions while Washington maintains responsibility for companywide planning and controls.

Such a split can work because their incentives are complementary. Milano needs to expand customer commitments and usage. Washington needs to ensure that growth creates durable returns.

It can fail when both executives believe they own the same decision. Enterprise software companies regularly face tension between customized sales commitments and standardized product delivery.

A large customer may request integration work, contract flexibility, or a specialized deployment schedule. The revenue organization sees a strategic deal. Finance and operations see implementation costs and long-term obligations.

Clear escalation rules turn that tension into productive review. Unclear authority can delay decisions or allow teams to shop for the answer they prefer.

Benioff remains the final decision-maker. That fact provides an escalation path, but it also presents a risk. A structure that sends too many cross-functional disputes to the CEO does not distribute operating authority effectively.

Salesforce has experience with multiple powerful presidents and operating leaders. Bret Taylor served as co-CEO before leaving in early 2023. Millham later took on broader operating responsibilities during a period of activist pressure.

The company’s 2023 reshuffle also brought Milano back as revenue chief. A contemporary account described the changes as part of Benioff’s response to slower growth and demands for better efficiency.

The current environment is different. Salesforce is producing stronger margins and presenting Agentforce as a new growth engine. Yet the underlying organizational challenge is familiar.

Benioff needs senior leaders who can translate an expansive product vision into consistent execution. The company also needs controls that prevent ambitious selling from weakening profitability.

Milano and Washington represent those two demands. The structure succeeds only when they operate as complementary owners rather than competing centers of authority.

Customers should watch the practical consequences. Changes to account coverage, implementation responsibility, partner programs, and contract packaging will reveal more than the titles alone.

Employees should watch which functions begin reporting to Milano. A wider remit over customer success, marketing, or strategic planning would confirm that his role extends beyond a ceremonial promotion.

Until Salesforce publishes or demonstrates that division, the safest interpretation is limited. Milano has gained authority, Washington has retained hers, and the overlap remains an execution risk worth monitoring.

What Oracle, Customers, and Investors Should Watch Next

The next two quarters will show whether Milano’s promotion simplifies Salesforce’s commercial machine or merely adds another senior title.

The first signal is Salesforce’s next earnings update. Investors should compare reported growth with the contribution from Informatica and examine whether the company delivers its promised organic acceleration.

Current remaining performance obligation deserves particular attention. Rising cRPO indicates that customers have committed to more revenue expected within the following 12 months. It offers a broader view than one quarter’s recognized sales.

Agentforce annual recurring revenue also matters, but it should be read alongside production usage. Growth in both measures would suggest customers are moving beyond pilots.

If contract values rise while Agentic Work Unit growth weakens, Salesforce could be signing commitments faster than customers deploy agents. If usage grows with recurring revenue, the commercialization case becomes stronger.

The second signal is the operating split between Milano and Washington. Salesforce may clarify the structure through updated leadership biographies, securities filings, earnings appearances, or internal changes that become public.

A defined division would strengthen the argument that Benioff has paired commercial execution with financial oversight. Continued ambiguity would increase concern about duplicated authority.

Reporting lines provide the clearest evidence. If customer success, go-to-market operations, or related functions move under Milano, his COO title will carry direct operational weight.

If his responsibilities remain substantially identical to the CRO position, the appointment may primarily signal status or succession planning. That interpretation would raise separate questions about Salesforce’s leadership bench.

The third signal is customer adoption across mixed technology environments. Salesforce needs Agentforce to operate where customers also use Oracle, Microsoft, SAP, ServiceNow, and other enterprise systems.

That is where the oracle salesforce rivalry becomes concrete. Customers will judge which vendor can govern cross-system work without forcing a disruptive replacement program.

Salesforce’s acquisition of Informatica strengthens its data integration and management portfolio. However, owning more components does not automatically produce easier deployment.

Milano’s team must demonstrate that Salesforce can sell integrated outcomes instead of a collection of products. Renewal rates, expanded deployments, and multi-product contracts will provide evidence.

Oracle’s response also matters. It can defend existing accounts by embedding agents directly into finance, human resources, supply-chain, database, and infrastructure products.

Microsoft can pressure both companies through Dynamics, Azure, Microsoft 365, and Copilot. ServiceNow can compete for workflow control, while SAP can use its presence in core business processes.

These competitors make Salesforce’s internal coordination more urgent. Customers do not care which executive owns a workflow when the deployment crosses sales, service, data, and finance. They expect one accountable vendor.

Knowledge workers face a related problem inside their own organizations. Important evidence often sits across meeting notes, documents, messages, and business applications.

A personal knowledge base can help individuals preserve context before automated systems act on it. Enterprise agents need comparable context, governance, and retrieval at organizational scale.

The two use cases differ in scope, but they share one lesson. Automation becomes useful only when it can access the right information and preserve accountable human review.

Salesforce’s leadership structure now faces the same standard. Milano must turn commercial demand into deployed work. Washington must protect financial quality and operational control.

Benioff has effectively created a test with visible outcomes. Stronger organic growth, expanding production usage, and clear decision ownership would validate the arrangement.

Weak adoption or persistent ambiguity would point in the opposite direction. The promotion would then look like another Salesforce executive reshuffle without a corresponding change in execution.

For enterprise buyers, the immediate action is straightforward. Track who owns delivery after the sales agreement, ask how Agentforce usage is measured, and require clear accountability across connected systems.

For investors, watch cRPO, organic growth, Agentforce recurring revenue, and usage together. No single figure establishes whether Salesforce’s AI strategy is working.

The oracle salesforce competition is no longer only about choosing a CRM application. It is becoming a contest over which platform coordinates data, agents, applications, and human decisions.

Milano’s promotion places a former Oracle executive at the center of Salesforce’s answer. The next earnings cycle will show whether the new authority produces a more coherent operating model.