Rho vs Runway
Side-by-side trajectory, velocity, and editorial themes.
Banking platform pushes into A/R and AI-startup banking, becoming a full SMB finance OS.
Rho is expanding from a corporate banking and card platform into a consolidated finance operating system for SMBs. Recent shipments add invoicing, mobile reimbursements, mobile deposits, and tighter accounting integrations alongside the existing card and bill-pay surface. The Rho AI Stack — bundling Claude, AWS, Lovable, and ElevenLabs credits with banking — also positions Rho explicitly toward AI-native startups.
The product is moving along the same arc as Brex, Mercury, and Ramp: collapse spend, bank, bill-pay, and now invoicing into one ledger. Recent releases are filling the white space between banking and accounting, with deeper Puzzle and QuickBooks plumbing rather than headline new modules. The AI Stack pivot suggests a deliberate vertical: capture AI-native startups whose largest non-payroll spend is infrastructure credits.
Expect invoicing to leave beta with payment acceptance rails, and the AI Stack to expand to more vendors as Rho leans into the AI-startup wedge. Bill-pay and reimbursements UX work signals continued mobile-first push.
Steady polish for collaborative financial planning — chart clarity, scenario branching, layout control.
Runway is in steady incremental mode for its collaborative financial planning canvas. Recent work focuses on the everyday ergonomics: 100% stacked charts now consistently display percentages, scenarios can be duplicated or locked as point-in-time versions from Activity History, table and database blocks are resizable per page, and formula editing has gotten cleaner (context menus, an 'f' indicator, sturdier draft history). Earlier entries added customizable fiscal year labels and Last close in formulas.
The cadence is small, focused improvements across the modeling and presentation surfaces — no directional pivot visible. The duplicate-and-lock-scenario primitive is the most strategically interesting recent addition; it suggests Runway is investing in version-control-style collaboration patterns familiar to engineers, not just spreadsheet users. Formula editing depth keeps getting attention, signalling power-user retention is a priority.
Expect continued refinement of scenario management (likely scenario comparison views or merge-style workflows), more chart-type polish, and probably an AI-assisted formula or modeling helper in the next quarter or two given how much editor surface area is being polished.
See more alternatives to Rho →
See more alternatives to Runway →