How Loople gets adopted
Clubs buy first so parents can get in. Parents are who the product is for — and why it sticks. Sales leads with communities; the experience stays parent-first.
Loople has two layers that are easy to mix up. Keep them separate so marketing, sales, and product don’t reinvent the chicken-and-egg every quarter.
Buyer vs hero
Near-term buyer: the club or community. They pay, set up programs, and open the door. Hero: the busy parent juggling children across communities. Parents are why Loople sticks.
GTM decision
Acquire community-first. Sales and partnerships lead with clubs, leagues, and organizations that need registration, payments, and updates. That’s how parents get onto Loople.
Product principle
Experience stays parent-first. Score every surface on what / when / where / who / respond / owe / done — across communities. Never ship club chrome that makes parents dig. Community ops can earn the revenue; they are not the hero experience.
Later chapter
Parent-driven growth comes after density — when enough communities use Loople that parents pull new orgs in. That’s a later GTM chapter. It doesn’t flip the product bar now, and it doesn’t mean we wait to care about parents.
One spine
Sales motion → community first. Experience bar → parent first. Same product, not two. If a message or feature only serves admin reporting and doesn’t help a parent close a loop, it’s secondary.