Esc
  • Jump to
  • The board
  • All launchesSort and filter by week or category
  • Open statsEvery number, in public
  • Maker storiesApps that stopped hiding
  • Submit a launch
  • AICategory
  • AnalyticsCategory
  • API & BackendCategory
  • Audio & VoiceCategory
  • AutomationCategory
  • CommunityCategory
↑↓ to move↵ to openPress / anywhere
Sign in

Newsletter Feature Pitch Template

A short, editor-friendly pitch email to get your indie product featured in a curated niche newsletter without sounding like a press release.

Updated · Outreach

Copyable template

Copyable email template
Subject: Tool tip for [Newsletter Name]: [Product Name] ([5-word summary])

Hi [Editor First Name],

I really enjoyed your recent issue on [specific topic or link from a recent edition], especially the note about [brief genuine detail].

I just launched [Product Name] ([Product URL]) and thought it might fit your [exact section name, e.g., "Tools Worth Trying" or "Links" section] for [reader group].

In one line: [Product Name] is a [category] that lets [target reader] [concrete result] without [common hassle].

Why your readers might care:
- [Specific angle 1 relevant to their audience]
- [Specific angle 2, e.g., free tier, open-source piece, or notable constraint]

If you prefer a ready-to-paste blurb:
"[Product Name]: [Clean 20-to-30-word description written in the newsletter's own voice.]"

No worries at all if the next few issues are already full. Thanks for putting [Newsletter Name] together every [week/month].

Best,
[Your Name]
[Product URL]

When to use this template

Use this template when pitching independent curators who run weekly or monthly roundups in your exact niche, such as developer tooling digests, design links newsletters, or bootstrapper roundups. Newsletter editors often review dozens of submissions per issue, so respecting their section format and giving them a clean, neutral one-sentence summary makes their job much easier.

Check first whether the newsletter has a paid sponsorship page or an explicit submission form. If they only feature tools through paid ads, ask for their media kit instead of pitching a free editorial mention.

How to fill each placeholder

  • [specific topic or link from a recent edition]: Read at least two recent issues before writing. Mention one real detail so the editor knows you actually read their publication.
  • [exact section name]: Reference the real recurring section where links appear (for instance, 'Cool Tools' or 'Shipped This Week'). Matching their structure shows you understand what fits.
  • [Specific angle 1-2]: Highlight what makes the tool notable for their specific subscribers, such as working offline, having a generous free tier, or solving a problem they recently covered.
  • Ready-to-paste blurb: Write this in the calm, objective third-person tone the newsletter uses, never in ad copy. Editors often tweak or drop it straight into their draft.
  • Subject line: Keep it factual and easy to scan in a crowded inbox, naming both the newsletter and what the tool does in five words.

Filled example (made-up product)

Example using a made-up release-notes tool called ChangelogKit:

Subject: Tool tip for Frontend Weekly: ChangelogKit (auto release notes from PRs)

Hi Elena,

I really enjoyed your recent issue on solo maintainer burnout, especially the note about how writing release notes is usually the first habit to slip after a busy sprint.

I just launched ChangelogKit (https://changelogkit.example) and thought it might fit your "New Tools" section for indie devs and small product teams.

In one line: ChangelogKit is a lightweight release-notes builder that turns merged GitHub pull requests into a hosted, human-readable changelog page without manual copy-pasting.

Why your readers might care:
- Connects to a GitHub repo in under two minutes and drafts plain-English entries you can edit before publishing
- Free for public open-source repositories, with paid plans starting at $12/month for private repos

If you prefer a ready-to-paste blurb:
"ChangelogKit: Turn merged GitHub PRs into clean, hosted release notes and an embeddable widget for your app. Free for open-source repos."

No worries at all if the next few issues are already full. Thanks for putting Frontend Weekly together every Tuesday.

Best,
Owen
https://changelogkit.example

Mistakes to avoid

  • Pitching a paid-only sponsorship slot as if it were a free editorial tip. Check the footer of the newsletter for 'Sponsor' or 'Submit a link' instructions first.
  • Sending a five-paragraph company history. Curators need to know what the product does, who it is for, and where the link goes in under thirty seconds.
  • Writing the sample blurb full of adjectives like 'revolutionary' or 'best-in-class.' Editors delete promotional language immediately.
  • Attaching heavy press-kit ZIP files or unrequested PDFs. One clean URL to a clear landing page is all an editor wants.

Pritam Ghosh runs Hauntboard and maintains these templates.

Published · Updated

Ready to put your launch in front of real visitors?

A person reviews every launch on Hauntboard, and every view and visit it sends your site is published on your launch page. Free to submit.

Launch free →

On the board

All →

Still hiding your app?

Put it on the board. Reviewed by a person, free to launch.

Launch free
Submit a launch