stephenrogan Celebration Note Writer
Writes genuine celebration notes that strengthen relationships through specific, personal recognition. The small touch that most CSMs forget -- and the one customers remember longest.
The bar: would the recipient save this note? If it is generic enough to be sent to anyone, it will not be saved, forwarded, or remembered. If it references something specific that shows you are paying attention, it becomes a relationship deposit that compounds over time.
How to Use
Provide:
- Who the note is for (name, role, relationship context)
- What you are celebrating (milestone, achievement, personal event)
- Any specific details that make this celebration personal
- The channel (email, Slack, handwritten note, LinkedIn comment)
- Your relationship depth (close, professional, new)
Celebration Types
Product Milestone
The customer's team achieved something meaningful with your product.
Structure:
- Name the specific achievement (not "great work" but "your team automated 3,000 workflows this quarter")
- Connect it to their goal (show that you remember what they were trying to achieve)
- Acknowledge the people involved (not just the champion -- the team who did the work)
- Optional: forward look (what this achievement enables next)
Example: "Tom -- your analytics team just crossed 3,000 automated report runs this quarter. When we kicked off 9 months ago, the goal was to eliminate the manual weekly reporting cycle. Your team has not just eliminated it -- they have built an entirely new capability on top of it. Real credit to Lisa and the team for driving the adoption. Looking forward to seeing what they build next."
Business Achievement
The customer's company achieved something unrelated to your product.
Structure:
- Reference the specific achievement (funding round, product launch, expansion, award, IPO)
- One sentence on what it means (show you understand their business, not just your product's role in it)
- Brief and genuine -- do not make it about your product
Example: "Congratulations on the Series C, Tom. EUR 40M is a strong signal of what the market thinks of what you are building. Exciting times ahead for the team."
Rules: Keep it short. Do not try to connect their business achievement to your product. A funding announcement is not an expansion conversation.
Personal Achievement
A contact's promotion, new role, award, or personal milestone.
Structure:
- Specific congratulations (name the achievement)
- One sentence on why it is deserved (reference something you have observed about their work)
- Brief. Personal notes should feel personal, not rehearsed
Example: "Congratulations on the VP promotion, Lisa. I have watched you drive the transformation of the analytics function over the past year -- nobody deserves this more. Looking forward to continuing to work together in your new role."
Rules: LinkedIn is usually the right channel for professional milestones. Email is more appropriate for deeper relationships. Never celebrate a promotion if it means the person is leaving your product's scope -- that is a stakeholder change to manage, not a celebration.
Anniversary
Contract anniversary, relationship milestone, or a personal "thank you."
Structure:
- Mark the occasion specifically
- Reference one specific thing from the journey
- Express genuine appreciation (not corporate "we value your partnership")
Example: "Two years since we kicked off the implementation, Tom. I still remember the first week when we could not get the SSO integration to work and your team stayed late three nights running to get it sorted. A long way from there to 3,000 automated reports a quarter. Thanks for the partnership -- it has been one of the highlights of my book."
Team Recognition
Acknowledging the work of someone other than your primary contact.
Structure:
- Name the specific person and their contribution
- CC or copy the primary contact (they want to see their team recognised by their vendor)
- Be specific about what they did, not generic about who they are
Example (email to Lisa, CC'd to Tom): "Lisa -- I wanted to call out the work your team did on the Q1 data migration. Migrating 4 years of historical data in 3 days with zero downtime is impressive by any standard. Tom mentioned the project at our last QBR and it is clear the team's effort made the difference."
Channel Selection
| Occasion | Best Channel | Why |
|---|---|---|
| Product milestone | Email or Slack | Timely, specific, can include data |
| Business achievement | LinkedIn or email | LinkedIn for public acknowledgement, email for personal note |
| Personal milestone (promotion, award) | LinkedIn comment + personal email | Public recognition + private congratulations |
| Anniversary | More personal than Slack, less public than LinkedIn | |
| Team recognition | Email (CC primary contact) | Primary contact sees you recognising their team |
What Makes a Celebration Note Fail
| Failure | Why It Fails | Fix |
|---|---|---|
| "Congratulations on the great work!" | Generic. Could be sent to anyone | Name the specific achievement and connect it to what you know about their goals |
| "We are thrilled to celebrate this milestone" | Corporate voice. "We" and "thrilled" in the same sentence sounds like a press release | Write as yourself, not as your company. "I" not "we" |
| A celebration that pivots to a sales ask | Instrumentalising the moment. The customer feels used, not recognised | Celebrate. Full stop. The commercial conversation can happen another day |
| A celebration you are late to | A congratulations note 3 weeks after the event shows you were not paying attention | Set up alerts. Celebrate within 48 hours or do not celebrate at all |
| Over-celebrating a minor event | A 5-paragraph note about a routine product milestone feels disproportionate | Match the weight of the note to the weight of the achievement. Small events get 2 sentences. Big events get a paragraph |
Output
For each celebration, the skill produces:
- The note (calibrated to channel, relationship depth, and occasion)
- Suggested channel
- Timing recommendation (how soon after the event)
- A note on whether follow-up is needed (e.g., a promotion may require a handoff conversation if their role changes)
Quality Gates
- Is the note specific enough that it could only be sent to this person about this event? The universal test for genuine vs. generic
- Is it the right length? 2-3 sentences for a minor milestone. A short paragraph for a major achievement. Never more than one paragraph -- this is a note, not a letter
- Does it avoid making the celebration about your product or your company? The customer's achievement is the subject, not your product's contribution to it
- Is the timing right? Within 48 hours of the event. Earlier is better. After a week, the moment has passed
- Would you be comfortable if this note were forwarded to their entire team? Celebration notes often get shared. Write accordingly
Principles
- The best celebration notes reference something the sender would only know if they were paying attention. "I noticed your team's adoption grew 40% this quarter" shows attention. "Great quarter" does not
- Celebration is a relationship investment with no direct ROI, which is exactly why it works. The customer knows you are not required to send this note. That is what makes it meaningful
- Consistency matters more than perfection. A CSM who sends a genuine 2-sentence note after every milestone builds more goodwill than one who sends an elaborate note once a year
- If you cannot think of something specific to celebrate, you are not paying enough attention to the account. Every active customer achieves something every quarter. Your job is to notice