the investor update nobody thinks is a problem

you don't feel skipped investor updates until the next raise. the update is the cheapest relationship tool you have... so why do founders skip it?

share x linkedin facebook

friday morning i talked to a founder building software for one boring job. investor updates.

he's spent seventeen years in product. before this he ran a fintech that ended in a small acquisition. he raised multiple rounds, and he felt the pain of updates himself.

his tool drafts the update in the founder's own voice, pulls in stripe and bank data, and calculates runway. the founder reads the draft instead of spending three hours building it from scratch.

his honest problem wasn't the product. it was that most founders he talks to don't think investor updates are a problem at all.

i get why. skipping one update doesn't hurt. nothing breaks. nobody emails you angry. the business keeps running.

skipping six does hurt. you just don't feel it until you need it.

here's when it shows up. you start your next raise. you go back to your existing investors first, because that's what you're supposed to do. and the people who could have helped, the ones who would have made intros, maybe even led, haven't heard from you in six months.

now your first email to them isn't an update. it's an ask. and an ask after six months of silence reads exactly the way you'd expect.

flip it around. imagine you'd sent a short note every month. here's the number. here's what went well. here's what didn't. here's one thing you could help with.

by the time you raise, those people have watched twelve months of you doing what you said you'd do. they've already made a couple of intros because you asked for something small. they're not being pitched. they're being invited to keep going.

that's what an update is. it's give first outreach to people who already said yes to you once. the cheapest relationship tool you'll ever have.

the common guidance is simple and i agree with it. monthly. short... one source suggests two hundred and fifty words or fewer. your key metrics. highlights and lowlights, both. and a specific ask.

the lowlights are the part founders skip, and the part investors trust most. anyone can send good news. when you send the bad month too, with what you're doing about it, every good month after that gets believed.

and the ask is the part that turns a report into a relationship. one intro. one customer type. one hire. make it small enough that someone can do it in five minutes.

and none of this has to take long. his whole pitch is that the founder reviews a draft instead of building it from scratch. whether a tool writes it or you do, the update should be a short monthly habit, not a quarterly project you dread.

on the call i told him what i keep telling every founder i talk to. building is close to trivial now. anybody can build almost anything in seconds with ai. the hard problem is go to market... selling, raising, partnering. his real job isn't the product. it's convincing founders the problem is real before the raise teaches them the hard way.

and that's the lesson for you, whether you use a tool or not. the update is a go to market activity. your investors are your first market for the next round. they deserve the same cadence you'd give a customer.

long term, the founders who raise easily aren't the ones with the best deck. they're the ones whose investors already know the story because they've been reading it every month.

if you want help setting up that rhythm before your next round, that's part of how i approach fundraising strategy.

so when did your investors last hear from you... and what would they say if you asked them for something tomorrow?

share x linkedin facebook
the newsletter

the machine economy brief

one email when it matters: bitcoin, ai, robotics, and what founders should do about it. unsubscribe anytime.

no spam, no list-selling. your email goes to sunny, nowhere else.

raising right now?

i run fundraising as a service. lead-investor manufacturing, warm intros, the whole motion.

see how raasrocket works →