================================================================================ PARTNERNOMICS TAGS TAXONOMY Module 7: System Scanner Pipeline ================================================================================ Complete reference for all tags used across the system. Tags help organize plays by context, and enable quick filtering in the play library. ================================================================================ SITUATION TAGS (Where in the partnership lifecycle) ================================================================================ Purpose: Identify which stage(s) of the partnership journey a play supports. Use these to find content relevant to your current phase. Tag Slugs: ────────── program-launch When you use it: In the early phase before you've signed any partners What it means: Building program foundation, strategy, and readiness Common plays: Plays in Playbooks 1-4 (Plan Your Program section) Guidance: Run these plays first if you're starting from scratch partner-recruitment When you use it: Once your program foundation is ready and you're hunting for partners What it means: Sourcing, evaluating, and qualifying potential partners Common plays: Plays in Playbook 5 (Partner Candidate Identification) Guidance: Use when you've completed PB1-4 gate deal-negotiation When you use it: Once you have shortlisted candidates and are negotiating terms What it means: Discussing structure, terms, contracts, and reaching agreement Common plays: Plays in Playbook 7 (Partnership Agreement Negotiation) Guidance: Use after partner evaluation (PB6) is complete partnership-activation When you use it: After agreement is signed, you're preparing for launch What it means: Building the launch plan, defining roles, setting up systems Common plays: Plays in Playbook 8 (First 90-Days Plan Launch) Guidance: Run immediately after partnership agreement is signed ongoing-management When you use it: Month 2+ of a partnership, running regular check-ins What it means: Monthly partner business reviews, scorecard tracking, health monitoring Common plays: Plays in Playbook 9 (Partner Business Reviews) Guidance: Establish this rhythm by Month 1 performance-review When you use it: Quarterly or annual assessments of partnership and program health What it means: Analyzing data, identifying trends, making optimization decisions Common plays: Plays in Playbook 10 (Performance Tracking & Optimization) Guidance: Run quarterly in your PBR meetings joint-selling When you use it: During execution phase when you're co-marketing or co-selling with partners What it means: Joint campaigns, co-branded content, coordinated go-to-market activities Common plays: Select plays in Playbook 10 (Scale & Optimize section) Guidance: Use once partnership is activated and performing implementor-engagement When you use it: When a service or implementation partner is involved in customer delivery What it means: Co-delivery planning, RACI definition, client onboarding Common plays: Play G5 (Service Partner Implementation Plan) Guidance: Use only for Service/Implementation partnership types Summary: 8 SITUATION tags Typical playbook coverage: Each play has 1-2 situation tags ================================================================================ AUDIENCE TAGS (Who is using this play) ================================================================================ Purpose: Target content to the right role in your organization. Use these to find plays that match your job title and responsibilities. Tag Slugs: ────────── cro-executive Role: Chief Revenue Officer What they do: Sets overall partnership strategy, reports to board When they use it: Program planning, goal-setting, quarterly reviews Example plays: D1 (Partnership Context), PB3 (Strategic Partnering Plan) Guidance: These plays help you align the organization and make GO/NO-GO decisions vp-partnerships Role: VP of Partnerships or Head of Channels What they do: Day-to-day leadership of partnership program, owner of strategy When they use it: Almost every phase; these are "your" plays Example plays: Most plays across Playbooks 1-10 Guidance: You'll use plays from every section; these are your primary tools partnership-manager Role: Partnership Manager or Partnership Lead What they do: Manage individual partnerships, run PBRs, track metrics When they use it: Partner recruitment, evaluation, ongoing management Example plays: Sourcing plays, PBR plays, performance tracking Guidance: These plays help you execute relationships and keep partnerships on track deal-negotiator Role: Business Development Manager or Partnership Account Executive What they do: Hunt for partners, evaluate fit, negotiate deals When they use it: Candidate sourcing, evaluation, negotiation phases Example plays: Plays in Playbooks 5-7 Guidance: Use these when you're in active deal pursuit program-analyst Role: Partnership Operations or Analytics role What they do: Build dashboards, track metrics, report performance When they use it: Performance tracking, quarterly reporting, data analysis Example plays: Plays in Playbook 10 (Performance Tracking & Optimization) Guidance: These plays help you build the measurement infrastructure implementation-lead Role: Director of Implementation or Solutions Architect (when managing service partners) What they do: Oversee delivery, client success, resource coordination When they use it: Service partner onboarding, client delivery planning Example plays: Play G5 (Service Partner Implementation Plan) Guidance: Use when a service partnership needs a 90-day delivery plan partner-marketer Role: Partner Marketing Manager or Co-Marketing Manager What they do: Create co-branded content, run joint campaigns, manage partner enablement When they use it: Post-launch, once partnerships are generating activity Example plays: Plays in Playbook 10 (Scale & Optimize section) Guidance: These plays help you build joint go-to-market activities sales-leader Role: VP of Sales, Sales Director What they do: Coach sales team on partner sourcing, review partner pipeline quality When they use it: Partner recruitment (defining ICP), partner evaluation, PBRs Example plays: Plays in Playbooks 1-2 (ICP definition), Playbook 6 (evaluation) Guidance: Use these to align sales on partner targets and partnership expectations Summary: 8 AUDIENCE tags Typical play coverage: Each play has 1-2 audience tags ================================================================================ OUTPUT TYPE TAGS (What gets created) ================================================================================ Purpose: Understand what deliverable or artifact a play produces. Use these if you need a specific document type. Tag Slugs: ────────── strategy-briefs What it is: Short strategic documents that make the case for a decision Length: 2-3 pages typically When you need it: When you're presenting to leadership or aligning the team Example plays: Partnership Context play, Strategic Partnering Plan play Guidance: These are meant to be read, discussed, and approved by leadership scorecards What it is: Evaluation tools that score partners against criteria Length: Varies, but typically checklist or spreadsheet format When you need it: When you're evaluating and comparing partner candidates Example plays: Partner Scoring plays, Readiness assessment Guidance: Use to apply consistent, objective criteria across all evaluations templates What it is: Reusable formats that you customize for each partner or situation Length: Document templates, 1-5 pages typically When you need it: When you need a consistent structure across multiple partnerships Example plays: Term Sheet template, First 90-Days Plan template Guidance: Build the template once, then customize it for each partner plans-calendars What it is: Action plans with timelines and milestones Length: 3-5 pages typically When you need it: When you're defining what needs to happen and when Example plays: First 90-Days Plan, Negotiation Matrix Guidance: Share these with partners so everyone understands the cadence dashboards What it is: Visual representations of data and metrics over time Format: Spreadsheet, tool-based, or visual presentation When you need it: When you need ongoing visibility into performance Example plays: Performance Tracking dashboard, PBR scorecard Guidance: Build these once, update them regularly (weekly or monthly) checklists What it is: Task lists that help you make sure nothing falls through the cracks Length: 1-2 pages typically When you need it: When you're managing a process with many steps Example plays: Onboarding checklist in First 90-Days Plan Guidance: Assign owners and deadlines to each item presentations What it is: Slide decks or pitch materials Format: PowerPoint or other presentation tool When you need it: When you're pitching a partnership opportunity to a partner or leadership Example plays: Partnership positioning presentation Guidance: Tailor these to your audience and keep them concise reports What it is: Detailed analysis documents and findings Length: 5-10 pages typically When you need it: When you're synthesizing performance data or program health Example plays: Quarterly Leadership Report, Case Study documents Guidance: These tell the story of program performance to leadership scripts What it is: Conversation guides and question frameworks Format: Bulleted or narrative format When you need it: When you're preparing for a conversation and want talking points Example plays: Discovery Call Script, Objection Preparation script Guidance: Use these to stay on track and hit key talking points one-pagers What it is: Single-page summaries of key information Length: Exactly 1 page (front or front/back) When you need it: When you need a quick-reference document Example plays: One-pager for co-branded opportunity Guidance: These are meant to be scannable in 2-3 minutes Summary: 10 OUTPUT TYPE tags Typical play coverage: Each play produces 1-2 output types ================================================================================ GOAL TAGS (What the user is trying to accomplish) ================================================================================ Purpose: Identify plays that support your specific objective. Use these if you know what you're trying to achieve. Tag Slugs: ────────── build-program Goal: Design and establish your partnership program foundation What it includes: Customer definition, partner definition, strategy, offer structure Timeline: Weeks 1-4 typically (Playbooks 1-4) Success looks like: Program foundation complete, ready to recruit Example plays: ICP definition, Strategic Partnering Plan Guidance: Do this phase first, before talking to any partners recruit-partners Goal: Find and qualify 20+ potential partners from your target market What it includes: Sourcing from multiple channels, initial conversations, scoring Timeline: Weeks 5-8 typically (Playbook 5-6) Success looks like: Shortlist of 5-10 high-probability partner candidates Example plays: Candidate generation, Discovery Call Script, Partner Scoring Guidance: Use your IPP and Term Sheet to filter candidates systematically close-deals Goal: Negotiate and sign partnership agreements What it includes: Negotiation planning, deal structure, contract review, sign-off Timeline: Weeks 8-12 typically (Playbook 7) Success looks like: Signed partnership agreements with 2-4 partners Example plays: Negotiation Matrix, Value Trading, Objection Preparation Guidance: Have your Term Sheet ready before starting negotiations launch-partnerships Goal: Activate each signed partnership with a clear launch plan What it includes: Role definition, goals, metrics, communication cadence Timeline: Week 1-2 post-signature (Playbook 8) Success looks like: Partners know exactly what to do, when, and what success looks like Example plays: First 90-Days Plan, Role-Based Pairing Map Guidance: Share the plan with partners 5+ days before kickoff track-performance Goal: Measure what's working and what needs attention What it includes: Dashboard setup, metric tracking, monthly and quarterly reviews Timeline: Ongoing starting Month 1 (Playbook 9-10) Success looks like: Team has data visibility into program health weekly/monthly Example plays: Performance Tracking Dashboard, PBR agenda, health summary Guidance: Start tracking from Day 1, not after 6 months scale-program Goal: Grow the program from 2-4 partners to 8-10+ partners What it includes: Optimization based on data, second-wave recruiting, success multiplication Timeline: Months 6-12 (Playbook 10) Success looks like: 8-10 active partners generating revenue, repeatable playbook Example plays: Optimization Recommendations, Quarterly Leadership Report Guidance: Use performance data to decide what to do more of align-internally Goal: Get everyone in the organization on the same page about partnerships What it includes: Leadership alignment, stakeholder communication, expectation-setting Timeline: Ongoing, especially in program planning phase Success looks like: Sales, marketing, ops, and leadership all understand strategy Example plays: Partnership Context, Strategic Partnering Plan Guidance: These plays help you facilitate alignment conversations choose-type Goal: Decide which type of partnership model(s) to pursue What it includes: Analysis of business context, decision frameworks, model comparison Timeline: Early in program planning (Playbook 1) Success looks like: Leadership agreed on partnership type(s) to pursue Example plays: Partnership Type Decision Tree, Business Case Comparison Guidance: Don't skip this; it shapes everything downstream Summary: 8 GOAL tags Typical play coverage: Each play supports 1-2 goal areas ================================================================================ EFFORT TAGS (How much time/investment this takes) ================================================================================ Purpose: Manage your capacity and plan your timeline. Use these to understand the effort required for a play. Tag Slugs: ────────── quick-win Time investment: 30 minutes to 2 hours for the person running the play Typical team time: 1-2 hours of coordination When to use it: When you need something fast or have limited bandwidth Example plays: Co-branded one-pager, Discovery Call Script review Guidance: These are meant to be fast; don't over-engineer deep-work Time investment: 4-8 hours for the person running the play Typical team time: 8-20 hours total (including team input) When to use it: When you have the time and want a thorough, well-researched result Example plays: ICP Reverse-Engineering, Strategic Partnering Plan, First 90-Days Plan Guidance: Block time on calendar; don't try to do these in between meetings ongoing-series Time investment: Ongoing, recurring activity (usually monthly or quarterly) Typical team time: 2-4 hours per cycle When to use it: These are standard operating procedures, not one-time projects Example plays: Partner Business Reviews, Performance tracking, quarterly reporting Guidance: Build these into your regular calendar rhythm Summary: 3 EFFORT tags Typical play coverage: Each play is tagged with exactly 1 effort level ================================================================================ ROLE TAGS (Who in the organization this is designed for) ================================================================================ Purpose: Identify the organizational role that should own or lead a play. Use these if you want to know who should be accountable for this work. Tag Slugs: ────────── partnership-leader Role: VP of Partnerships, Head of Channels, VP of Alliances What they own: Full partnership program strategy, execution, team What they lead: Most plays across all playbooks Example plays: Nearly all plays have this tag Guidance: If you're in this role, you're the primary consumer of the system partnership-manager Role: Partnership Manager, Channel Manager, Account Manager (for partners) What they own: Individual partner relationships, day-to-day execution What they lead: Partner-specific plays, PBRs, relationship management Example plays: Plays in Playbooks 5-9 (recruiting through management) Guidance: These are your core operating tools; use them weekly implementation-lead Role: Director of Implementation, Solutions Architect, Delivery Manager What they own: Partner onboarding, co-delivery, customer success What they lead: Service partner plays, client delivery planning Example plays: Service Partner Implementation Plan, Co-delivery coordination Guidance: Use if your partnership involves co-delivery or implementation sales-team-member Role: Sales Director, VP Sales, Sales rep (working with partners) What they own: Partner sourcing, pipeline qualification, closed deals with partners What they lead: Plays related to partner prospecting and closing Example plays: Partner Sourcing plays, Discovery Call Script Guidance: These help sales team understand partner priorities and sourcing approach marketing-collaborator Role: VP Marketing, Partner Marketing Manager, Content Marketing Manager What they own: Co-marketing initiatives, joint content, brand alignment What they lead: Marketing-specific plays in scale/optimize phase Example plays: Co-marketing plan, co-branded collateral, case study Guidance: Use once partnerships are performing and generating demand executive-sponsor Role: CRO, CEO, CFO (overseeing partnership program) What they own: Strategic alignment, resource allocation, approval authority What they lead: Strategy-level plays, quarterly reviews, GO/NO-GO decisions Example plays: Strategic Partnering Plan, Partnership Context, Quarterly reviews Guidance: These plays help you present partnership performance to leadership Summary: 6 ROLE tags Typical play coverage: Each play targets 1-2 organizational roles ================================================================================ USAGE GUIDANCE ================================================================================ How to use tags in practice: 1. FINDING CONTENT: - Use AUDIENCE tags to find plays for your job title - Use SITUATION tags to find plays for your current phase - Use GOAL tags to find plays that support what you're trying to accomplish - Use OUTPUT TYPE tags if you need a specific document 2. PLANNING YOUR TIMELINE: - Use EFFORT tags to estimate how long plays will take - Use SITUATION tags to understand the sequence (program-launch before partner-recruitment) - Block calendar time based on EFFORT tag guidance 3. DELEGATING WORK: - Use AUDIENCE tags to identify who should own each play - Use ROLE tags to confirm organizational alignment - Share tag information with team members so they understand scope 4. COMMUNICATION: - Use these tags when discussing plays with stakeholders - Tags provide shorthand for common concepts across the system - Share tag descriptions with team to align on terminology ================================================================================ SUMMARY COUNTS ================================================================================ Total Tags: 33 Situation tags: 8 Audience tags: 8 Output Type tags: 10 Goal tags: 8 Effort tags: 3 Role tags: 6 Typical Play Coverage: Each play is tagged with: 1 situation + 1 audience + 1 output type + 1 goal + 1 effort + 1 role = 6 tags Most plays range from 5-7 tags to enable flexible filtering Tag Purpose: - Organize content for easy discovery - Enable quick filtering by role, phase, or goal - Facilitate communication across teams - Support capacity planning and timeline estimation Version: 1.0 Date: 2026-02-12 Status: Complete ================================================================================ END OF TAGS TAXONOMY ================================================================================