A store owner spins up their league with zero help
A public onboarding page where a store owner enters their name and contact, picks a slug, sets an admin password, and uploads a logo — then lands directly in their own admin console. No Dwight in the loop. This is the single feature that turns a booth tool into a self-serve retail product that can scale past the number of stores we can hand-hold.
Today, standing up a new store's league is a manual, Dwight-in-the-loop step. That's fine for the first handful of shops, but it is a hard ceiling: the platform can only grow as fast as we can personally provision stores, which is exactly the bottleneck Organized Play is supposed to remove.
For a store owner, the current path is also opaque — they can't just discover the product, sign up, and start running events tonight. Every serious retail platform lets a shop self-provision in minutes; anything slower and the store never bothers.
The engine underneath is already multi-tenant. What's missing is the front door: a no-touch signup that creates the tenant, sets the credential, and drops the owner straight into their console.
Everything a store needs to go live, without us.
Store name, contact, desired slug, admin password, and logo upload on one public page — the whole identity of a new league captured in a single step.
On submit, the tenant is created, the credential is set, and the slug is claimed — all against the existing multi-tenant engine. No manual seeding, no waiting on us.
The owner lands directly in their own /[slug]/admin console, ready to configure a tournament and go live the same night they signed up.
Not yet built. Here's the planned path from signup form to live tenant.
Origin: Manual per-store provisioning is the growth ceiling. This is the feature that makes the platform genuinely self-serve.
Prereqs: None blocking — the multi-tenant engine and per-store auth are already live; this adds the public front door on top.
Status: Designed and on the roadmap, no production code yet. O1 (signup + provisioning) is the unlock; O2/O3 are guardrails and owner lifecycle.
Internal strategy page. Keep this honest as the build changes.