Software as the Bad Cop
Andrew Hoag, CEO of Teampay on building expense management for the enterprise
Making the software the bad cop turns finance from a department that cleans up mistakes into a system that prevents them before money leaves the company. In Teampay’s model, employees start with a request in Slack or Teams, the workflow checks budget, vendor, approval chain, and payment method, and only then issues a card, bill pay, or reimbursement path. That is what creates compliance, cleaner books, and a less adversarial relationship between employees and finance.
-
The core product logic is request, approve, pay, and reconcile. That matters because most spend tools historically focused on what happens after a purchase, like receipts or reimbursement, while Teampay is trying to decide whether the purchase should happen at all, and who must sign off first.
-
This is the main split between workflow first vendors and card first vendors. Brex and Ramp used free cards and interchange to grow fast, while Teampay and Airbase leaned harder into paid software, approvals, ERP integrations, and larger customers with 100 plus employees, where uncontrolled card sprawl stops working.
-
Once approval logic sits in front of every purchase, it becomes a wedge into adjacent products. Teampay describes purchase orders turning naturally into bill pay, and Ramp is extending the same control layer with AI that reads receipts, invoices, and contracts, then preclassifies spend for finance teams.
The market is heading toward systems that act less like expense reporting tools and more like access control for company money. The winners will be the platforms that encode policy deeply enough to route every purchase automatically, then use that position to absorb AP, procurement, cards, and eventually more of the finance back office.