How to Write a Monthly Founder Update for Your Team
As a startup grows past a handful of people, the founders stop being in every conversation, and the team starts to wonder what is really going on. A monthly founder update closes that gap. It is one honest, well-structured message that tells everyone where the company stands, what changed and what matters next. Here is how to write one your team will actually read.
Key takeaways
- A monthly founder update gives the whole team the same picture of progress, problems and priorities.
- Use a consistent structure: headline, key numbers, wins, challenges, priorities, asks and thanks.
- Share bad news early and plainly, with what you are doing about it.
- Keep it short enough to read in five minutes and send it on the same day every month.
- Invite questions and answer them, so the update becomes a conversation, not a broadcast.
If you are reading this in late January, you are in a perfect spot to start. The first update of the year can look back on the last quarter, restate the goals you set for the months ahead and set the tone for how you will communicate all year. Even if your team is only five or six people, starting the habit now makes it much easier to keep as you grow.
This guide focuses on updates for your own team. Many founders also send a regular update to investors. The two overlap, but the audience is different, so we will touch on how to adapt one into the other near the end.
Why a monthly team update matters
In the very early days, everyone sits in the same chat, hears every customer call and knows the bank balance. That changes quickly. Once you have people focused on engineering, sales or support, they each see only part of the picture. Without a regular update, gaps get filled with guesses, and guesses tend to be more worrying than reality.
A good monthly update helps you:
- Align the team. Everyone understands the goals and how their work connects to them.
- Build trust. Sharing both good and bad news shows that leadership is honest.
- Save time. Fewer people need to ask "How are we doing?" in one-to-ones.
- Create a record. Over a year, your updates become a history of decisions, lessons and progress.
- Sharpen your own thinking. Writing forces you to decide what really mattered this month.
Pick your format and rhythm
Before you write, make three simple decisions and stick to them for a few months.
When to send it
Choose a fixed day, such as the first Monday or the third working day of each month. That gives you time to close out the numbers but keeps the news fresh. Consistency matters more than the exact date, because people learn to expect it.
Where to send it
Email works well because it is easy to archive and forward to new hires. Some teams post the update as a page in their wiki or knowledge base and share the link in the team channel. Pick one home and keep all past updates there.
Written, video or both
The written version should always exist, because it is searchable and easy to skim. Some founders add a short recorded walkthrough for the bigger picture, or discuss the update at a monthly all-hands meeting. If you do, keep the written update as the source of truth.
Pro tip
Keep a running notes document during the month. Whenever something notable happens, such as a customer win, a lesson or a teammate going above and beyond, drop in one line. When update day arrives, most of your draft is already there.
What to include in your founder update
The best updates follow the same structure every month, so readers know where to look. Here is a structure that works for most startups.
- Headline. One or two sentences that sum up the month. If someone reads nothing else, they should still understand how things went.
- Key numbers. Three to six metrics you track every month, such as revenue, active customers, pipeline, product usage or cash runway. Show this month, last month and the target.
- Wins. Customer wins, product launches, hires, milestones and good feedback. Name the people behind them.
- Challenges. What went wrong or is behind plan, why, and what you are doing about it.
- Priorities for next month. The two or three things that matter most, tied to your goals or OKRs if you use them.
- Asks. Where you need help from the team, such as referrals, feedback on a plan or volunteers for a project.
- Thanks. A few lines of specific recognition.
If you use OKRs, which stands for Objectives and Key Results and are typically set quarterly, the monthly update is a natural place to report progress on each key result. A simple "on track", "at risk" or "off track" label next to each one tells the story quickly.
Common mistake
Turning the update into a highlight reel. If every month sounds like a press release, people stop believing it, especially when they can see problems in their own work. Include at least one honest challenge every month. It makes the good news more credible.
A copyable founder update template
Use this structure as the skeleton for each update. Copy the key numbers table into your draft and fill in your own figures. The numbers below are made up for illustration only.
Key numbers table
| Metric | Last month (example) | This month (example) | Target (example) | Status |
|---|---|---|---|---|
| Monthly recurring revenue | $38,000 | $41,500 | $45,000 | At risk |
| Active paying customers | 112 | 121 | 120 | On track |
| Months of cash runway | 16 | 15 | 12 or more | On track |
Written sections
- Subject line: "Founder update, [month]: [one-line headline]"
- Headline: "January was a strong month for new customers, but expansion revenue lagged. Here is what we are changing."
- Wins: "We closed our first customer in Ireland, thanks to Sam's work on the onboarding call script."
- Challenges: "Two larger customers delayed their upgrade decisions. We are running interviews to understand why."
- Priorities: "1. Ship the team permissions feature. 2. Hire our second support person. 3. Finalize pricing for annual plans."
- Asks: "If you know great support candidates, send them to me this week."
- Thanks: "Huge thanks to Aisha for covering the weekend outage and writing up the fix."
- Close: "Questions? Reply directly or add them to the update thread. I will answer them all by Friday."
How to share difficult news
Some months will include hard news: a big customer leaves, a fundraise takes longer than planned, a key hire falls through or cash is tighter than you hoped. These are the months when your update matters most. People usually cope well with bad news. What damages trust is hearing it late, secondhand or wrapped in spin.
Follow a simple pattern for difficult updates:
- Say it plainly and early. Put the important news near the top, not buried under wins.
- Explain what it means. Be specific about the impact on the team and the plan.
- Share what you are doing. List the concrete steps you are taking and when you will update again.
- Be clear on what you do not know. It is fine to say "We do not have a decision yet, and we will tell you by the 15th."
- Make space for questions. Offer an open session or office hours for anyone who wants to talk.
Before sending anything sensitive, such as news about job changes, think about who should hear it first and in what order. Some news is better shared in person or on a call before it appears in writing, and some topics may have legal implications. When in doubt, check with a qualified employment adviser first.
Hypothetical example
Imagine Marcus, founder of a 14-person software startup. In one month, his largest customer gives notice. Instead of hiding it in the challenges section, he opens his update with it: what happened, how it affects revenue, and the three steps the team will take, including a pause on two planned hires. He ends with an open question session the next day. Several people later tell him that the honest update made them more confident, not less, because they trusted they were getting the full picture.
Tips for writing an update people read
Even the best structure fails if the update is long, dense or dull. Keep these habits in mind.
- Aim for a five-minute read. Link to deeper documents instead of pasting everything in.
- Use headings and short paragraphs. Most people skim first and read in detail second.
- Write like you talk. A friendly, direct tone builds connection. Avoid jargon and buzzwords.
- Be specific with praise. "Thanks to the team" is forgettable. "Thanks to Jo for the customer interviews that changed our pricing" is not.
- Show trends, not just snapshots. Comparing this month with last month and the target makes numbers meaningful.
- Use AI tools carefully. Tools such as ChatGPT, Claude, Gemini or Grammarly can help tighten a draft, but the voice and the judgment should be yours. Avoid pasting confidential figures into any tool before you check its privacy policy.
Adapting it for investors
Many founders send a similar update to investors. You can reuse your structure, but adjust the focus. Investors care most about metrics, cash, fundraising plans and specific asks such as introductions. Your team cares more about priorities, wins, recognition and what changes affect their work. Write the team version first, then trim and adapt it, rather than forwarding the same message to both groups.
Your founder update checklist
- Pick a fixed send day each month and put it on your calendar
- Choose one home for all updates, such as email or your wiki
- Start a running notes document for wins, lessons and thanks
- Choose three to six key numbers and track them the same way every month
- Write a one-line headline that sums up the month
- Include wins, at least one honest challenge and two or three priorities
- Add clear asks and specific thanks
- Plan how to share any sensitive news before you write it down
- Invite questions and answer them within a set time
- Archive every update so new hires can read the history
Frequently asked questions
How long should a monthly founder update be?
Aim for something people can read in about five minutes. A short headline, a small table of key numbers and a few bullets for each section is usually enough. Link to longer documents if people want more detail.
Should I share financial numbers with the whole team?
Many startups share revenue, runway and key metrics because it builds trust and helps people make better decisions. Some details, such as individual salaries or confidential deal terms, should stay private. Decide what level of openness suits your company and be consistent.
What if nothing much happened this month?
Send it anyway. A short update that says "steady progress, here are the numbers and next priorities" still builds the habit and reassures people. Quiet months are often when the team most needs to hear that the plan is on track.
Who should write the update when there are several founders?
Usually the CEO owns it, with input from the other founders on their areas. Some teams rotate sections. What matters most is a single, consistent voice and a clear owner who makes sure it goes out on time.
Related reading
The bottom line
A monthly founder update is one of the simplest tools for keeping a growing team aligned. Use the same structure every month, lead with an honest headline, show a few key numbers, share both wins and challenges, and end with clear priorities, asks and thanks.
Open a blank document today, copy the template above and draft your first update for this month. It does not need to be perfect. It just needs to be honest, clear and on time, and then again next month.
