Why VC Newsletters Work - and How to Build One That Scales

Most VC newsletters die quietly. Not from lack of ideas - from lack of system. The fund publishes three issues in January, skips February, sends something in March, then goes dark. By the time they return, the list has forgotten them.

The funds whose newsletters actually work - the ones LPs forward to their partners, founders read before a first meeting, and co-investors reference in deal memos - run on a four-part loop that takes about two hours a week to maintain. The artifact is a repeatable content operation, not a writing talent. Here is how to build one.

This is written for Israeli VCs specifically, but the mechanics apply anywhere a small team is trying to publish consistently without a dedicated content hire.

Step 1: Map Your Thesis and Audience

The input here is a single document - a one-page investment thesis in Google Docs or Notion. It should contain six fields: sector focus, stage, geography, check size, founder profile, and what you will not invest in. If you don't have this written down already, write it before you publish issue one.

Why does this matter for a newsletter? Because without it, you drift. A Tel Aviv-based VC with a cleantech thesis realizes, six months in, that 40 percent of their newsletter mentions AI startups. Not because they changed strategy - because whoever was sourcing stories grabbed what was interesting that week. The newsletter started as a cleantech signal and became a general tech roundup. Subscribers who signed up for cleantech insight quietly unsubscribed. New subscribers who found it through AI content had no idea what the fund actually does.

Run the thesis audit before you start sourcing. Use this template:

[YOUR FUND NAME] | Sectors: [list, e.g., cleantech, climate infra] | Stages: [list, e.g., pre-seed, seed] | Geography: [list, e.g., Israel, Europe] | Check size: [range] | Founder type: [description, e.g., technical founders with regulatory experience] | What we will NOT cover: [explicit list]

Paste this at the top of your sourcing sheet. Every story you consider adding should pass through the last line - what you will not cover - before it goes in.

What you get back:

• A one-sentence thesis statement you can put in the newsletter header

• A subscriber persona: who is reading this, what is their title, what decision are they trying to make, and on what timeline

• A content guardrail: a written list of what the newsletter covers and what it explicitly does not, so sourcing decisions take seconds instead of arguments

What this step will not tell you: whether your thesis is differentiated enough to attract subscribers who don't already know you. That is a positioning question you need to answer separately.

Step 2: Build a Sourcing System

The input is a sourcing spreadsheet - Google Sheets or Airtable. Columns: Source, URL, Founder Name, Sector, Stage, Date Found, Newsletter Issue, Notes. This is not a reading list. It is a production queue. Every row is a potential story. The Newsletter Issue column tells you which issue it ran in, or leaves it blank if it hasn't been used yet.

An Israeli VC with 15 portfolio companies and 3 LPs was sending a newsletter every week but had no sourcing system. By week eight, they were recycling the same three portfolio companies in every issue. LPs noticed. Founders noticed. The newsletter started to feel like a vanity press release rather than a market signal. The fix wasn't better writing - it was a sourcing discipline that forced them to pull from a wider set of inputs: Israeli press, EU regulatory updates, founder Twitter threads, academic papers on battery chemistry, LP introductions from other funds.

Use this template as your sheet header:

Source | URL | Founder Name | Sector | Stage | Date Found | Newsletter Issue | Notes

Add three to five sources per week on a fixed day - Tuesdays work well. Pull from Israeli tech media (Calcalist, CTech, NoCamels), sector-specific feeds, portfolio company updates, and one international source that covers your thesis area. If you can't find three relevant stories in a week, your thesis may be too narrow - or your sourcing inputs too thin.

What you get back:

• A running log of 50 or more story ideas within three months

• A clear view of which sectors you're covering and which you're ignoring - the blank rows are as informative as the filled ones

• A reusable archive for future newsletters, so you're never staring at a blank page on Wednesday morning

What this step will not tell you: whether your sourcing inputs are actually representative of the market, or just the corners of the internet you already read. Audit your source column every quarter and replace any source you haven't pulled a story from in eight weeks.

Step 3: Write and Test a Template

The input is a single email template saved in your newsletter platform - Substack, Mailchimp, or Ghost. The template has fixed sections that don't change week to week. This is the constraint that makes the newsletter producible in under two hours.

A VC sent a 1,200-word newsletter with eight stories, no clear structure, and no call to action. Open rates dropped 30 percent over the first six weeks because subscribers didn't know what to focus on. Every issue felt like a different product. When they cut to a fixed template - short intro, three stories, one portfolio spotlight, one closing question - open rates recovered within four issues. The content hadn't changed. The predictability had.

Use this structure as your starting template:

[NEWSLETTER NAME] | Issue #[NUMBER] | [DATE]

