Writing an Investor Update That Actually Gets You Help
Most investor updates end the same way: "let us know if you can help." It sounds open and grateful, but it asks the reader to do the work of figuring out what help actually means, and that's exactly the kind of vague request most people quietly skip past. A founder who sends a genuinely well-written update to forty investors, with strong metrics and honest framing, can still get zero replies simply because the closing line never told anyone what to actually do.
Warning
"Let us know if you can help" isn't an ask, it's a request for the reader to invent one. Most won't, not because they don't want to help, but because a specific favor is easier to act on than an open-ended offer.
An investor update with metrics and no specific ask informs. One with a real ask gets you something back.
Why a vague closing line goes nowhere
A specific ask, an introduction to a named type of person, feedback on a particular decision, gives the reader something concrete to act on today. A vague offer requires them to first figure out what you need, which most readers, however well-intentioned, don't do before moving to the next email. An investor reading a monthly update from a dozen portfolio companies isn't going to pause and brainstorm what a founder might need; they'll only act on something specific enough to recognize instantly as something they can actually do.
Take an investor who reads "let us know if you can help" at the bottom of an update. Even if they genuinely want to be useful, the request requires them to guess: intros? Feedback? Hiring help? Most readers, faced with that ambiguity, simply move on to the next email in their inbox. Compare that to "we're looking for intros to mid-market operations leaders who'd be a good fit for our product," which the same investor can act on in under a minute if they happen to know someone, because the ask told them exactly what to look for.
Before: write the update, cover the metrics honestly, close with an open invitation to help if they can.
After: give Claude your actual situation, and turn the closing line into one specific ask a reader could act on immediately, an intro, an answer, a piece of feedback.
A process for a closing ask that gets acted on
- 1
Name the actual thing you need, not a category of help
"Intros to enterprise buyers" is actionable. "Help with sales" isn't. Give Claude the specific need, not the general area it falls under.
- 2
Ask for the request phrased as something easy to forward
Request wording a reader could copy into an email to someone else without editing it. An ask that's easy to relay gets relayed more often than one the reader has to translate first.
- 3
Put the ask where it won't get missed
Ask Claude to place it as its own clearly marked line, not buried in a closing paragraph. A reader skimming the update should be able to find what you need without rereading.
- 4
Limit it to one ask per update
Multiple asks dilute which one actually matters most right now. If several things would help, pick the highest-leverage one for this specific update.
MRR grew 8% this month but we lost our biggest customer. Draft a one-page investor update: three headline metrics, a narrative paragraph, and one specific ask, without burying the churn. The ask should be for intros to mid-market operations leaders who'd be a good fit for our product.
”For an ask this specific, it's worth including one identifying detail that helps an investor recognize a match quickly, a company size, an industry, a role title, since the more precisely the ask describes the target, the more likely an investor is to think of a specific real person rather than dismissing it as too vague to act on.
Make the intro ask even more specific: we're looking for operations leaders at companies between 200-500 employees in logistics or manufacturing specifically, not operations leaders in general. Rework the ask to reflect that.
”
Inside Claude Tutorial
Turning a vague request into one specific, actionable ask is transferable.
Naming exactly what would help, in a form the reader can act on immediately, applies well beyond investor updates. The app has a full lesson on it, with practice that carries over to any message where you're hoping for help back.
When the honest ask isn't about growth
Not every real need is an intro or a customer lead. Sometimes what would actually help is candid feedback on a decision, or just someone with relevant experience to talk something through with, and that's a legitimate ask too. Founders sometimes avoid this kind of ask because it feels less impressive than an intro request, but an investor with real relevant experience is often more willing to spend twenty minutes on a genuine strategic question than to cold-email a contact on your behalf.
Tip
If the real need is feedback or a conversation rather than an introduction, ask Claude to phrase that as specifically as an intro request would be: what decision, by when, and why their perspective matters.
The real ask this month isn't an intro, it's feedback. We're deciding whether to raise a bridge round or cut costs to extend runway. Phrase a specific ask for input on that decision, including why their perspective as a former operator would be useful.
”It's also worth naming a real deadline for that kind of ask, since an open-ended request for feedback is easy to defer indefinitely, while a specific timeframe, "before our board meeting on the 15th," gives the investor a concrete reason to respond this week rather than someday.
Add a specific timeframe to this feedback ask. We need input before our board meeting on the 15th, and that deadline should be stated plainly, not implied.
”Continue reading
- Sharpening a Pitch's Opening Before Investors Hear It: earning the audience this update goes out to in the first place.
- Writing a Board Update That's Honest About Mixed Results: the equal-weight-metrics discipline this same update relies on, covered in more depth.
- Comparing Bootstrapped and Funded Paths Before You Choose: deciding whether you want this audience receiving updates at all.