first principles
Work with me
← Channel playbooks

Channel 11 / 13 · Own distribution

Email & owned audience

Build a way to reach interested practitioners again.

Use it when

You regularly have useful technical lessons, product news or customer examples.

Don't confuse it with

Dumping every contact into a weekly sales newsletter.

01 / What companies actually did

PostHog launched its own newsletter

Its developer-marketing lessons explicitly recommend owned channels such as email over dependence on a social feed or occasional Hacker News attention.

[P1] PostHog — 40 things learned about developer marketing ↗

Supabase distinguished user updates from major launches

Its launch write-up describes monthly beta update emails, with broader public campaigns later during Launch Week.

[S1] Supabase — How we launch ↗[S3] Supabase — November Launch Week recap ↗

Tailscale used newsletter replies to learn

Tailscale says its regular customer survey, distributed with its newsletter, surfaces candid feedback on its free plan and product direction.

[T1] Tailscale — Why the free plan stays free ↗

02 / How to do it

  1. 01Create separate tracks for subscribers, free users, evaluators and customers; respect consent.
  2. 02Send one useful item per email: guide, benchmark, launch, setup or customer lesson.
  3. 03Use an explicit audience: “for platform teams running X,” not everyone.
  4. 04Pair content with a relevant next step and keep unsubscribing easy.
  5. 05Track replies and engaged product actions as well as opens/clicks; review with sales without over-attribution.

Things you can publish or run

This month in [technical category]: one practical lessonHow we built [feature] — engineering notesThree common mistakes in [workflow] and how to fix them

03 / What good looks like

Watch this

Replies, return readers, documentation/product visits, activated users, assisted opportunities, unsubscribes.

Common trap

Open rate alone is unreliable and does not prove revenue impact.

04 / Copy the worksheet

COPYABLE WORKSHEET / 11

Email & owned audience template

Replace the brackets. Use this as a starting point, not a rigid formula.

DEVELOPER NEWSLETTER ISSUE
Subject: [one useful technical observation]
Audience: [role / stack]
Opening (2–3 sentences): [real observation / case]
One practical thing: [code / method / chart]
What we learned: [trade-off / result / limit]
Read/use: [link to guide/demo]
Optional next action: [reply / try / join workshop]
Footer: who sent this + why recipient receives it + unsubscribe
Segment: subscriber / customer / evaluator
Track: engaged visitors, replies, next actions

05 / Original sources

Next channelFounder & engineer-led social →