Regulator made it free
K3 · §4.2.1 · Public infra moat
A private product that competes with a free official source: a government service, regulator, registry, tax portal, permit system, or public database. Better UX, meaning a nicer interface, is not enough when the official tool is funded by taxes, legally trusted, and required by policy. Buyers may hate the public tool, but they still must use it, and they often cannot justify paying for a second version.
Signs your idea has this
- 01The workflow depends on a public registry, tax service, permit, or compliance form.
- 02A government or regulator already provides the core service for free.
- 03The product promise is mainly a nicer interface over an official portal.
- 04The official source has legal or procurement authority.
- 05Customers must reconcile back to the public source anyway.
- 06The public roadmap is expanding into the same workflow.
- 07The paid version cannot create legal authority or remove required steps.
Public idea database
No public examples yet. The idea database is still small, and we are not making one up.
Rare survivors
Survived by bundling legal, banking, and setup work around company formation instead of replacing the public filing.
Survived by collecting compliance evidence automatically instead of competing with the compliance standard itself.
Why this pattern exists fundamentally
Public infrastructure has official status, forced adoption, and funding that does not depend on normal market demand. Survivors do not sell a better version of the regulator. They remove painful work around the official layer while the public source stays the source of truth.
Related patterns
Got an idea that looks different? Run the same framework before building.
Check whether the official source already wins