COMMENTARY: The SaaS Playbook Built Your Finance Stack. AI Is Breaking It. – Digital Transactions

Finance teams spent a decade assembling best-of-breed tools. One for AR. Another for AP, treasury, FP&A, etc. The SaaS era rewarded this specialization: find a workflow, own it, expand from there. Point solutions won by going deep on single workflows.

I spent decades building the billing systems that finance teams depend on. More recently, I’ve been building enterprise AI solutions for those same teams, and what I’ve learned changes how I see the stack we built together. 

We used to need structured integrations because systems couldn’t read. An invoice was opaque to software. So we built APIs, schemas, and data pipelines to translate documents into something machines could process. The best point solutions were those that built the best translation layer for their workflow.

Today, AI can read the invoice all by itself. No need for translation. That changes everything about how the stack should be assembled.

There are four agent categories finance organizations need: 

• Assist agents draft collection emails, summarize payment history, and pull aging reports. They’re useful, but human bottlenecks remain.
• Automate agents process invoices, match POs, code to GL, and queue for payment without a human in the loop.
• Advise agents surface what nobody was looking for: vendors whose pricing is quietly drifting, customers whose payment patterns predict churn six months out, expense categories outpacing the revenue it supports.
• Configure agents go further, observing approval workflow bottlenecks and restructuring them, or vendor-tiering based on spend patterns that no longer reflect the business.

Most teams never get to Advise and Configure. The problem isn’t motivation, it’s architecture. And that’s the same problem that’s making your SaaS playbook suddenly dangerous.

An Advise agent that only sees your AR platform can’t connect a customer’s payment slowdown with declining order frequency and a change in their AP contact. It can only see within one system. A Configure agent that only touches your invoice workflow can’t restructure the approval hierarchy that spans finance, procurement, and operations. It’s bounded by the same silo its SaaS predecessor was.

The entire value proposition of Advise and Configure agents, (the real value in AI), depends on context that crosses the boundaries of your existing point solutions. The insight that a vendor’s pricing is drifting against comparable suppliers requires visibility across every invoice, every contract, every historical negotiation. That data doesn’t live in one system. It lives in five. 

The instinct to restrict data access across systems is legitimate. Finance carries real regulatory exposure, and even model behavior introduces risks that blunt access controls can’t fully address. But the answer isn’t fragmentation as a proxy for governance. It’s policy-based access with full observability: agents operating under defined permissions, every action logged, every decision auditable. That’s a harder architecture to build than a firewall between systems. But it’s the only one that actually scales.

This is why re-bundling is happening across enterprise software. The companies winning with AI are those that recognize owning one workflow means owning none of them, that the AI that creates real value needs to see the full picture. The foundation-model companies understand this better than anyone. They are not selling APIs any more. They are selling trust, and they’re accumulating the cross-workflow context that makes that trust deserved. 

That’s the AI growth playbook, and it runs directly counter to how finance teams have been buying software for the past decade.

If you’re a finance leader, the individual tools in your stack are probably fine. Your liability is the absence of a context layer connecting them. An Automate agent processing invoices in one system, an Advise agent watching vendor patterns in another, a Configure agent restructuring approval workflows in a third—these agents need to share context to work as a system. 

I wrote a piece on LinkedIn recently about the distribution of the CFO, that is. agents pushing financial decision-making to operating units while the CFO governs through policy. The enabling architecture is a mesh of agents that can see the whole organization. Security governance travels with the agents, instead of blocking them at the door, as in the SaaS playbook.

Unlike specialized SaaS stacks, the AI playbook rewards the finance team with the context layer capable of connecting all of it.

Most of the finance leaders I talk to already sense this. Their tools are good, but the results are underwhelming. The gap isn’t motivation or budget. It’s architecture. Fragmented systems share exports, not context. And agents without context can only Assist.  So, the question is whether  your stack is optimized for the world AI is building, or the one SaaS already built.

—Chris Couch is head of product for the B2B segment at Flywire.