Float prioritizes subscription revenue

This pricing choice means Float is selling control software first, and card volume second. A finance team pays Float like it pays for payroll or accounting software, because the product does the work of issuing cards, blocking out of policy spend, collecting receipts, coding transactions into the ledger, and syncing books. That makes revenue more recurring and less tied to how often customers swipe cards.

• In practice, Float gives admins a dashboard to create cards, set merchant rules and spending caps, approve purchases, and push cleaned transaction data into QuickBooks, Xero, and NetSuite. Once those workflows are set, ripping Float out is painful, which supports subscription pricing.
  1 sacra 2 sacra
• Many card led fintechs lean on interchange, the small fee generated each time a card is used. Ramp states it earns revenue primarily from card usage and interchange, with subscriptions as an add on. In Canada, Keep is also described as monetizing primarily from interchange, plus FX spreads and lending.
  4 floatfinancial 5 ramp 6 sacra
• Float still has card economics around it, including cashback and business accounts whose yield tiers depend on card spend, but the core package is priced per user each month. That lines up with customers who want predictable software spend, not a vendor whose economics depend mainly on pushing more transactions.
  1 sacra 4 floatfinancial 7 floatfinancial

The next step is a broader finance suite where cards are the entry point and subscription revenue expands into bill pay, reimbursements, banking, and treasury. If Float keeps winning on Canadian workflows and local integrations, it can look less like a card program and more like the default operating system for business spend in Canada.