Indiecity

Guide · 17 Aug 2026 · 16 min

How to start a founder newsletter that sells the product

Field guide

A short list, one promise, and the email you send every week.

You can ship a product this week. In 2026 that is not rare. What you can still own is the inbox. A founder newsletter is a recurring letter to people who asked for it, written so they pay for the letter or pay for the product the letter sells.

It is not a brand magazine. It is not a vanity open-rate chart. Indiecity is for one person or a team under twenty. You do not need a media company. You need a small group that trusts your next email enough to read a price.

Pieter Levels put the hard part plainly in June 2026: everyone can build apps with AI. Almost nobody has an audience, money for ads, or a free way to get seen. A newsletter will not magically create demand. It will give you a place to talk to people who already care, on a schedule you control.

Pick the job: letter is product, or letter sells product

Each issue needs one primary job.

  • Letter is the product: people pay for the research, the brief, the weekly shortlist. The email is what they buy.
  • Letter sells the product: the free issues teach the job and the product is the paid fix (SaaS, service, course, template).
  • Hybrid later: free issues for reach, paid tier or product for revenue. Start with one primary job so you know what to measure.

Kevin Conti’s Software Ideas is the first path in public. In 2020 he turned market research into a paid newsletter for B2B SaaS founders and wrote that he hit $6k MRR in three months. He pre-sold it before treating it like a finished media brand. The letter was the product. He did not wait for a giant free list to prove the idea. The method still holds: sample, pre-sale goal, then send.

Indie Hackers · u/Kevin Conti

How I grew Software Ideas to $6k MRR in three months

Paid newsletter as the product: free sample posts, pre-sales with a hard goal, then growth on channels he had already tested.

Arvid Kahl runs the second path in public. The Bootstrapped Founder is a free weekly letter and podcast that sells books, a course, and attention for Podscan. The letter is how people find the products. Copy the job split, not his tools: one voice, one cadence, clear offers.

If you only collect emails and never choose a job, you have a waitlist with better branding. Recognition is not revenue. So pick who the letter is for before you pick a subject line.

Write for the smallest viable audience

Seth Godin calls it the smallest viable audience: not a compromise, a choice. You pick who it is for and what it is for. You make something those people would miss if it stopped. Be specific. A letter for “founders and marketers and anyone building online” is a letter for no one.

Not everyone, but someone. And it turns out that ‘someone’ isn’t as easy as it sounds.

Name one job title. Name one recurring pain. Name one outcome. That is the signup line, the subject pattern, and the filter for topics. If an issue does not serve those three, cut it. Godin’s other useful rule still holds: permission is anticipated, personal, and relevant. If you stop sending and nobody notices, you never had permission. You had an address dump.

A feed can disappear. A list you write to stays, if you keep the promise. That is why you start with people you can name, not a splash page for strangers.

Start with people you can name

Do not wait for a public launch to fill the list. Write the first thirty to fifty addresses by hand.

  • Past clients, coworkers, and buyers who already hit the problem
  • People who complained in Slack, Discord, email, or a call
  • Forum or review writers who named the pain in public
  • Friends of friends in the same job, if you can get a warm intro
  • Anyone who already pays you for adjacent work

Justin Jackson’s rule for early customers is personal email to people who might care, not ads or SEO first. Your first newsletter readers can be the same people. Invite them with a one-line promise, not a splash page full of features.

Invite someone you know
Hey [name]. I’m starting a short [weekly/biweekly] note for [job title] who still [pain in their words]. Promise: [one outcome or one useful thing each issue]. No spam, easy unsubscribe. Want on it? Reply yes and I’ll add you, or use this link: [signup].

Paul Graham still says you cannot wait for users to come to you. The same is true for readers. You go get the first ones. Manual invites are not a fallback. They are how a small audience starts.

Put a signup on your site the day you ship anything. Levels has long said to add email capture so you can re-engage later, and to be sparing when you write those people. A silent “we’ll tell you when we launch” box is not a newsletter. A confirmed list with a first issue on the calendar is.

Make one promise and a boring schedule

Write the promise in one sentence a stranger can understand. Examples:

  • Every Tuesday: one real workflow fix for [job] who still [pain].
  • Every other Thursday: three market gaps for bootstrappers hunting a niche.
  • First Monday of the month: what I shipped, what broke, and what is for sale.

