Partner Tracker: Why Rep-Level Tracking Matters

Purpose: Explain the reasoning behind rep-level tracking before building the final schema
Date: January 2025


🎯 The Core Problem Steve Identified

“The hardest part about the partner channel isn’t building the relationships, it’s building the relationships with effective sellers.”

Key insight: Not all reps are created equal. You have:

  • “Jordans” (high-quality reps): Proactively share account lists, make introductions, suggest joint activities
  • Time-wasters: Multiple meetings with no action, expect you to bring everything, “tell me when you have a deal”

If you treat all reps the same:

  • You waste time on reps who won’t bring you into deals
  • You under-invest in reps who will
  • You can’t optimize your outreach (what works for Tier 1 doesn’t work for Tier 4)

📊 Why Rep-Level Tracking (Even if Lightweight)

1. Different Reps Need Different Cadences

Tier 1 Rep (Active Deals):

  • Cadence: Weekly
  • Focus: Deal support, account research for active deals
  • If you don’t track this, you’ll miss weekly check-ins and deals will stall

Tier 4 Rep (Stale):

  • Cadence: Quarterly
  • Focus: Re-engagement or deprioritize
  • If you don’t track this, you’ll waste time on monthly outreach that gets ignored

Without rep-level tracking: You either over-communicate (waste time) or under-communicate (miss opportunities).


2. You Need to Identify “Jordans” vs. Time-Wasters

Steve’s insight:

“The hardest part about the partner channel isn’t building the relationships, it’s building the relationships with effective sellers.”

Signs of a “Jordan” (high-quality rep):

  • ✅ Proactively shares account list
  • ✅ Suggests joint marketing activities
  • ✅ Makes introductions without requiring proof first
  • ✅ Responsive and engaged

Signs of a time-waster:

  • ❌ Multiple meetings still “building rapport”
  • ❌ Lip service but no action
  • ❌ Expects you to bring everything, offers nothing
  • ❌ “Tell me when you have a deal”

Without rep-level tracking: You can’t identify which reps to focus on. You’ll spend equal time on Jordans and time-wasters.


3. Response Rates and Collateral Usage Vary by Rep

Example:

  • Rep A: 80% response rate, uses all collateral → Tier 1, weekly cadence
  • Rep B: 20% response rate, never uses collateral → Tier 4, quarterly cadence

If you only track aggregate:

  • You see “50% average response rate” (useless)
  • You don’t know Rep A needs weekly attention
  • You don’t know Rep B should be deprioritized

With rep-level tracking:

  • You know Rep A is a Jordan → focus energy here
  • You know Rep B is stale → deprioritize

4. Action Planning Requires Rep-Level Context

Monday morning question: “Who do I need to follow up with this week?”

With aggregate tracking:

  • “Snowflake needs follow-up” (not actionable - which rep? what action?)

With rep-level tracking:

  • “Jarred Clifford (Snowflake) - Next Action: 2/4/2026 - Follow-up on account lists” (actionable)

Without rep-level tracking: You can’t prioritize daily work. You’re guessing.


🤔 But You’re Right: It Can Be Lighter-Weight

The key insight: You don’t need 27 columns in a Google Sheet if HubSpot is your source of truth for detailed rep data.

What you DO need in the sheet:

  1. Partner company-level metrics (aggregate)
  2. Rep engagement summary (high-level, not detailed)
  3. Action planning (who to contact, when, why)

What can live in HubSpot:

  • Detailed rep contact info
  • Full activity history
  • Response rate calculations
  • Collateral tracking
  • Meeting notes

💡 Proposed Lightweight Approach

One sheet: Partner Companies

Columns:

  1. Partner Company Name
  2. Partner Type
  3. Industry
  4. Confidence (1-3)
  5. HYPE (1-3)
  6. Relationship
  7. Origin Story
  8. Slack Channel
  9. Hyperscaler Association
  10. Partner Program Status
  11. Partner Manager Name/Email
  12. Last Engagement Date
  13. Deal Size
  14. Active Reps Count (calculated from HubSpot)
  15. Tier 1 Reps (count, names in notes)
  16. Tier 2 Reps (count, names in notes)
  17. Tier 3 Reps (count, names in notes)
  18. Tier 4 Reps (count, names in notes)
  19. Next Action (highest priority action across all reps)
  20. Next Action Date (earliest next action date)
  21. Next Action Rep (which rep needs attention)
  22. Leads Generated (aggregate)
  23. Closed/Won Deals (aggregate)
  24. Current Phase
  25. Phase Date
  26. HubSpot Link
  27. Notion Link
  28. Notes (can include rep names and brief context)

