There's been some bad advice going around the last week: only send investor updates when you're winning. Silence, the thinking goes, is safer than sending a bad update and getting quietly written off.
The advice is appealing because it treats communication as a cost. Every update is time away from building, and skipping the rough months feels like protecting bandwidth for the parts of the business that more obviously move things forward.
None of that makes the logic hold up. Silence stops being neutral once an investor knows a founder only writes when there's a win, and credibility and trust erode fast. I'd add that from our review at Dynamo, two consecutive months of no updates prior to a Series B raise more often than not maps to a company that is not going to make it.
The investors you want to take money from know that startups are hard and expect both the good and the bad. Someone tracking twenty companies at your stage has usually watched a version of your current problem play out somewhere else already, including what its early signs looked like. Cutting the updates cuts the one channel where that kind of pattern recognition could reach you before you needed it.
Then there are the moments where the founder more obviously needs help or perspective. Say a bridge round becomes necessary, a customer that makes up a big chunk of revenue starts pulling back, or there's a gnarly co-founder issue. These are the moments a founder actually needs someone to call. If the last thing an investor heard from you was a fundraise announcement eighteen months earlier, there's no relationship to draw on when one of those hits. The strategy that avoids bad news also avoids the one situation where the relationship would have mattered most.
Not every investor can play therapist, prevent a customer from churning, or write the next check. But quality investors can still care enough to understand and help problem-solve, which matters when a founder needs to talk and not just when they need a resource. Founding is hard in ways that have nothing to do with the business plan, and a person who's read a year of honest updates already has that context without needing the whole story explained from scratch. The relationship also outlasts the company. The investors reading your updates now are the ones you'll be raising from, or getting referred by, on whatever you build next.
A good update doesn't need to be complex. It covers the basics of the business in an honest, balanced, and reflective way: Asks, KPIs, Customers, Product, People, Capital, Major Goals, and Shoutouts. Quality investors already know the work is hard. They're not just grading the numbers. They're reading the thinking behind them, month over month.
The founders I've watched do this best keep a real cadence, monthly till a Series B, then quarterly once the company has more structure to lean on. That discipline is its own signal. An investor can't see how a company runs day to day, but a founder who reliably gets the update out on schedule is showing them something about the operation that has nothing to do with what's actually written in it.
All of this is really just trust, built on a schedule instead of by accident. Investors could hold up their side of that better too, responding faster and more consistently instead of going quiet themselves. That's a real problem, and a different piece.
None of this takes as much time as the excuse at the top of this piece assumes, either. Pulling customer, product, and talent data into a draft used to eat real hours. An agent that watches those systems can assemble the first pass on its own, leaving the founder to edit and add judgment instead of starting from a blank page every month. The skill in this repo is built off what the best of these actually look like, if it's useful. Load it up into Claude or your favorite harness to begin using it ASAP (it even has some light integration prompts to email, Slack, and your CRM to gather context).
Founders who save updates for the highlight reel are optimizing for how the good months look. The harder thing to manage is the month that isn't good, and whether anyone is still around with enough context to help when it lands.