Slack-first Enterprise Spend Control

Diving deeper into

Andrew Hoag, CEO of Teampay on building expense management for the enterprise

Interview
we were one of the first subscription and enterprise SaaS apps to launch with the Slack-first approach.
Analyzed 4 sources

Launching in Slack early signaled that Teampay was not trying to be another finance back office system, it was trying to become the place where every employee starts a purchase. That mattered because spend controls usually fail at the first step, when employees bypass finance and buy software or services anyway. By putting request and approval inside Slack and later Teams, Teampay turned finance policy into a chat workflow people would actually use, which made adoption itself part of the product moat.

  • Teampay built around request, approve, pay, and reconcile, with the biggest value in the first two steps. In practice, an employee asks for a tool in Slack, the system routes it based on rules like budget, vendor, or security review, then finance issues payment only after approval. That is more like procurement software made conversational than a card app with receipt capture added later.
  • This was a different bet from Ramp and Brex, which initially used free cards and interchange to spread quickly. Those products started with the payment instrument, then expanded into software. Teampay and Airbase instead targeted companies with 100 plus employees that needed deeper approval logic, ERP integrations, and paid software from day one.
  • The Slack first design also matched a broader enterprise software shift toward living inside existing workflow hubs. Brex now embeds cards inside Navan and Coupa for the same reason, to meet users inside travel and procurement flows instead of forcing a separate app. The winning pattern is not just controlling money, it is controlling the moment when a spending decision gets made.

The next step in this market is deeper embedding and more automation. As spend platforms absorb chat, procurement, travel, and accounting context, the advantage will go to products that can approve, issue payment, and reconcile with almost no manual work. The front end will look simpler, but the companies that win will be the ones with the deepest workflow logic and system integrations underneath.