The future ofSaaS is brightThe future ofSaaS is bright

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 prototypes to test whether an architectural idea survives contact with real operational constraints.

Site production

Harry Hawk originated the BYO-UI thesis and directed the work. Codex Sol 5.6 Extra High - not Harry - performed the site's research, information design, software build, and optimization.

The site demonstrates the direction of Codex from an original strategic thesis through research, product definition, design, implementation, testing, and public communication.

If Codex built it, what did Harry do?

Harry supplied the original thesis, strategic direction, constraints, source examples, corrections, quality bar, and final judgment. Directing the work is the capability being demonstrated. The point is not that Harry manually wrote every line. The point is that he can use Codex to turn a point of view into a rigorous public artifact.

Origin

The idea began with a change in B2B software economics: AI made exports, artifacts, interfaces, and applications dramatically cheaper to create, while the difficult foundation purchased with mature SaaS—data models, integrations, identity, permissions, domain logic, reliable actions, operational history, and maintenance—remained valuable.

The thesis took shape while Harry supported enterprise RevSure customers balancing urgent needs for custom enhancements against a shared product roadmap. The recurring question was practical: when should a team wait for the core product, and when should it shape a focused experience around the governed system it already owns?

RevSure publicly lists organizations including Glean, Zscaler, Abnormal AI, Agent.ai, and Observe.AI among its customers and customer stories. Those public references establish the operating context, not Harry’s individual work with each organization.

Harry first published the full thesis 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 buy SaaS for the durable foundation—governed data, identity, permissions, domain logic, integrations, reliable actions, history, and maintenance—while creating the exact export, report, artifact, feed, interface, agent, or workflow a specific person and job require. The site develops that claim through research, examples, patterns, and operating boundaries.

Noncommercial stance

This site does not sell BYO-UI software, 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 working example because it offers multiple ways to work with its maintained data and capabilities. It is not treated as the destination of the thesis, and the site is not a RevSure sales property.

Frequently asked questions

Does a missing capability mean a platform does not support it?

No. The Atlas records capabilities supported by the reviewed evidence. If a surface or action is not marked, it may be undocumented, unresolved, plan-specific, or simply absent from the sources reviewed so far. MCP actions are assessed from MCP-specific evidence rather than inferred from a platform’s broader API.

How to participate

• Use “BYO-UI” to describe exports, artifacts, feeds, interfaces, and workflows shaped by customers on top of one or more governed B2B SaaS foundations.
• 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.
• Request a private profile review when a platform record needs a correction, a missing capability, or newer first-party evidence.

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.