Payhawk Travel and Procurement $1M

Fast early uptake shows Payhawk is no longer selling just cards and expenses, it is selling a broader finance workflow that lands more seats and more spend inside the same account. Travel plugs employee booking into approval rules and card issuance, while Procurement plugs purchase requests and POs into the same control layer, so each add on makes the core system harder to replace and raises revenue per customer.1 2 3 4 5

• Travel is built as a native booking flow inside Payhawk. Employees search flights, hotels, and rail with company policy already applied, submit for approval, and once approved Payhawk completes the booking. That is a direct answer to Navan, whose main wedge has been turning travel booking into a broader spend management sale.2 3 6
• Procurement extends Payhawk upstream from payment into the moment a team asks to buy something. In practice that means drafting purchase orders and routing requests before money moves. This puts Payhawk into the same budget control workflow targeted by tools like Coupa, Zip, Ramp, and Brex, but with cards, bills, and payments already connected.2 4 7 8
• The speed matters because new modules in finance software often take months to prove demand. Here, early sales suggest Payhawk was selling into an installed base that already trusted it with expenses, AP, and payments. The company also reported $3.2B in payment volume in 2025, so each attached workflow can feed more transaction volume as well as software revenue.1 4 5

The next step is a tighter bundle where employees ask for a trip, a purchase, or a payment in one interface, and Payhawk handles policy checks, approvals, booking or PO creation, and settlement in the background. If that product motion keeps working, Payhawk moves closer to being the default operating system for mid market and enterprise business spend in Europe.2 3 4 6 8