Favors.dev
You get featured in a newsletter by handing the writer a story their readers want, not by asking them to look at your product. A feature is earned with material, a sponsorship is bought with money, and a swap is traded with your own list. Those are three different asks, and founders lose months sending the third one while believing they sent the first.
Every niche has roughly twenty newsletters your buyers already open on a Tuesday morning. Between them they reach more of the right people than your social accounts will all year, and a mention in one of them arrives with something no ad can buy: the writer's judgment attached to it. This is the pitch-craft version of that problem, with the actual email I send, annotated, and an honest audit of whether you are worth featuring yet.
What does getting featured in a newsletter mean?
A newsletter feature is an unpaid editorial mention: the writer chooses to cover your product, tool or story inside the body of an issue because it serves their readers. It can be a two-line callout in a links roundup, a paragraph in a weekly digest, or a whole issue built around something you did. What makes it a feature rather than an ad is that nobody paid for the placement and the writer keeps editorial control.
That distinction is the entire reason the tactic works. Readers have been trained by a decade of email marketing to know exactly where the sponsor block sits, and their eyes travel past it. The recommendation two paragraphs above it does not get skipped, because it reads as the writer talking. You are not buying attention. You are borrowing trust, which is why the bar to get in is higher and the return is better.
An ad interrupts the issue. A feature is the issue. That is the whole difference in conversion, and it is why the pitch has to be about their readers rather than your product.
Feature, sponsorship or swap: which ask is right?
Pick the ask that matches what you currently have: a story means pitch a feature, a budget means buy a sponsorship, a list of your own means propose a swap. Founders mix these up constantly, usually by sending a pitch that reads like an ad request to a writer who only runs editorial.
| The ask | What it costs you | Control and conversion | Use it when |
|---|---|---|---|
| The featureAn editorial mention: the writer covers you because the story fits their issue | A pitch and a story worth telling | None. They write it, they cut it, they may never run itHighest. It arrives as a recommendation, in the writer's voice | You have something genuinely new, useful or countable to say |
| The sponsorshipA paid ad slot, clearly marked, in a fixed position | Money, usually priced per thousand subscribers | Total. You write the copy and pick the dateLowest of the three. Readers have learned where the ad sits | You have budget and a page that already converts cold traffic |
| The swapA mutual mention between two lists of roughly similar size | Your own subscribers' attention | Shared. You each write your own recommendationHigh, if the audiences overlap and both sides write honestly | You already publish to a list of your own |
The ordering matters more than the table suggests. A feature costs nothing but is the hardest to earn and cannot be scheduled. A swap is the most reliable of the three, because both sides want the same thing, which is why newsletter swaps are the first channel I recommend to any founder who already publishes. A sponsorship is the one to reach for last, since paying for attention before your page converts is the classic way to turn a marketing budget into a lesson, which is the argument running through marketing a SaaS on no budget.
How do you find 20 newsletters worth pitching?
Build the list from what your buyers already read, not from a roundup of the biggest newsletters in your category. One evening is enough. Five sources, in the order that produces the best names first:
- Ask five customers. One question: which emails do you actually open? The answers are usually smaller and stranger than anything you would have guessed, and those are the ones that convert.
- Mine the recommendation widgets. Subscribe to three newsletters you already trust and read the recommendation blocks at the bottom. Every platform surfaces adjacent lists with the same reader, so this compounds fast.
- Search the niche, not the word.Your category plus "newsletter" on Substack and beehiiv gets you the obvious twenty. Your category plus a specific problem your buyers have gets you the ones worth pitching.
- Follow the thank-yous. When a founder publicly thanks a writer for a mention, you have found both a newsletter that features small products and proof that it drives something.
- Check the communities. People who run niche lists tend to hang around the same places their readers do, which overlaps heavily with the indie hacker communities you should already be in.
For each candidate, record four things and nothing else: the writer's name, roughly how big the list is, which recurring section of the issue you would fit into, and the date of the last issue. That fourth field kills more bad pitches than any other, because a good share of the newsletters you find will have quietly stopped publishing.
Size is the field founders over-weight. A list of 1,200 people who all build in your exact niche will send you more signups, and better ones, than a general business newsletter with 90,000 subscribers. Y Combinator makes the same point about press generally in its guide to getting press for your startup, which argues for a steady drip of smaller stories over waiting on one large hit. Twenty small lists you can pitch honestly is a channel. One large list you cannot reach is a fantasy.
What does a newsletter pitch that gets answered look like?
It runs under 150 words, it proves you read their work in the first line, and it hands them a finished story instead of asking them to go find one. Here is the shape I send, annotated. Read the note under each block, because the structure is doing most of the work.
The pitch, annotated
Subject: the pricing test that cost me 40% of my signups
The subject line is the story, not your company name. A writer scanning an inbox is deciding whether there is an issue in here, and a product name answers that question with no.
Hi Dana, your issue on freemium ceilings last month is the reason I finally ran a price test instead of arguing about it for another quarter.
One specific line about one specific issue, never "I love your newsletter." This is the only sentence that proves a human sent the email, and it cannot be reused for the next writer.
I moved my starter tier from $9 to $19 for six weeks. Signups dropped 40%, revenue rose 31%, and support load halved because the people who left were never going to convert. I logged every week of it, including the two weeks I nearly reverted.
The story, with numbers you counted yourself and a decision inside it. Note what is absent: no feature list, no positioning, no adjectives about the product. The admission at the end is a large part of what makes it publishable.
Happy to write it up as a short guest piece, or just send you the raw weekly numbers and a chart to use however you like. Either way it is yours, no link required.
Two options, both of them less work for the writer than declining. "No link required" is the line that converts skeptics, and you usually get the link anyway, because writers attribute their sources.
Useful, or not your thing? Either answer is fine. Mark
An easy no. Giving someone permission to decline is what gets you a reply at all, and a fast no frees you to pitch the next newsletter this week rather than waiting a month.
Send it from your own name and address, one writer at a time, never in a thread with anyone else on it. Follow up once after eight or nine days, in two lines, with something new in them. Then stop. The same discipline that governs cold email for founders applies here with one difference: a writer is not a prospect, and treating their inbox like a pipeline is how you get quietly blacklisted from a niche that has maybe forty people in it.
Four ways a good story gets binned anyway
- Pitching a launch date instead of a finding. The date is your deadline, not their story.
- Attaching a press kit. Nobody running a one-person newsletter opens a zip file.
- Asking for a call. The pitch has to survive on its own, in the inbox, in ten seconds.
- Pitching a section the newsletter does not have. Read three issues first, every time.
Are you actually featurable yet?
Most founders who cannot get featured do not have a pitching problem, they have a material problem: there is nothing in the company yet that a writer could run. Score yourself honestly against the seven lines below. Three or more of the top four and you are ready to pitch this week. Any of the bottom three and your next move is to go make something worth writing about.
You can name a number nobody else has
Something you counted yourself: what happened across 40 outreach emails, what 200 signups did in week one, what you charge and what churned. Original data is the single most pitchable thing a small company owns.
You have a story with a decision in it
Writers do not run product descriptions. They run choices: what you tried, what it cost, what you would do differently. A decision that went badly is more publishable than a launch that went well.
You built something free that stands alone
A calculator, a dataset, a template, a directory. It gives the writer something to link that helps their reader whether or not that reader ever buys from you.
Your own page can carry the traffic
One clear promise above the fold and a single next step. A feature sends people who arrive curious and leave in nine seconds if the page argues with the sentence that sent them.
Your news is that you launched
Launching is not a story to anyone outside your company. Products launch every hour. The story is the thing you learned or the thing you measured while doing it.
Your pitch works for any newsletter
If you could send it to thirty writers unchanged, it reads as a template to all thirty. Anything reusable is the part they skip.
You are asking for a favor with nothing behind it
“Would you mind sharing my launch?” gives the writer work and no material. Give them the paragraph, the number, the screenshot. Make running it easier than declining it.
The fastest way to move from the bottom of that list to the top is to go measure something. Run one experiment properly for six weeks, log it weekly, and publish the numbers whether or not they flatter you. That is also how founders end up with the raw material for podcast invitations, since both channels want the same thing: a person who did a specific thing and can say what happened.
How do you convert a feature once it runs?
Prepare the destination before the issue lands, then measure the tail rather than the spike. A mention in a mid-sized niche newsletter tends to arrive as a sharp 48-hour wave followed by a slow trickle from the archive that can run for months. Founders who set up nothing in advance capture the wave and lose the trickle.
- Match the page to the sentence. Whatever the writer said about you should be the first thing a visitor reads on your page. A mismatch here wastes the whole placement.
- Use a link you can measure. One tagged URL per feature. Without it you will be guessing about your best channel for the rest of the year.
- Ask for the email, not the trial. Curious readers are not buyers yet. Capturing them into your own list is what turns one issue into compounding growth, which is the whole argument behind getting your first 1,000 subscribers.
- Report back within a week. Send the writer what actually happened, with real numbers. Almost nobody does this, and it is the highest-return email in the whole sequence.
There is a second, slower payoff that did not exist a few years ago. AI referrals to top websites rose 357% year over year to 1.13 billion visits in June 2025 on Similarweb's numbers, and yet AI still accounts for under 1% of publisher referral traffic. The click is not the whole prize any more; the citation is. Answer engines assemble responses from named-author writing, community discussion and reviews, and research from 5W found that Wikipedia and Reddit alone drive over 25% of ChatGPT citations in the US. A newsletter feature that also lives on a public archive page is exactly the shape of source those systems quote: attributed, dated, written by a named human about a specific company. Ask the writer whether issues get published to the web as well as the inbox, and prefer the ones that say yes.
One feature is a spike. Four features across a year, from writers who now know your name and have your numbers on file, is a channel. The gap between those two outcomes is almost entirely the follow-up email nobody sends.
Frequently asked questions
How do you get featured in a newsletter for free?
You get featured for free by giving the writer material they would have wanted anyway, rather than asking for a favor. Pick newsletters whose readers overlap with your buyers, read three recent issues to learn which section of the issue you would fit, then send a short pitch that hands them a specific story with a number in it and a link they can use. Editorial mentions are not bought, so the currency is usefulness to their readers. Founders who send a product description get ignored; founders who send a countable finding get run.
Is a newsletter feature better than a sponsorship?
For an unknown product, yes, and it is not close. A feature arrives inside the part of the issue people actually read, written in the voice they trust, so it lands as a recommendation instead of an interruption. A sponsorship is clearly marked, sits in a position readers have learned to skip, and costs money you probably need elsewhere. Sponsorships have one real advantage, which is control: you choose the date and the copy. If you have to hit a launch date on the calendar and you have budget, buy the slot. Otherwise earn the mention.
How do you find newsletters in your niche?
Start from what your buyers already read rather than from a directory of the biggest newsletters in your category. Ask five customers which emails they open, search your niche plus the word newsletter on Substack and beehiiv, look at who your competitors' customers thank publicly, and read the recommendation widgets at the bottom of every newsletter you already subscribe to, since those point at adjacent lists with the same reader. An evening of that produces twenty candidates, which is more than you can pitch properly in a month.
How long should a newsletter pitch be?
Under 150 words, in four short paragraphs: one line proving you read their work, two or three lines of the actual story with the number in it, one line saying what you can give them, and one line closing with a low-friction yes or no. Writers scan on a phone between other work. A long pitch does not read as thorough, it reads as work, and work gets archived. Anything the writer might need but the pitch does not need should sit behind a single link.
What happens after your product gets mentioned in a newsletter?
Expect a sharp spike over roughly 48 hours, then a long tail from the archive, and plan for both. Have the destination page ready before the issue lands, use a link you can measure, and put your one next step above the fold. The spike itself matters less than what you keep from it: an email address, a reply, a piece of feedback. Then close the loop with the writer by telling them what the mention actually did, because concrete results are what turns one feature into a relationship.