Control Plane for Business Spending

Owning the approval path turns spend software from a payment tool into the system that decides whether money moves at all. In practice, that means the product captures the request, the policy check, the coding, and the approver before a card swipe or bill payment happens. Once those steps live in one system, adjacent products like AP, reimbursements, and procurement become natural extensions instead of separate tools bolted on later.

• Teampay’s core loop is request, approve, pay, reconcile. The important step is not the payment rail, but the front end workflow where an employee asks to buy software, travel, or services and the system routes it through budget owners, security review, legal, and finance. That is where policy enforcement and lock in are created.
  1 sacra
• This is the key contrast with card led models like Brex, Ramp, and Divvy. Cards spread fast because they are free and easy to swap, with monetization driven by interchange. But card volume alone has low switching costs, so those companies added expense and approval workflows to create weekly usage and move into higher margin software.
  2 sacra
• The same logic explains why Teampay could launch AP after already processing $1B to $2B in purchase orders. If a purchase order is already approved and coded, the bill payment step shrinks to click and pay. Airbase pursued a similar mid market finance team position by bundling procurement, expenses, and vendor payments into one product.
  1 sacra 3 sacra

The market keeps moving toward the company that becomes the control plane for business spending. The winners will be the products that sit at the moment an employee asks to spend, then expand outward into bill pay, cards, travel, and accounting sync. Payments will stay commoditized, while workflow ownership will keep absorbing the rest of the finance stack.