How it works:

  • Sheet = high-level view, action planning
  • HubSpot = detailed rep tracking, activity history
  • Weekly review: Check HubSpot for rep details, update sheet with aggregate metrics and next actions

Option B: Two Sheets (Company + Rep Summary)

Sheet 1: Partner Companies (same as current, with aggregate metrics)

Sheet 2: Rep Summary (lightweight - 10-12 columns max)

  1. Rep Name
  2. Partner Company
  3. Engagement Tier ⭐
  4. Rep Quality Score ⭐ (1-10)
  5. Last Contact Date
  6. Next Action Date ⭐
  7. Next Action Type ⭐
  8. Introductions Made (count)
  9. Response Rate (calculated)
  10. Notes (brief context)

How it works:

  • Sheet 2 = quick rep overview, action planning
  • HubSpot = detailed tracking
  • Daily: Check Sheet 2 for “Next Action Date < Today”
  • Weekly: Review HubSpot for details, update Sheet 2

🎯 Recommendation: Option A (Single Sheet with Rep Summary)

Why:

  • ✅ One sheet to maintain (easier for one-person team)
  • ✅ Focus on aggregate metrics (what you need for reviews)
  • ✅ Action planning built in (Next Action Date/Type/Rep)
  • ✅ HubSpot handles detailed rep tracking (where it belongs)

What you track in the sheet:

  • Partner company metrics (aggregate)
  • Rep engagement summary (Tier counts, next actions)
  • Action planning (who to contact, when, why)

What you track in HubSpot:

  • Detailed rep contact info
  • Full activity history
  • Response rates
  • Collateral usage
  • Meeting notes
  • Engagement signals

Workflow:

  1. Daily: Check sheet “Next Action Date” column → see who needs attention
  2. Weekly: Review HubSpot for rep details → update sheet with aggregate metrics
  3. Monthly: Review tier movements in HubSpot → update tier counts in sheet

📊 What You Get vs. What You Give Up

What You Get (Even Lightweight):

  • ✅ Action planning (know who to contact, when)
  • ✅ Tier-based prioritization (focus on Tier 1, deprioritize Tier 4)
  • ✅ Aggregate metrics (for reviews and reporting)
  • ✅ Rep engagement summary (without detailed tracking)

What You Give Up (vs. Full 3-Sheet System):

  • ❌ Detailed rep tracking in sheets (but HubSpot has this)
  • ❌ Individual rep metrics in sheets (but HubSpot has this)
  • ❌ Full activity history in sheets (but HubSpot has this)

Net result: You get 80% of the value with 20% of the complexity.


🎓 The Steve Quote That Matters

“The hardest part about the partner channel isn’t building the relationships, it’s building the relationships with effective sellers.”

Translation: You need to know which reps are effective (Jordans) vs. ineffective (time-wasters), and you need different cadences for each.

Minimum viable tracking:

  • Tier per rep (in HubSpot)
  • Next Action Date/Type per rep (in HubSpot or sheet)
  • Aggregate tier counts (in sheet for quick view)

You don’t need:

  • 27 columns per rep in a sheet
  • Full activity history in sheets
  • Detailed metrics in sheets (HubSpot is better for this)

✅ Final Recommendation

Single Sheet: Partner Companies with:

  • Company-level metrics (what you have now)
  • Rep engagement summary (Tier counts, Next Action Date/Type/Rep)
  • Action planning (who to contact, when, why)

HubSpot:

  • Detailed rep tracking (tiers, quality scores, activity history)
  • Response rates, collateral usage
  • Full contact management

Workflow:

  • Sheet = daily action planning, aggregate metrics
  • HubSpot = detailed rep management, activity tracking
  • Weekly sync: Update sheet from HubSpot data

Result: Lightweight sheet for action planning + HubSpot for detailed tracking = best of both worlds.


Next Step: Should I build the lightweight single-sheet schema based on this approach?