partnership-messaging-queue-template

Partnership Messaging Queue Template (EA Handoff)

Use this document to convert the weekly partner pulse into a single execution list your EA can run without founder intervention.

Purpose

• Turn partner status into executable outbound actions.
• Ensure every active partner has a clear next message owner, timing, and success criteria.
• Create one weekly source of truth for messaging execution and follow-up.

Inputs required before starting

1. Latest pulse draft in knowledge/sales/partnerships/ops/drafts/.
2. Latest PARTNER_CONTROL_CENTER.md for each active partner.
3. Recent activity evidence (Gmail, Slack, HubSpot/manual) if available.
4. Active partner tiers for the week (Gold/Silver/Bronze/Calibration).

Weekly run cadence

• Build queue: Monday morning.
• Execute first-touch messages: Monday-Tuesday.
• Execute follow-ups: Wednesday-Thursday.
• Weekly closeout update in #sales-partnerships: Friday.

Handoff operating rules (EA)

1. Do not change partner tier in this document; only execute against current tier.
2. Do not send partner messages without an owner recorded in Execution logistics (below the main queue).
3. Keep one primary channel per row (email or Slack or LinkedIn), not multiple.
4. If no response by the fallback date, execute fallback step exactly as written in logistics.
5. Log sent messages and outcomes in Execution logistics the same day (status + evidence link).
6. Escalate to Robert only on blocked rows marked Escalate = Yes in logistics.

Queue status definitions

• Queued: Ready to send, not yet sent.
• Sent: Initial message sent.
• Waiting: Sent and waiting for partner response.
• Follow-up Sent: Follow-up sent after no response.
• Response Received: Partner replied; next step required.
• Blocked: Cannot proceed without decision/input.
• Closed: Action completed for this week.

Weekly queue header

Field	Value
Week of	[YYYY-MM-DD]
Prepared by	[EA name]
Source pulse file	[path to markdown draft]
Slack summary thread	[link to sales-partnerships thread]
Last updated	[YYYY-MM-DD HH:MM TZ]

Execution queue (copy this table each week)

Keep this table narrow: strategy and copy context only. Put dates, owner, and status in Execution logistics.

Partner	Tier	Objective	Channel	Audience	Message type	Draft location	Success criteria
[Snowflake]	[Gold]	[Book PM sync + confirm AE brief format]	[Email]	[Where it lands: e.g. Partner Manager thread, #channel]	[Nudge]	[path or link to pre-draft]	[What “done” means for this action — tied to the objective]
[Mixpanel]	[Silver]	[Re-open Q2 webinar planning]	[Slack]	[#partnership-mixpanel or named thread]	[Reactivation]	[path or link]	[Date confirmed / owner named]
[MotherDuck]	[Bronze]	[Offer invite-only workshop to 10 accounts]	[Email]	[Partner contact + thread]	[Proposal]	[path or link]	[Partner agrees to pilot scope]

Column guide

• Objective — The outcome this touch should advance (one line).
• Channel — Email vs Slack vs LinkedIn; name the surface (DM, channel post, existing Gmail thread).
• Audience — Exactly where the message must land (Slack channel name, email thread, @person, partner pod).
• Message type — Taxonomy label so sent messages can feed a learning loop (patterns on what works per type).
• Draft location — Pre-drafted copy, control-center section, or doc to pull language from.
• Success criteria — How you know this action succeeded (aligned with the objective, not generic ops).

Execution logistics (optional; copy each week)

Partner	Owner	Send by	Fallback date	Fallback action	Status	Evidence link	Escalate	Notes
[Snowflake]	[EA/Hannah]	[YYYY-MM-DD]	[YYYY-MM-DD]	[2-line follow-up + alt slot]	[Queued]	[link]	[No]	[context]
[Mixpanel]	[Owner]	[YYYY-MM-DD]	[YYYY-MM-DD]	[Escalate in #sales-partnerships]	[Queued]	[link]	[No]	[context]
[MotherDuck]	[Owner]	[YYYY-MM-DD]	[YYYY-MM-DD]	[Low-frequency nurture]	[Queued]	[link]	[No]	[context]

Suggested message-type taxonomy

• Reactivation: Re-open stalled thread with concise context.
• Nudge: Prompt response on an existing ask.
• Proposal: New concrete collaboration ask (event, intro, co-sell).
• Follow-up: Second touch after no response.
• Close-the-loop: Summarize prior action and confirm next step.

Daily update checklist (EA)

1. Update Status in Execution logistics for every row touched today.
2. Add Evidence link for each sent message.
3. Add one-line Notes if partner replied (and adjust Success criteria next week if the goal shifted).
4. Move completed rows to Closed in logistics.

Friday closeout format (post to sales-partnerships)

Use this exact structure:

1. Completed this week: [count]
2. Waiting on partner: [count]
3. Blocked: [count + blockers]
4. Top wins: [1-3 bullets]
5. Top risks next week: [1-3 bullets]
6. Rows needing Robert input: [list partner + decision]

Escalation rules

Escalate only when one of these is true:

• Partner asks for pricing/terms change not already approved.
• New legal/commercial commitment is requested.
• Tier change is recommended.
• Two follow-ups went unanswered and partner is high-priority.

Definition of done each week

• Every active Silver/Bronze partner has at least one executed row (Sent, Waiting, or Response Received).
• All sent rows include evidence links.
• Friday closeout posted in #sales-partnerships.
• Next week’s queue can be prepared without backtracking messages.