1
AI lowers interface cost
Small teams can create focused screens, agents, and workflows faster than packaged applications can anticipate every customer-specific question.
A Thesis on the Future of Enterprise SaaS
Buy SaaS. Bring your own user interface.
AI is not going to kill enterprise SaaS. It changes where customers should build. Buy SaaS for secure data, permissions, domain logic, integrations, reliable actions, operational history, and maintenance. Then build the export, artifact, app, agent, or workflow your team actually needs. A public thesis, not a product. The B2B SaaS foundation you buy.
158reviewed platform profiles
729first-party source records
37interface patterns
12multi-system recipes
TCO, risk, and the right layer to build · 36 seconds
What you’re actually buying
See why well-managed B2B SaaS can lower total cost and risk—and why vibe coding is most powerful at the UI and experience layer.
Read the complete transcript
The choice can look simple: buy established B2B SaaS, or vibe-code the whole system.
But the interface hides the expensive responsibilities underneath: secure data, identity, permissions, data controls, domain logic, integrations, synchronization, audit history, reliability, upgrades, and maintenance.
Rebuilding that foundation adds more than initial development cost. It adds security exposure, maintenance burden, integration breakage, inconsistent data, and operational risk.
A well-managed B2B SaaS foundation can lower total cost of ownership and mitigate risk by absorbing those durable responsibilities. It is not always cheaper in every circumstance, but a fair comparison must include the cost of operating what you build.
Use vibe coding where it creates the most leverage: the UI and experience layer. Shape a custom export, graph, brief, interactive artifact, role-specific application, agent, workflow, or controlled feed over the maintained foundation.
Buy SaaS. Shape the experience around the job.
The thesis at a glance
Buy the foundation once. Shape many experiences.
BYO-UI separates two decisions that enterprise software usually bundles together: which SaaS should own the governed data and actions, and which experience best helps a particular person complete the job.
2
B2B SaaS supplies the foundation
The product you buy has already absorbed the difficult work: clean models, permissions, integrations, operational edge cases, domain logic, reliable actions, and durable history.
3
Customers shape what sits on top
The same foundation can produce an export, inline graph, interactive artifact, live application, approval workflow, AI agent, or governed feed into another system.
What a customer-shaped experience can be
Not every BYO-UI needs to be another application.
The interface layer is any useful presentation, artifact, interaction, or delivery path built on the governed B2B SaaS foundation.
Custom export or answer
A purpose-built CSV or XLSX export, a written brief, a chart, or an inline answer assembled for one question.
Interactive artifact
A filterable report, explorer, simulator, comparison, approval packet, or generated artifact someone can interrogate and act on.
Live experience
An artifact, program, personal app, team workspace, or agent that stays current as the underlying SaaS system changes.
Governed downstream feed
SQL, query access, or Reverse ETL that carries trusted SaaS data into BI, analytics, or another operational system.
A working public thesis
The thesis, turned into research and practical tools.
Harry Hawk supplied the thesis, direction, constraints, and final judgment. Codex Sol 5.6 Extra High performed the research, information design, software build, testing, and optimization.
The site demonstrates the direction of Codex from an original strategic thesis through research, product definition, design, implementation, testing, and public communication.
Not build versus buy
Buy what is expensive to get wrong. Build what is valuable to make your own.
Vibe coding changes the cost curve for the experience layer. It does not make the B2B SaaS foundation—identity resolution, attribution logic, consent, account hierarchy, permissions, data quality, reliable actions, or auditability—disappear.
“BYO-UI means the SaaS product is still the source of truth, the operational brain, and the governed action layer. But it no longer has to be the only interface.”Harry Hawk, original BYO-UI essay
That separation creates room for both new-logo growth and deeper expansion. B2B SaaS vendors can sell and expose the trusted foundation instead of absorbing every customer variation into the core roadmap. Customers can adopt mature systems without surrendering the ability to shape how individuals and teams consume data, make decisions, and complete work.
One system or several
The interface follows the job—not the vendor boundary.
BYO-UI can shape one output from one B2B SaaS foundation or coordinate several foundations in a customer-owned workspace while preserving each source of truth.
A
Single-system interface
A beehiiv publication cockpit, a HeyGen production console, or a HubSpot pipeline debugger. One system supplies most of the data and actions.
Focused jobOne authorization boundaryFast MVP
B
Multi-system composition
A newsletter-to-video studio, account journey room, or campaign exception cockpit. The interface coordinates systems of record, production, and engagement.
Shared identifiersExplicit approvalsCross-system audit
Evidence across the stack
Platforms already expose the ingredients.
The Atlas evaluates B2B SaaS foundations and enabling platforms—not merely MCP servers—across APIs, events, SQL and query access, Reverse ETL, extensions, identity, governance, action depth, and agent surfaces.
Metadata.io
Metadata
System of engagementBYO-UI-ready platform
A strategically important B2B demand platform whose official MCP exposes a broad operational surface across campaigns, audiences, analytics, creative, budgets, and connected systems.
APIMCPFirst-party provider
beehiiv
beehiiv
System of engagementBYO-UI-ready platform
A leading newsletter operating platform with an unusually broad first-party MCP that makes publishing, audience, growth, monetization, automation, podcast, and site capabilities available…
APIMCPWebhooks / eventsFirst-party provider
HeyGen
HeyGen
System of productionBYO-UI-ready platform
A leading AI-video platform with a first-party remote MCP, extensive APIs, asynchronous jobs, and webhooks—making it a clear example of a production capability that can sit inside a larger…
APIMCPWebhooks / eventsFirst-party provider
HubSpot
HubSpot
System of recordBYO-UI-ready platform
A system of record in CRM, marketing, service, and CMS with documented external access and relevance to customer-shaped experiences over B2B SaaS.
SQL / structured queryAPIMCPWebhooks / eventsFirst-party provider
Salesforce
Salesforce Sales Cloud / Platform
System of recordBYO-UI-ready platform
A system of record in CRM and enterprise application platform with documented external access and relevance to customer-shaped experiences over B2B SaaS.
SQL / structured queryAPIMCPWebhooks / eventsFirst-party provider
Snowflake
Snowflake
System of orchestrationBYO-UI-ready platform
A system of orchestration in Data cloud and AI platform with documented external access and relevance to customer-shaped experiences over B2B SaaS.
SQL / structured queryAPIMCPWebhooks / eventsFirst-party provider
Adopt the idea
Use it. Test it. Challenge it.
BYO-UI is a public thesis. Read it. Test it. Build on it. Show where it works and where it fails.