Louis Hoch is the co-founder, chairman, president and CEO of Usio, a Nasdaq-listed payments technology company. He has more than 30 years of experience in management and payment processing.

For most of the cloud era, SaaS companies built competitive advantage by shipping better features faster than their competitors. Generative AI is weakening that advantage. It can help a small team write code, build interfaces, and launch functionality in a fraction of the time those tasks once required.

Subscribe to the FR

For SaaS companies, that creates a meaningful opportunity to experiment faster, serve narrower markets, and improve products without adding large development teams. But those same capabilities are available to competitors. A feature that once took months to develop may no longer remain distinctive for long, making it harder to turn faster development into a lasting advantage.

Software is not becoming irrelevant. But software functionality alone is becoming less defensible. SaaS leaders now have to ask a more important question: What makes our platform genuinely difficult for a customer to replace?

Increasingly, the answer is not another feature. It is a deeper role in the customer’s workflow, and payments are often where that workflow becomes economically meaningful.

As AI makes software features faster and cheaper to replicate, SaaS companies need other ways to build durable customer relationships and revenue. Embedded payments can offer both, but only when they solve real problems within the workflows customers already use.

From software tool to business infrastructure

When payments are embedded into a platform, the software moves closer to the center of how the customer operates. A field-service platform, for example, may already help a contractor schedule a technician, document a job, and generate an invoice. If that same platform also collects the payment, manages a refund and sends transaction data into the accounting workflow, it’s no longer just a scheduling tool. It has become part of the business's financial infrastructure.

This matters for both retention and revenue.

A customer can compare software features and switch to a competing offering. Replacing a platform that connects operations, customer data, invoicing, and payments is a more consequential decision. Payments also create transaction-based revenue that can grow alongside the customer. Instead of relying entirely on a fixed subscription, the SaaS provider participates in the economic activity that its software facilitates.

This is why companies such as Shopify and Toast are not best understood as subscription-software businesses alone. Their platforms combine software, commerce, and financial services. The payment functionality is an inherent part of the product’s value.

Payments aren’t authentically a moat

I won’t argue that every SaaS company should add card acceptance and declare victory. Basic payment processing is widely available. If it sits awkwardly alongside the product or creates a disconnected experience for customers, it may add little strategic value.

Embedded payments become defensible when they solve a recurring problem inside the workflow. That may mean coordinating complex money movement across multiple parties, payment channels and recurring transactions, while automating reconciliation and handling refunds. The strongest programs remove operational friction that the software provider already understands better than a general-purpose payments company would.

The starting point, then, should not be “How do we earn payment revenue?” It should be “Where does money movement create friction for our customers, and can we solve that friction within the experience they already use?”

If the answer is clear, monetization and retention can follow. If it’s not, embedding payments may become a distraction rather than a strategy.

Build the experience. Partner for the infrastructure

Once a platform identifies a real use case, it faces another decision: how much of the payments stack should it build itself?

For most SaaS companies, the right goal is to own the customer experience without trying to become a payments company from the ground up. Merchant underwriting, fraud controls, compliance, settlement, network relationships, and support all require specialized infrastructure and ongoing investment. Building those capabilities internally may make sense for a company with enormous scale and a highly unusual need, but it is not the most efficient path for most vertical platforms.

A payment facilitator or infrastructure partner can manage much of that complexity behind the scenes while the SaaS company controls how payments appear within its product. The partner should not force the platform into a generic model. It should support the payment methods, money flows, and customer experience that the platform’s market actually requires.

SaaS leaders evaluating partners should look beyond processing price. They should ask whether the infrastructure can support their desired onboarding experience, handle their customers' risk profile, accommodate how funds need to move, and scale without requiring a major rebuild later.

The next SaaS advantage

AI will continue to lower the cost of creating software. It will also produce more specialized applications for more industries. That fragmentation creates an opening for platforms that understand not only what their customers need to do, but also how and when money moves through that work.

The durable advantage will come from combining three layers: AI to make the product more intelligent, software to control the workflow, and payments to facilitate the economic activity inside it.

Enjoying? Sign up here

SaaS companies should not embed payments simply because the market is moving in that direction. They should do it when payments make the product more useful, the customer’s operation more efficient, and the platform harder to replace.

AI may make features easier to copy. It cannot as easily copy a trusted position at the center of a customer’s business.