Chapter 04 · How I'd close partnerships
Sales Execution for Orgo
Here's how I'd position Orgo against TeamSnap, handle the five objections we'll hear in every partnership cycle, run discovery that actually qualifies a partner, and use a structured pilot to prove out adoption before we ask for a full rollout.
Section 1
How I'd position against TeamSnap
When partners bring up TeamSnap, TeamLinkt, or LeagueApps, here's the frame I'd train every rep to use.
The eight points of separation
- Time Literacy: we don't just move events to an app. We teach families the 'four moments' so kids learn time management and accountability
- Automatic buffer calculation: travel time, prep time, arrival time. Families know exactly when to leave
- Voice input: hands-free for busy parents
- Weather-aware alerts: 'bring an extra layer' or 'game might cancel due to lightning'
- Consumer-first design: parents actually want to use it, which is what makes the partnership work
- Partner economics: zero cost to the organization, recurring revenue back on every paid family subscription
- White-label: organizations can run it on their own domain so it feels like their own product
- Enterprise infrastructure: twenty years scaling. We don't break under tournament load
The line I'd hand a rep when TeamSnap comes up
"TeamSnap is solid. They got to market first. But here is what is different with us: first, we are not just moving events around. We teach Time Literacy. Your kids actually learn something. Second, we do not just schedule. We calculate travel time, prep time, arrival time. Families know exactly when to leave. Third, we are built for families first, which is what makes the partnership economics work. You introduce us to your community at no cost, and you earn recurring revenue back on every family that subscribes. That is a model TeamSnap cannot give you."
Section 2
The five objections I'd train against
These five come up in almost every cycle. I'd script them, role-play them weekly, and refuse to wing them in real calls.
"We already use TeamSnap / TeamLinkt"
"I get that. TeamSnap is solid for basic scheduling. But are your families actually using it? Are parents still missing updates? Are coaches still coordinating in GroupMe? What if there was a platform families would want to use, where they actually learned something about time, where they got travel-time alerts, where updates came through naturally, and you earned recurring revenue on every paid subscription instead of paying a software bill? That is different. And you could white-label it so it feels like your organization. Can I show you a quick example?"
"We don't have budget for another tool"
"Good. You don't need any. This isn't a software purchase. The partnership costs your organization nothing. We give your families access to Orgo, you help us introduce it, and you earn recurring revenue on every paid family subscription. So instead of a new line item, you'd be adding a new revenue line and a better experience for your members at the same time. Worth walking through how the partner economics work?"
"We'd need board / admin signoff"
"That makes sense. A new family-facing tool always deserves board visibility, even when there's no cost. What if I prepared a short brief for the board focused on family retention, the partner revenue line, and what we're asking families to install? And I can do a separate IT review focused on security and integration. Would that help move this forward?"
"We're not ready to introduce a new tool right now"
"Got it. You might be in the middle of something. But let me ask: when would be a good time to revisit? Off-season? Before next year's planning? I would love to stay in touch. Maybe a quick pilot with one team this off-season, no cost, no pressure, just to see how your families respond. Would that interest you?"
"Parents won't want to download another app"
"That is a fair concern. And you are right, parents hate apps. But here is what we see: when parents use Orgo, they keep using it. Why? Because it actually works. Travel times are calculated. Packing alerts come through. Updates hit them at the right time. It is not just scheduling. It is family peace of mind. I have talked to dozens of parents who told us they love it because it gives them one less thing to think about during the week. Can I show you a few testimonials?"
Section 3
The discovery questions I'd require
No demo gets booked without answers to at least six of these. This is what separates a qualified opp from a hopeful one.
- Tell me about the organizational structure. How many people are involved in scheduling and communication?
- How many teams are you managing? How many families? What age groups?
- Walk me through a typical week. When do you send out updates? How do you send them?
- How do you know families actually got the message? Do you get confirmation?
- What happens when you need to send an urgent update, like a weather cancellation?
- What are you hearing from parents about the coordination experience?
- Are you losing families to other organizations? If so, why?
- How much time per week do you spend on coordination? Your coaches? Your volunteers?
- What tools are you currently using? Email? Spreadsheets? GroupMe? WhatsApp?
- If you could solve one operational problem, what would it be?
- What would need to happen for you to consider a new solution?
Section 4
How I'd use pilots as a closing tool
Pilots are a closing mechanism, not a stalling tactic. The structure is what makes the difference.
What I'd offer
- Free 30–60 day pilot scoped to one team or one age group
- Full feature access. No limitations
- Dedicated onboarding support
- Pre-agreed success metrics, written down before the pilot starts
The pitch I'd use
"Here is what I propose. No risk. Pick one team to run with Orgo for the next season. Let families experience it. Measure parent satisfaction, communication effectiveness, and your coordination time. If it works, you roll it out. If it does not, you walk away. No long-term commitment. Just proof."
Rule
If we can't write the success metrics down on the call, it's not a pilot; it's a stall. Walk away or push to a real proposal.