The person, purpose, and principles behind BYO-UI.

Bio

Harry Hawk works across product marketing, go-to-market strategy, demand generation, customer experience, and applied AI. His work focuses on making complex systems understandable and useful—especially where data, software architecture, and the human moment of work meet.

He builds with agentic AI and Model Context Protocol systems, teaches and writes about emerging technology, and uses working implementations to test whether an architectural idea survives contact with real operational constraints.

Origin

The idea began with a change in software economics: AI made front-end creation dramatically cheaper, while the difficult foundations of mature SaaS—data models, integrations, identity, permissions, logic, reliability, and maintenance—remained valuable.

Harry first published the full argument in April 2026 as “The Future of B2B SaaS Is Buy the System, Bring Your Own UI,” then continued the discussion publicly on LinkedIn.

Purpose of the site

The core claim is simple: organizations can keep the durable value of mature software systems while creating interfaces tailored to a specific person, job, decision, or workflow. The site develops that claim through research, examples, patterns, and implementation boundaries.

Noncommercial stance

This site does not sell BYO-UI software, consulting, implementation, sponsorship, placement, rankings, or access to the research. There is no lead form, gated report, demo request, or paid listing.

The desired outcome is that product teams, vendors, buyers, builders, and researchers use the language, test the architecture, publish what works, and challenge what does not.

Professional context

Harry works with RevSure, and the company helped provide the practical context from which the thesis emerged. RevSure is included in the Atlas as one implementation example because it offers multiple ways to work with its governed data and capabilities. It is not treated as the destination of the thesis, and the site is not a RevSure sales property.

How to participate

• Use “BYO-UI” to describe a customer-owned interface over one or more governed SaaS systems.
• Cite the thesis when it informs your work.
• Publish architectures, experiments, critiques, and failure cases.
• Keep facts, vendor claims, editorial assessments, and proposed designs visibly separate.

Citation

Editorial principles

• No paid placement or hidden ranking criteria.
• First-party evidence wherever available.
• Visible verification dates and unresolved questions.
• Author and professional context documented on this page.
• No claim that a proposed interface is a vendor product.