AI lowers interface cost
Small teams can create focused screens, agents, and workflows faster than packaged applications can anticipate every customer-specific question.
An open thesis for B2B SaaS
AI has changed the economics of building software. It has not erased the value of governed data, permissions, domain logic, integrations, actions, and operational history. Buy the foundation. Shape the experience around the work.
A public thesis, not a product.
Governed data · identity · permissions · domain logic · integrations · actions · history · reliability
The thesis in 90 seconds
The build-versus-buy decision is no longer one decision. The system layer and interface layer can be evaluated separately.
Small teams can create focused screens, agents, and workflows faster than packaged applications can anticipate every customer-specific question.
Clean models, permissions, integration maintenance, operational edge cases, domain judgment, and reliable actions remain costly to reproduce.
The same trusted system can serve an executive brief, a diagnostic console, an approval queue, or an AI agent—without rebuilding the engine.
Not build versus buy
Vibe coding changes the cost curve for front-end software. It does not make identity resolution, attribution logic, consent, account hierarchy, permissions, data quality, 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. Vendors can expose trusted capabilities rather than absorbing every customer variation into the core roadmap. Customers can adopt mature systems without surrendering interface flexibility.
One system or several
BYO-UI can be a focused layer over one platform or a customer-owned workspace that coordinates several systems while preserving each source of truth.
A beehiiv publication cockpit, a HeyGen production console, or a HubSpot pipeline debugger. One system supplies most of the data and actions.
A newsletter-to-video studio, account journey room, or campaign exception cockpit. The interface coordinates systems of record, production, and engagement.
Evidence across the stack
The Atlas evaluates systems—not merely MCP servers—across APIs, events, query access, extensions, identity, governance, action depth, and agent surfaces.
A strategically important B2B demand platform whose official MCP exposes a broad operational surface across campaigns, audiences, analytics, creative, budgets, and connected systems.
A leading newsletter operating platform with an unusually broad first-party MCP that makes publishing, audience, growth, monetization, automation, podcast, and site capabilities available…
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…
A system of record in CRM, marketing, service, and CMS with documented external access and relevance to customer-owned interfaces.
A system of record in CRM and enterprise application platform with documented external access and relevance to customer-owned interfaces.
A system of orchestration in Data cloud and AI platform with documented external access and relevance to customer-owned interfaces.
Adopt the idea
BYO-UI is offered as a public, falsifiable thesis. Read it, challenge it, cite it, build an implementation, or propose a better boundary between the system and the interface.