Intro: [2-3 sentences on this week's theme or market observation]

Story 1: [Headline] | [2-3 sentences on why it matters to your thesis] | [Link]
Story 2: [Headline] | [2-3 sentences on why it matters to your thesis] | [Link]
Story 3: [Headline] | [2-3 sentences on why it matters to your thesis] | [Link]

Portfolio spotlight: [Company name] | [One-sentence update or milestone]

Closing question: [One open question you're sitting with this week - invite replies]

Keep the intro to three sentences maximum. Keep each story to three sentences. The closing question is optional but drives more replies than any other section - replies signal to email providers that your newsletter is worth delivering to the primary inbox, which matters for Gmail's promotional tab filtering.

What you get back:

• A consistent format subscribers recognize after two issues - they know where to find what they need

• A measurable baseline for open rate and click-through rate (CTR, the percentage of openers who click at least one link) within four weeks

• A faster writing process - the template fills in 30 minutes once your sourcing sheet is populated, compared to two or three hours starting from a blank document

What this step will not tell you: which story angle your specific audience responds to. You'll need four to six issues of data before you can draw any conclusion from open rates. Don't optimize too early.

Step 4: Set a Cadence and Automate Reminders

The input is a calendar entry - Google Calendar or Notion - with a fixed send day, send time, sourcing deadline, and draft deadline. All four fields, not just the send day. Cadence matters more than frequency. Weekly is better than sporadic, even if weekly feels like a lot. The reason is simple: subscribers form habits, and habits require regularity. A newsletter that arrives every Thursday at 9 AM Israel time becomes part of the Thursday morning routine. A newsletter that arrives whenever the team has time trains subscribers to ignore it.

An Israeli VC was sending every two to three weeks when they had bandwidth. Subscribers forgot about it between issues. The unsubscribe rate climbed. They switched to every Thursday at 8 AM. Within eight issues, their open rate went from 22 percent to 31 percent. Not because the content improved - because subscribers started expecting it. Industry benchmarks put average open rates for investment and finance newsletters around 25 to 30 percent; consistency is the most reliable lever for staying above that range.

Use this checklist to lock in the cadence before you publish issue one:

Send Day: [e.g., Thursday]
Send Time: [e.g., 9 AM Israel time]
Sourcing deadline: [e.g., Tuesday 5 PM - no new sources added after this]
Draft deadline: [e.g., Wednesday 5 PM - template filled and reviewed]
Review reminder: [e.g., Thursday 8 AM - final check before send]
Slack reminder set: [Yes / No]
Calendar block set: [Yes / No]

Set a Slack reminder or recurring calendar block for each of the three deadlines. The send doesn't fail because you ran out of ideas - it fails because no one remembered to start on Tuesday.

What you get back:

• A predictable schedule that subscribers trust enough to open before they've read the subject line

• A clear internal workflow with no ambiguity about who does what and when

• A measurable send frequency - 52 newsletters a year is a different signal to the market than 18

What this step will not tell you: the right send time for your specific audience. Test two different send times over six weeks each before committing. Israeli business hours and European LP schedules don't always overlap.

The Whole Loop on One Page

The four steps run as a cycle: Map Thesis - then Source Stories - then Write Template - then Send on Cadence - then loop back to Source Stories. The thesis mapping happens once, then gets audited quarterly. Everything else runs weekly.

The weekly rhythm looks like this: every Tuesday by 5 PM, add three to five sources to the sheet. Every Wednesday by 5 PM, fill in the template using the sourcing sheet. Every Thursday at 8 AM, review the draft and send. The whole active work time - sourcing plus writing plus review - is under two hours per week once the system is running.

All four tools required to run this are free to start: Google Sheets for sourcing, Google Docs for the template draft, Substack or Ghost for sending (both have free tiers), and Slack for deadline reminders. No paid tools required for the first 500 subscribers.

This loop works for one newsletter per week. If you scale to two per week, add a second sourcing person or use a tool like Feedly to auto-tag stories by sector - otherwise the sourcing bottleneck will cause the second newsletter to drift off-thesis before issue four.

Where This Breaks

Three failure modes show up consistently. All three are predictable. None of them are about writing quality.

You source stories but never send. The trigger is a busy period - fundraising, a major deal closing, a portfolio company in trouble. The symptom is a sourcing sheet with 200 rows and a newsletter that hasn't gone out in six weeks. The fix is to decouple sourcing from sending. Sourcing is Tuesday's job. Sending is Thursday's job. If Thursday's newsletter goes out with only two stories instead of three because sourcing slipped, that is acceptable. A short newsletter is better than no newsletter. Protect the send date above everything else.

Your thesis drifts. The trigger is a few investments outside your stated focus - a couple of AI deals when your thesis says cleantech - followed by a few more. The symptom is a newsletter that covers four sectors instead of one, and subscribers who followed you for a specific signal stop engaging because the signal got noisy. The fix is the quarterly thesis audit. Pull up the content guardrail from Step 1 and run every story in the last twelve issues against it. If more than 20 percent of your stories sit outside the guardrail, the newsletter has drifted. Either update the thesis document to reflect where the fund is actually going, or remove the off-thesis stories from the queue. Either is fine. The problem is leaving the drift unacknowledged.

The template gets too long. The trigger is gradual accumulation - you add a fourth story, then a market data section, then a commentary paragraph, then a jobs board. Each addition feels justified. The symptom is that CTR drops and replies stop because subscribers can't find the point. Research on email engagement consistently shows that shorter emails generate higher click rates than longer ones, even when the longer version contains more useful information. The fix is a hard rule: no more than three stories, one portfolio spotlight, and one closing question. When you want to add something new, remove something existing.