Sequence moving into embedded payments

Adding payments would turn Sequence from the system that calculates what a customer owes into the system that also moves the money, which is where billing software becomes much harder to replace. Sequence already stores the contract terms, usage totals, invoices, reminders, and portal experience. If it also lets a buyer pay the invoice by card, ACH, or pay by bank inside that same portal, it can earn software revenue plus a small cut of each payment flow.

• The product pieces are already adjacent. Sequence has contract intake, invoice generation, dunning, and a branded customer portal with line item visibility. Payments is the next logical step because the invoice is already inside Sequence, and the customer action left is simply approving and sending funds.
  1 sacra
• The business model upgrade is similar to what happened in vertical SaaS. Order.co combines subscription fees with interchange from virtual cards, and Shopify and Toast showed that once software owns workflow, moving into payments adds a second revenue stream tied to customer volume rather than seat count alone.
  3 sacra 4 sacra
• The competitive pressure is real. Stripe bought Metronome to pair high throughput usage billing with payments, showing that payment companies want to move upstream into billing. For Sequence, adding payments is not just expansion, it is defense against larger platforms that can bundle billing and money movement together.
  1 sacra 2 sacra

The likely direction is a fuller quote to cash stack where Sequence handles quote creation, usage pricing, invoicing, payment collection, and revenue recognition in one workflow. If that happens, Sequence can increase take rate per customer and deepen lock in, especially for AI and API companies where billing logic and cash collection are tightly linked.