Orgo · Operating Playbook
Edition Q2 FY26
Chapter 00 · Opening

How I'd Build Orgo's Partnership Motion

This isn't a generic sales playbook. It's how I'd attack the youth sports market for Orgo specifically: the partner segments I'd start with, the scripts I'd put in BDRs' hands, the GTM motion I'd run week one, and the pipeline math that ties partnership signups to family adoption and recurring revenue.

Orgo
Edition Q2 FY26
Section 00

Why I built this document

The ask, restated

You asked to see an example of a script or a GTM motion that's specific to Orgo and us, not a textbook framework. You wanted to visualize the "how" so you could see how I'm interpreting the opportunity. That's what this document is. Every chapter is a piece of the motion I'd actually run, with the artifacts I'd actually use.

How I'm reading the opportunity

Orgo isn't another scheduling app, and it isn't another piece of software a director has to find budget for. The wedge is Time Literacy plus enterprise-grade infrastructure, distributed through partner organizations that already have trust with families. The partner introduces Orgo to their community at no cost, helps drive adoption, and earns recurring revenue back on every paid family subscription. That model changes who I talk to, how I open the conversation, and what I anchor every motion to. I'm not going to run a generic outbound playbook against a generic "youth sports" TAM. I'm going to run a segmented, partner-led motion with scripts written for the four partner archetypes that actually drive adoption.

What's in here

  • Ch 01. The Partners: the partner profile I'd lock onto in the first 90 days and the segments I'd deprioritize.
  • Ch 02. Problem & Triggers: the specific pain I'd anchor every conversation to, and the signals that say a partner is ready.
  • Ch 03. Outreach & Stakeholders: the opening scripts I'd hand a BDR on day one, by segment.
  • Ch 03b. Worked Example: one named partner, 14 days, every artifact.
  • Ch 04. Sales Execution: how I'd position against TeamSnap, handle the five objections we'll hear most, and use pilots to prove adoption.
  • Ch 05. Pipeline & Daily Execution: the stage definitions and daily rhythm I'd hold the team to.
  • Ch 06. Partnership Cycles: the timelines I'd plan capacity against.
  • Ch 07. Pipeline & Revenue Plan: the month-by-month math that ties partner signups to family adoption to MRR.
  • Ch 08. What I'd Want to Talk About Next: the questions whose answers would change how I'd run month one.
Bottom line
If you read one chapter, read Chapter 03b. That's where the "how" is most visible: a named prospect, a real motion, every artifact. Then jump to Chapter 08 for what I'd want to talk about next.