Momentum & Social Proof Emails
Overview
Between your announcement and race day, the goal is simple: make it feel like everyone is joining. Momentum and social proof drive signups more than explanations ever will. Send these 2–3 weeks before the race starts.
These messages should be short — one number, one comparison, one link. Mix and match the variants below depending on what data you have.
Base Template (Rivalry Update)
To: All staff
Subject: [X] people registered — can we hit [round number] by [date]?
Quick update: [X] people across [X] teams have signed up for [Challenge Name].
[Department A] has [X] racers. [Department B] has [X]. [Department C]… still looking for a captain.
The challenge starts [date]. Register here: [link]
Registration Milestone
To: All staff
Subject: We just hit [round number] signups for [Challenge Name]!
[X] people have signed up for [Challenge Name] — and registration is still open.
Can we hit [next round number] before [date]? If you haven’t joined yet, there’s still time: [link]
Captain / Team Spotlight
To: All staff
Subject: Meet your [Challenge Name] team captains
[Captain Name] from [Department] is leading [Team Name] — and they already have [X] members.
“[Short quote from captain — e.g., ‘I’m not a runner but I walk every morning. This is going to be fun.’]”
[X] teams are forming for [Challenge Name]. Join an existing team or start your own: [link]
Slack / Teams version:
Shoutout to [Captain Name] — [Team Name] already has [X] members for [Challenge Name]. [Department] is bringing it. Who else is in? [link]
Tips
- Keep each message to 2–3 sentences. These are momentum nudges, not announcements.
- Include one number. Registration count, team count, or department standing — pick the most impressive one.
- Department rivalries work. “Sales has 3 teams. Engineering has 1. Just saying.” drives more signups than any incentive.
- Repeat the link every time. People need to see it 3–5 times before they act.
- Visuals get attention. A screenshot of the race map with avatars is more compelling than any paragraph of text.
- Mix channels. Send one via email, post the next on Slack, share the bib preview on Teams. Don’t repeat the same message on the same channel.
Contact support if you have questions.