Ramp Reportedly Raises $1.85B at $60B Pre-Money Valuation

An accountant reviewing a reconciliation needs a way back to the transaction that produced it. Ramp is putting that review relationship inside a wider finance platform, adding AI accounting and AI spending controls to the cards, payments and purchasing workflows that already bring it into company budgets.

That expanding remit provides the context for Bloomberg's October 9 report that the New York fintech raised approximately $1.85B at a roughly $60B pre-money valuation. Dragoneer Investment Group and Thrive Capital reportedly led the round, with Founders Fund participating. Ramp declined to comment, so the transaction terms remain reported rather than company-confirmed. The business question reaches beyond the valuation: how much financial work will customers allow one platform to execute, and how will they retain the evidence needed to oversee it?

What the reported Ramp funding establishes

Bloomberg's reporting describes a completed fundraising effort, following its earlier account of discussions in September. The $60B valuation excludes the new capital. The report does not establish a round-series label, an exact closing date, the full investor roster or a primary-versus-secondary breakdown, and those details should remain open rather than acquire precision through repetition.

The October report follows Ramp's June financing of $750M at a $44B valuation. Eric Glyman's official author page identifies that earlier raise, alongside the company's June discussion of AI spending management. The two events belong to different points in Ramp's development; combining their amounts into a claim about cash available today would require additional capital-accounting evidence.

Fresh financing can support a company's capacity to develop and distribute products, but Ramp has not publicly specified how these October proceeds will be allocated. Its currently marketed products offer a more concrete view of the operating agenda than an invented hiring target or expansion timetable would. The funding story can establish the reported investor commitment while the product story explains what buyers are being asked to consider.

For operators comparing financial software, this distinction is useful. A private valuation describes the terms investors reportedly accepted. A procurement decision still needs its own case: the workflow being replaced, the cost of moving it, the controls required and the people who will remain accountable when the software acts.

Ramp's leadership change puts technology inside the decision

Eric Glyman and Karim Atiyeh became co-CEOs in a June 25 announcement. Glyman described the change as formalizing an existing partnership, with Atiyeh already managing functions that included risk, operations and marketing. Older descriptions of Atiyeh solely as CTO miss the current management arrangement.

Ramp's earlier company history identifies Glyman, Atiyeh and Gene Lee as cofounders. Lee's current operational title is not established in the evidence reviewed here. The company, founded in 2019, gives a New York business address and now reports more than 70,000 customers on its About page. That customer figure is Ramp's own measure, rather than an independently audited count.

The co-CEO arrangement matters to the product discussion because financial software contains organizational decisions. A spending limit defines somebody's authority. An approval route decides which colleague carries the next judgment. Moving an accounting task into an agent changes the work a reviewer receives, including what needs to be checked before a financial record is accepted.

Putting a technical cofounder at the center of general management makes those decisions part of the leadership job. The interpretation is grounded in the remit Ramp has described, without assuming what either founder privately intends. Customers evaluating the platform will encounter that remit through implementation, permissions and the procedures their teams can sustain after deployment.

AI spending introduces a different budget conversation

Ramp's AI Token Spend Management product brings costs into view across providers, models and users. The product addresses a practical problem: the invoice from an AI provider can combine consumption generated by different people and different kinds of work. Assigning that cost to an owner is a necessary step toward discussing its value.

A finance team can ask whether a particular workflow deserves its current budget only after the spending is visible at a useful level. Usage data supplies part of that discussion. The business still has to decide how it will judge a resolved support request, a drafted document or a piece of completed engineering work, because a unit of consumption cannot establish the quality of the result by itself.

Glyman's June essay on the company's $44B valuation sets out Ramp's interest in attributing AI costs, identifying less expensive model options and establishing controls. These are the company's product direction and commercial argument. They should be evaluated against a buyer's actual workloads rather than treated as proof that every substitution will preserve quality or deliver savings.

That creates a specific opening for financial operations software. The person procuring a model, the team consuming it and the manager defending the expense may have different views of the same bill. A platform that helps connect those views can become part of the continuing budget discussion, even as providers, prices and applications change around it.

Accounting execution extends the relationship with reviewers

Ramp Stack launched in June as an AI platform for accounting work. Ramp says it partners with more than 4,500 accounting firms, including 92 of the top 100 CPA firms. Those company-reported relationships describe a distribution context; they do not establish how many firms use every Stack capability or how consistently the product performs.

The company's Q2 product release describes client-specific workflows, reconciliations, schedules and monthly reporting, with source-linked outputs that support an audit trail. The important connection is between execution and review. An accountant needs to examine how a result was produced before accepting the consequences that flow into the ledger.

Ramp is therefore competing across connected decisions: permission to spend, payment, cost attribution and accounting review. A buyer can examine whether the connections reduce repeated work, while also asking what happens when a transaction is corrected, a permission changes or an automated output needs to be challenged. Those are evaluation questions, not claims that Ramp has solved every implementation problem.

The reported October financing arrives while that wider product relationship is taking shape. Glyman and Atiyeh are running a company asking finance teams to entrust software with more execution. The accountant reviewing the reconciliation remains part of the commercial relationship, carrying the requirement that each accepted result can still be traced to the money and decisions behind it.