Then pick the day. Put it on your calendar like a customer call. Solo founders fail newsletters by shipping when inspiration hits. Readers expect a rhythm. Miss three weeks and restarting is harder than starting.

Length is not the product. Reliability is. A tight issue with one story, one lesson, and one link beats a long essay you dread. If you only have twenty minutes, send twenty minutes of useful writing. Do not invent a production studio. Then the issue itself has to sell: teach first, then name the next step.

What a selling issue looks like

A selling issue is not a brochure with a greeting. It earns the click, then makes the next step obvious. Most of the issue should teach. The product is the next step, not the whole email.

  1. Subject names the outcome or the tension, not your brand.
  2. Open with the reader’s problem in their words.
  3. Show one concrete example (a mess, a fix, a before/after in plain language).
  4. Teach the principle in a few sentences.
  5. Close with a soft ask or a hard ask, never a vague “check us out.”
Issue skeleton (letter sells product)
Subject: [Outcome] without [painful workaround]

[Name the pain in one line.]

Last week a [job title] told me they still [specific mess]. Here is what actually worked: [3–8 sentences of method].

If you want that handled end to end, [product] does [outcome] for [price]. Start here: [payment or signup link].

If this is not your problem, forward it to the person who owns it. Reply and tell me what you tried.
Issue skeleton (letter is the product)
Subject: [This week’s deliverable in plain words]

Here is this issue’s [research / shortlist / brief].

[Body that delivers the promise in full for paid readers, or a strong sample for free readers.]

Paid plan: [price] for [what they get next]. Subscribe: [link].

Questions about the method? Reply. I read them.

Soft ask: one honest line and a link, once per issue is enough for free lists that sell a tool. Hard ask: price, what they get today, payment link. Conti pre-sold Software Ideas with a public sample post and a clear path to pay. He set a pre-sale goal before he trusted the idea. Compliments did not count. He left a friend’s purchase out of the goal. Compliments still do not count.

When it is launch week for a product, switch to a launch sequence. How to launch to a small email list and still get paid is the playbook: warm-up, priced launch email, human follow-up. The weekly letter keeps the list warm between those spikes.

Grow without fake milestones

Ignore round numbers. “I need 1,000 subscribers” is how people delay the ask for a year. Measure things that pay the bills:

  • Replies that name a problem in new words you can reuse
  • Clicks on the priced link
  • Trials or demos booked from an issue
  • Payments attributed to an issue or a sequence
  • Unsubscribes after a clear promise (healthy if you got specific)

Grow the list the same way you got the first names. Publish one public piece that is as good as an issue and end it with the promise and the form. Answer real questions in rooms where buyers already talk. Ask happy customers to forward one issue. Cross-promote only with writers who share the same job title, not random swap schemes.

Do not buy scraped lists. Do not scrape conference PDFs into a blast. That is not permission. Godin’s test is simple: if you stopped, would they ask where you went? Cold dumps never pass it.

A four-week start plan

  1. Day 1. Write the job (letter is product vs letter sells product). Write the one-sentence promise. Name the job title and the pain. Create the signup form and the from-name people will recognize.
  2. Days 2 to 3. List 30 to 50 people by hand. Send personal invites. Put the form on your site and in your bio.
  3. Day 4. Draft issue one using only the skeleton. Put the price or product link in if you already sell something. If the letter is the product, put the paid plan or pre-sale link in.
  4. Day 5. Send issue one on the day you promised. Track opens only as a health check. Track replies and clicks as the real signals.
  5. Week 2. Send issue two on the same weekday. Rewrite the signup line with words people used in replies. Cut anything that served a different audience.
  6. Week 3. One public sample (blog, Indie Hackers, niche forum) that ends with the same promise. Invite, do not spam.
  7. Week 4. Hard ask week if you sell a product: one issue that teaches, then states price and link without apology. Count payments, not applause. If you sell the letter, push the paid plan with a sample of what paid readers get.

Keep a simple sheet: date, subject, soft or hard ask, clicks, replies, paid. After four issues you will know if the audience is real. If twenty engaged people will not click a clear offer, the offer or the buyer is wrong. That is useful. It is not a reason to redesign the template again.

