Templates · Newsletters
Company monthly update template
What shipped, the numbers, wins and people news, ready to send as an email newsletter
Start with this template →Sign in
Opens on reph with the template ready to start. No account needed; sign in to keep your document.
Filled example
The template filled in for a made-up company, so you can see what good looks like.
Lumen Labs, September 2026
Lumen Labs · October 2, 2026
September was the month the self-serve plan started paying for itself: 61 teams signed up and paid without ever talking to sales, and they now bring in more new revenue each week than outbound does.
The numbers
What shipped
- Runbook import: teams can bring their Confluence runbooks over in two clicks, formatting intact. Release notes
- Alert links: every PagerDuty alert now opens the matching runbook directly, so on-call starts in the right place.
- SAML for all paid plans: no longer Enterprise-only, which unblocked four deals stuck in security review.
Wins
- Northwind signed a three-year Enterprise agreement, our largest contract to date. Credit to Imani and Josh for a six-month cycle that never stalled.
- "We fixed the runbook during the incident, and it was still right the next time." That came from an SRE at Fernhill in a support ticket, unprompted.
- Support median first response hit 38 minutes, down from 2 hours in June. Thank you, Aiden and the support crew.
What didn't go well
The September 12 outage took search down for 47 minutes. The postmortem is public internally, and the two fixes (index failover and an alert that actually fires) both shipped by September 20.
People
- Welcome to Rosa Kim (Design), Femi Adebayo (Sales, London) and Tariq Haddad (Platform).
- Five years at Lumen for Hannah Weiss, our first engineering hire.
- Congratulations to Luis Moreno, now Engineering Manager for the Integrations team.
Coming next month
- Start the EU data residency beta with three design partners.
- Hire two more support engineers to cover the APAC morning.
- Q4 planning wraps October 17; team plans go to the shared planning doc.
One ask
Fill in the 5 question engagement survey by Friday. It takes four minutes and it shapes the Q4 offsite agenda. Take the survey
The template
Show the blank template
Company monthly update
[workspace] · [date]
One paragraph: the single thing everyone should remember from this month.
The numbers
Three to five numbers the company steers by. Same set every month so the trend means something.
What shipped
Customer impact first, feature name second.
- [Thing]: what it does for customers, in one line. [Link]
- [Thing]: more
Wins
A customer quote, a deal, a milestone. Name the people who made it happen.
What didn't go well
One or two honest lines on a miss, and what you're doing about it.
People
Welcome new joiners, celebrate anniversaries and promotions.
Coming next month
One ask
The one thing you want readers to do. Make it a link.
Questions
- Who should write it?
- A founder or exec signs it, even if comms drafts it, so it reads as leadership talking
- Should bad news go in?
- Yes, briefly and early; people hear it anyway, better from you
- How long should it be?
- Readable in three minutes, with links for anyone who wants depth
- How does it reach everyone?
- Publish it, then use Set up sending on the doc to email a workspace list; colleagues join with the list's signup link from the workspace's Audiences panel
- Who can see the published page?
- Anyone with its link, so keep out numbers you would not want forwarded
- Can I check it before it goes out?
- Send me a test in the send dialog emails only you; the subject starts as the dated title and can be changed there
Fill it with your agent
Connect Claude to reph over MCP, then paste this. The draft arrives as suggestions you accept or reject section by section. How to connect Claude.
Find my reph doc "Company monthly update" with search_docs, then read it with read_doc. Draft this month's issue from the finance dashboard numbers, release notes, team leads' weekly digests and the joiners list. Find last month's issue with search_docs, call get_reader_signals on it and lead with what got read to the end. File it with suggest_edit, one replace_section op per section (heading line kept) so each can be accepted alone. Ask each open question (numbers finance has not closed) with add_comment quoting that section's heading line, then call request_review with a one-line summary.
Related templates
Start with this template →Sign in