How to write a weekly startup update (template and example)
Short answer
A good weekly startup update is a short note, sent on the same day every week, that says what shipped, which numbers moved and why, what didn't work, what's next, and one specific ask. Put a one-line summary on top so a busy reader gets the point in ten seconds. Your team, users and mentors can get it weekly; investors are usually better served by a monthly roll-up of the same notes.
- Updated
- Reading time
- 6 min read
What this page is for: You want a short, repeatable update that people actually read and that shows real progress, in good weeks and bad ones.
Who the update is for
Decide the reader first; it changes what goes in and how you say it.
| Reader | What they want to know | Tone | Usual cadence |
|---|---|---|---|
| Users | What changed for them, what got fixed | Plain words, no internal metrics | Weekly or per release |
| Team | Decisions, blockers, this week's priority | Direct and complete | Weekly |
| Mentors and advisors | Where you're stuck, the decision ahead | Candid, problem first | Every few weeks, or when needed |
| Investors | Key numbers against last period, cash, problems, asks | Brief, numbers first | Monthly |
| Public followers | What you built and learned | Human and specific | Weekly |
- Users care that the export button finally works, not about your conversion rate. Keep a Changelog's advice fits: write for people, group similar changes, newest first.
- Team updates carry the uncomfortable detail: the bug that cost two days, the customer who left. 37signals' Heartbeats are a good model; Jason Fried describes one as a summary of all the work a team did over its last six-week cycle, open to everyone in the company.
- Mentors help most when you open with the problem.
Don't send one email to all five groups. Write one note for yourself and the team, then trim a version for each reader.
A copy-paste template
Subject: [Startup name] weekly update, week [N]
One line: [The single most important thing this week, good or bad.]
Shipped
- [Thing that is live, in one line, and who it is for]
- [Fix or improvement]
Numbers that matter
- [Metric]: [this week] (last week: [x]). [Why it moved, or a caveat.]
- [Metric]: [this week] (last week: [x]). [Context.]
What didn't work
- [What you tried, what happened, what you learned]
Next week
- [The one priority]
One ask
- [A specific person, intro, answer or test you need, and by when]
How to fill each part:
- One line. Write it last. "Pricing test failed; daily use up" says more than "Busy week!"
- Shipped. Only what is live or in users' hands. "Working on" belongs under Next week.
- Numbers that matter. Pick two to four and keep the same ones, defined the same way, every week. Show the previous value and one line of context: a small sample, a one-off spike, a friend who signed up. In "Startup = Growth", Paul Graham names revenue as the best thing to measure growth by, and active users if you aren't charging yet. A number that fell goes in the same spot it would sit if it rose.
- What didn't work. This makes the rest believable. "Cold emails: 40 sent, 1 reply" beats a paragraph of spin.
- Next week. One priority. Eight priorities means none.
- One ask. Specific and easy to forward: "an intro to someone who buys stock for a cafe chain", not "let me know if you can help". For investors, move it right under the one line so it can't be missed.
Example update
This is an example for an invented startup called Rafnot, a stock-tracking app for small cafes. The numbers are made up to show the format.
Subject: Rafnot weekly update, week 14
One line: Barcode scanning is live and 3 of 5 pilot cafes used it daily,
but nobody has paid yet.
Shipped
- Barcode scanning for deliveries, so staff stop typing items by hand
- Fixed the sync bug that duplicated items when two phones edited at once
Numbers that matter
- Pilot cafes active daily: 3 of 5 (last week: 2 of 5). The new one is a
friend's cafe, so read it with care.
- Items scanned: 412 (first week of the feature, nothing to compare yet)
- Paying customers: 0 (last week: 0)
What didn't work
- I emailed all five pilots about pricing. One reply: "maybe after summer."
Asking late and by email made it easy to postpone.
Next week
- Call each pilot owner with one question: $15 a month, yes or no?
One ask
- Do you know a cafe owner who orders stock every week? A 20-minute call
before Friday would let me test the pricing question with someone new.
The bad number sits next to the good one, the friendly pilot is flagged, and the ask has a deadline.
Cadence and length
Weekly or monthly? Weekly suits you, your team and anyone following along, especially early, when one week changes a lot. When Y Combinator relaunched Startup School in 2020, it asked founders for weekly updates tracking their goals and most important metrics, and said it plainly: "Consistent progress every week is a prerequisite for success." Investors differ. Leo Polovets of Coding VC writes that once a month is a good frequency for investor updates, and that weekly ones burden founders and are rarely eventful. So write the note weekly, and once a month turn the last four into one investor update. It's easier still if you keep a line a day somewhere, for example on Upvera: by Friday the week's material is already written.
Consistency beats length. Pick a day and keep it. A three-line note every Friday builds more trust than a long essay that only appears in good weeks. A missing week gets noticed, usually the one you'd rather not report. Send it anyway.
How to keep it short:
- Aim for two minutes of reading on a phone.
- Three bullets per section at most. Empty section? Write "Nothing this week."
- Link to details (a demo video, a doc) instead of pasting them in.
- Cut process. "We had a lot of meetings" is not progress.
Common mistakes
- Only good news. Once readers notice there is never a bad week, they discount all of it.
- Changing the metrics. Dropping a number the week it falls gets noticed. If you change the set, say so and say why.
- Totals instead of movement. "1,000 signups all time" hides whether this week beat last week.
- A vague ask. "Any help welcome" gets no help. Name the person, intro or answer you need.
- One version for everyone. Users get lost in burn rate; investors don't need a note for every bug fix.
When it doesn't work
An update reports progress; it can't create it. If nothing shipped, a template won't hide that, and dressing it up costs trust. Very early numbers are also noise: with five users, one person moves every percentage, so report what you learned from conversations instead. If you post publicly, leave out customer names, revenue details and anything a pilot user hasn't agreed to share.
Questions
How long should a weekly startup update be?
Two minutes on a phone: a one-line summary and two or three bullets per section. Need more room? Link to a separate doc.
What do I write in a week with nothing to show?
Write it anyway and say so in the one-line summary: what blocked you, what you learned, what you'll ship next. A skipped week reads worse than an honest slow one.
Should investor updates be weekly or monthly?
Monthly is the usual rhythm; Leo Polovets writes that most startups he works with send monthly. A month also gives numbers time to mean something, and you can still write weekly for yourself.
Which numbers should I include before I have revenue?
The closest thing to real use: weekly active users, repeat use, or how many people completed the core action. Avoid totals that only go up, like all-time signups.
How Upvera does it
Upvera is a progress platform where startup founders and independent builders share what they build every day. You add your startup, which gets a public page, and post what you did today in a line; those days become the raw material for your weekly or monthly update. If you connect GitHub, the App Store, Vercel or npm, pushes and releases are read from the source and added to your days automatically. Days are sealed into an append-only ledger, and anyone can check the published daily roots at upvera.co/dogrula. Add your startup to start your daily record.
Sources
Keep your days in one place
On Upvera you add your startup and share what you did each day in a line. The sources you connect fill in your days on their own.
Related guides
- What is building in public, and how do you start?What building in public means, why founders do it, a weekly rhythm, a post template, how open to be and what never to share.
- How to set up a founder accountability groupWho to invite, a 45-60 minute weekly format, a written commitment template and how to keep a founder accountability group going.
- What to post when you have nothing to show yet14 post types for founders with nothing to show yet, with examples, a one-line formula, honest bad-day posts and what to avoid.