The thesis

The future of enterprise SaaS is buy SaaS, bring your own UI.

AI is not going to kill enterprise SaaS. It changes where customers should build. Keep the secure, maintained foundation. Shape the experience around the work.

AI changes TCO – it doesn't kill SaaS

From the SQL back door to everyday advantage · 25 seconds

One foundation,many experiences

Follow one maintained B2B SaaS foundation as it becomes useful in different forms for different people and moments of work.

Read the expanded context

Large enterprises have long separated systems from presentation through warehouses, SQL, ETL, and BI.

That path made SaaS data available outside the application without rebuilding the source system.

AI-assisted building expands the same advantage beyond centralized data teams.

One maintained foundation can support a CSV or XLSX export, an inline graph, an executive brief, an interactive artifact, a live application, and a controlled BI or activation feed.

The interface changes with the person and job. Identity, permissions, domain logic, actions, and operational history remain anchored in the system underneath.

One foundation. Many customer-shaped experiences.

AI coding has made it possible to prototype in days what once took quarters. That is a meaningful economic shift. But it does not eliminate the B2B SaaS build-versus-buy question; it separates that question into two layers.

Buy SaaS when recreating its data, security, permissions, integrations, reliable actions, and maintenance would add avoidable cost, operational burden, or risk. Then decide independently whether the vendor’s native interface, a configured view, a generated artifact, or a customer-built experience is the best way to use it.

What B2B SaaS still makes valuable

The hard part of mature B2B SaaS is rarely drawing the chart. It is harmonizing systems, maintaining integrations, resolving identity, enforcing permissions, preserving history, handling edge cases, modeling the domain, and making actions reliable.

When the cost of front-end code falls, the value of a trustworthy foundation can rise. A custom interface on the wrong model simply spreads confusion faster.

What teams can shape

The native B2B SaaS product remains important as the default, fully supported experience. It simply stops being the only possible output or surface for every user, question, and moment.

The shaped experience might be a custom CSV or XLSX export, an inline report or graph, a written artifact, an interactive artifact, a live-updating program, a personal app, a team workspace, or a governed SQL or Reverse ETL feed into BI and other systems.

A demand-generation leader may want a board-ready narrative. A sales leader may want an account-priority queue. A marketing-operations leader may need a lineage and anomaly debugger. A content team may need a workspace spanning beehiiv, HeyGen, and distribution channels. Those experiences can be narrow because the B2B SaaS systems underneath remain broad.

From enterprise extension to individual advantage

Large enterprises have long separated system and presentation through data warehouses, SQL, ETL, and BI tools. That enterprise “SQL back door” made SaaS data available for custom reporting without rebuilding the source application.

AI-assisted, vibe-coded BYO-UI generalizes that pattern. It makes customer-shaped experiences practical for individuals and teams, not only centralized data organizations—and it extends beyond reporting into exploration, simulation, drafting, approvals, orchestration, and governed action.

Seven tenets

  1. The interface is separable. A B2B SaaS application bundles a maintained system and a native experience, but the two do not have to remain inseparable.
  2. The SaaS foundation is still valuable. Maintained data, identity, semantics, integrations, actions, permissions, history, and reliability are the durable product value being purchased.
  3. The native UI still matters. BYO-UI extends a strong default product; it does not mean abandoning one.
  4. Experiences should follow moments of work. Generate or build around a question, decision, exception, approval, or production task—not a clone of the source application.
  5. Use several access modes. SQL, APIs, events, MCP, SDKs, and extensions are complementary rather than mutually exclusive.
  6. Governance travels with capability. Identity, scopes, approvals, audit, provenance, and rollback are part of the interface contract.
  7. Composition is first-class. A customer-shaped experience can sit over one B2B SaaS foundation or coordinate several without erasing their sources of truth.

What BYO-UI is not

  • It is not “vibe-code your own Salesforce.”
  • It is not a claim that every workflow belongs in a chat window.
  • It is not permission to bypass consent, policy, or approval controls.
  • It is not an MCP-server marketplace.
  • It is not a product, service, or vendor ranking.

Test it yourself

The thesis should be judged by observable outcomes: whether customers adopt B2B SaaS more readily when interface lock-in falls; whether vendors can expand into more personas without bloating the native product; whether focused exports, artifacts, interfaces, and workflows improve decision time and adoption; and whether governance can remain intact as experiences become more fluid.

The practical test: name one person and job; define the desired outcome; identify the SaaS systems that own the required data and actions; begin read-only; choose the smallest useful experience; set the approval boundary; and preserve source links, provenance, and action receipts. Add a reversible or approval-gated action only after the value is clear.

Original formulation

The thesis was first published by Harry Hawk in April 2026 and then extended through public discussion and this research Atlas.

Read the original essayView the original post