Weekly White-Label Partner Newsletter

Audience: white-label partners only (153 active subdomains as of send time)

Format: TEMPLATE for a recurring weekly newsletter

Cadence: Tuesdays at 9am ET

Sender: {partner_program_lead} (currently routes to the partner team alias)

Length: ~600 words populated, structured for skim-and-deep-read

SECTION 01Subject line (rotate by week tone)

• WL Partner Brief: {short_headline} ({mm_dd})
• WL Brief: {short_headline}
• WL Weekly: {short_headline}

The {short_headline} is the single most important thing in the newsletter, written as a phrase. Examples: "voice-mismatch detection now live for all partners," "the three audience tweaks that lifted Q1 partner show rates by 14%," "Sarah's panel at the Tampa partner summit is open for sign-ups."

SECTION 02Email body template

Hey {partner_first_name},

This is your Tuesday brief. Skim what is relevant, jump on anything that needs your attention this week.

This week's product changes

{product_changes_intro_sentence}

• {change_1_title}: {change_1_one_liner}. {change_1_action_for_partner}.
• {change_2_title}: {change_2_one_liner}. {change_2_action_for_partner}.
• {change_3_title}: {change_3_one_liner}. {change_3_action_for_partner}.

Full release notes for partners are at {partner_changelog_url}. The customer-facing changelog (do not link your end clients to the internal one) is at {public_changelog_url}.

If any of this week's changes affect a feature you have customized in your white-label, the migration notes are flagged in the partner changelog with a yellow tag. Anything not flagged is fully backward compatible with your existing setup.

Market intel

{market_intel_intro_sentence}

The signal we are watching this week: {market_signal_description}

What it means for your campaigns: {market_signal_implication}

What we are testing in response: {market_signal_test}

A few partner data points from the last 7 days that are worth knowing:

• Median partner acceptance rate this week: {median_acceptance_rate}% (last week: {prev_week_acceptance_rate}%)
• Median partner reply rate: {median_reply_rate}%
• Top-performing audience filter combination across the network: {top_audience_combo}
• Worst-performing opener template (deprecated this week): "{deprecated_opener_snippet}..."

If you are still using the deprecated opener, swap it. Replacements are in the message library at {message_library_url}.

Partner spotlight

{partner_spotlight_intro_sentence}

This week we are featuring {spotlighted_partner_name} at {spotlighted_partner_company}.

The win: {spotlight_win_description}

The play: {spotlight_play_description}

The lesson for the network: {spotlight_lesson}

If you want to talk to {spotlighted_partner_name} directly about how they ran this, they have agreed to take three intros from other partners this month. Reply to this email and we will make the connection.

(If you have a result you would like featured here, send it our way. The bar is "would another partner learn something from this." It does not need to be a record-breaking number.)

Training assets

New this week in the partner training library:

• {training_1_title} ({training_1_format}, {training_1_length}): {training_1_one_liner}. Open
• {training_2_title} ({training_2_format}, {training_2_length}): {training_2_one_liner}. Open
• {training_3_title} ({training_3_format}, {training_3_length}): {training_3_one_liner}. Open

Reminder that everything in the partner training library is white-labelable. You can drop the videos into your own client portal with your branding. The Loom embeds use a partner-aware viewer that swaps logos based on your subdomain. Setup instructions are at {whitelabel_video_setup_url}.

The two highest-watched videos across the network last week were {top_video_1} and {top_video_2}. Worth a look if you have not seen them.

Partner office hours

The next bi-weekly partner office hours are on {office_hours_date} at {office_hours_time_et} ET. Open agenda this round, no set topic. Last session we ended up spending 40 minutes on the new audience pruning rules and the rest on partner Q&A.

If you have a topic you want covered, reply to this email and we will add it to the agenda. If you want to attend silently and just listen, that is fine too. About a third of the partners on the call never unmute and it is a perfectly valid way to participate.

Add the office hours to your calendar

Heads up for next week

A few things on the radar that are not changes yet but might affect your week ahead:

• {heads_up_1}
• {heads_up_2}
• {heads_up_3}

We will go deeper on any of these in next week's brief if they progress.

Questions, ideas, complaints

Reply directly to this email. Every reply gets read by a human within 24 hours, usually within 4. If you want to escalate something urgent (campaign down, partner client emergency), the on-call partner support number is in your partner dashboard.

Talk Tuesday.

{partner_program_lead} {partner_program_lead_title}

Partner dashboard | Partner training library | Partner changelog

SECTION 03Auto-population mapping (engineering reference)

SECTION 04Editorial rules

No filler. If there are no real product changes this week, say "no breaking changes this week, here is what is in flight" and skip the bullet list. Manufactured updates erode trust faster than a thin email does.

Anonymize partner data. Median network metrics are fine to share. Specific partner numbers are not, unless that partner has explicitly opted in (the spotlight section is the only place named partners appear).

One CTA only at the bottom. The newsletter naturally has multiple links because of the structure. The single bottom-of-email "do this thing" is the office hours sign-up. Resist adding a second primary CTA.

Length cap: 600 words. Skimmable in 90 seconds. The detail lives behind the links. If a section is running long, push the depth into a partner-only doc and link to it.

No emoji, no exclamation points. This is a B2B partner newsletter. The tone is "smart colleague writing to smart colleague," not "marketing team trying to get clicks."

Partner-only language. The newsletter regularly references things partners' end clients should not see. Use "your clients" not "the customer." Use "white-label" not "platform." Treat the reader as a peer who runs a business, not as a user.

SECTION 05Send checklist

• [ ] Headline written and tested (does the email subject earn the open from a busy partner?)
• [ ] Product changes pulled from release log and one-lined
• [ ] Market intel section has real signal (no filler)
• [ ] Partner spotlight subject confirmed and intro reviewed
• [ ] Training assets section reflects current week's adds
• [ ] Office hours date/time correct
• [ ] All links resolve (404 check before send)
• [ ] Length under 600 words
• [ ] Test send to partner team alias for review
• [ ] Send Tuesday 9am ET

SECTION 06Failure modes to avoid

The newsletter dies in three ways. Watch for each.

Death by sameness. If three weeks in a row the partner spotlight, market intel, and product changes all sound like the same kind of update, partners stop opening. Vary the angles. One week lead with a tactical play, next week lead with a market shift, next with a tooling announcement.

Death by promotion. The newsletter is not a place to push partners to upsell their clients. The moment it starts feeling like marketing-to-the-marketers, the open rate drops. The job is to make their week of running campaigns easier and more informed. The promotion happens because they trust us, not because we promote.

Death by silence. If we skip a week, partners notice. We have skipped only twice in the last two years and both times we got concerned replies. The cadence is part of the contract. Even a 200-word "quiet week, here is what is on the roadmap" beats a missed Tuesday.