What to stop doing

  • Waiting for a big subscriber number before you name a price.
  • Writing for “everyone building online” so nobody feels chosen.
  • Sending only when you launch, then going silent for months.
  • Pasting the same ChatGPT opener and calling it a voice.
  • Measuring success by open rate alone.
  • Buying cold lists or renting attention you did not earn.
  • Turning every issue into a feature dump with no teaching.
  • Hiding the product so thoroughly that readers never learn you sell something.

How you know it is working

People reply with details. People forward the issue. Someone asks the price before you do. Someone pays after an issue, or pays for the letter itself. Those are the signals. “Great content” without a next step is politeness.

If you need the cold start before the letter can compound, pair this with how to get your first 10 paying customers without ads. The newsletter is not a substitute for asking humans to pay. It is how you talk to them again after the first ask.

Then you have a channel

Shipping is cheap in 2026 and attention is noisy. A founder newsletter is still simple: a small audience, one promise, a day you keep, and a clear path to money. The letter is the product, or it sells the product. Pick one.

When money moves and the story is yours, write it down. When the product is real, put it on the map. You can join Indiecity while you send the first four issues. Tuesday’s email is still yours to write.

Pick the job. Name the someone. Send the first issue this week.

FAQ

Questions people get stuck on

Do I need thousands of subscribers before I start?

No. [Seth Godin’s smallest viable audience](https://seths.blog/2022/05/the-smallest-viable-audience/) is the point: not everyone, someone. Ten people who open and reply beat a thousand silent addresses. Start with people who already feel the problem. Grow from buyers and intros, not from a vanity total.

Is the newsletter the product, or does it sell a product?

Pick one primary job. Either readers pay for the letter itself (research, briefings, a paid issue), or the free letter sells a tool, course, or service you already charge for. Mixing both is fine later. Starting without a job is how you get a hobby inbox.

How often should I send?

Often enough that people remember you, rare enough that you keep the promise. Weekly is a strong default for a solo founder. Biweekly works if the research is heavy. Daily is almost never required. Miss the schedule and you train people to ignore you. Pick a day and protect it.

What if I hate writing long essays?

Then do not write essays. Send short notes: one problem, one example, one link or ask. [Justin Jackson’s advice](https://justinjackson.ca/100-emails) for early customers is personal email, not a magazine. A useful 300-word issue beats a polished 2,000-word post you never ship.

When do I ask for money?

When the issue has earned attention and the offer matches the problem you just named. Soft ask: a clear line about the product with a link. Hard ask: price, payment link, and what happens after they pay. Do not wait for a round number of subscribers. [Launching to a small list still works](/stories/launch-small-email-list-get-paid) if the people care.

Is a waitlist the same as a newsletter?

No. A waitlist is people who typed an email for a future product. A newsletter is a recurring promise you keep. Recognition is not demand. [Waitlist vs charging on day one](/stories/waitlist-vs-charging-day-one) is the split. If you only collect addresses and never send, you do not have a list. You have a spreadsheet.

What tool should I use?

Whatever lets you collect addresses, send on schedule, and add a payment link without a week of setup. Kit, Buttondown, Beehiiv, Loops, or plain transactional email all work at the start. The tool is not the product. The promise and the cadence are.

How is this different from posting on X every day?

You own the inbox. Algorithms do not. [Pieter Levels has said for years](https://levels.io/bootstrapping) to capture emails so you can re-engage later, and not to spam. Daily social posts can help discovery. The letter is how you talk to people who already chose to hear from you. It also works if you [grow without posting on Twitter every day](/stories/grow-saas-without-twitter-every-day).

What if nobody opens?

Check the promise and the subject. Write to one job title about one pain. Send personal follow-ups to people you know. If twenty people who opted in never open three issues in a row, the audience or the topic is wrong. Change who it is for. Do not buy a cold list to paper over that.

Can the letter sell a SaaS and still feel useful?

Yes, if most of the issue solves a problem in the reader’s words and the product is the next step, not the whole message. Teach the job. Show what broke. Link the tool that removes it. Pure brochure emails get deleted. Pure free content with no ask never pays the server bill.

More from the journal