Ramp Chooses Partner-Led Finance OS
Post-Brex Ramp vs Mercury
Ramp is trying to win this market by treating banking and card rails like cloud infrastructure, useful plumbing to buy from the fastest supplier while keeping its own engineers focused on the workflow a controller actually sees on screen. That means faster launches of things like bill pay, procurement, travel, and treasury, and it also keeps Ramp pointed at a software and AI valuation story instead of a bank valuation story.
-
In practice, Ramp builds the part finance teams touch. Virtual card controls, receipt matching, accounting coding, and month end close automation. It leaves network connections, bank partnerships, and card program operations to providers like Marqeta, Stripe, and banking partners, because those back end pieces are not where it thinks differentiation lives.
-
This is the opposite of Brex. Brex built direct card infrastructure so it can launch country by country faster for global enterprises and own credit, fraud, and capital workflows itself. Ramp is accepting less control at the rail layer in exchange for more product speed at the finance software layer.
-
The revenue logic follows the product logic. Ramp reached $1B in annualized revenue in August 2025, and the key next step is shifting from mostly interchange toward subscriptions, payments fees, treasury revenue, and AI software. That mix supports a much higher multiple than a deposit spread driven bank model like Mercury.
Going forward, this makes the contest less about who owns the charter or the processor and more about who becomes the default operating system for finance teams. If Ramp keeps turning card, ACH, procurement, travel, and treasury activity into one faster close workflow, its partner led model gives it more shots on goal than a vertically integrated bank.