Before You Build
Web AppShut Down

Indie Friends

Indie Friends was a paid founder community by Pete Codes. The case is directly relevant to independent developers because it shows how a superficially simple community business can fail on market size, willingness to pay, segmentation, and founder opportunity cost.

View original story

Product snapshot

What it was

Indie Friends was a paid founder community for people building and growing indie businesses.

Who it was for

indie foundersbootstrapped foundersfounders with existing revenue

Problem / value

Give founders peer support and private community access while they built independent businesses.

Core workflow

Founders joined a private peer group, discussed indie business problems, and got support from other builders.

Core dependency

The business needed a large enough paid founder segment to justify ongoing community work.

Product form

paid online communityinvite-only free group after closure to new members

Pricing model

The product was a paid community before being closed to new members; exact pricing is not disclosed in the sources used.

Competitors or alternatives

paid founder communitiesfree founder communitiesindie founder newsletters and peer groups

What happened

Summary

Pete Codes closed Indie Friends to new members and kept it as a free invite-only group for current people.

Core risk

Too Small Market And Weak Willingness To Pay

Timeline

  • Pete Codes says he renamed the founder community to Indie Friends.
  • He later closed Indie Friends to new members and kept it as a free invite-only group for existing people.

Before you build

Why it matters

Many indie developers consider paid communities, newsletters, and info products because they seem easier than SaaS. Indie Friends shows that narrow segmentation and weak willingness to pay can make a simple-looking community hard to sustain.

Primary check

Price-test one founder segment and its recruitment cost before turning peer support into a paid community business.

Checklist

  • Can you name the first buyer segment and the repeated job they need solved?
  • Can you reach that segment without relying on one fragile channel?
  • What evidence would disprove the too small market and weak willingness to pay risk?
  • Do the market-size math before building a paid community around a narrow audience.
  • Compare a project against founder opportunity cost, not only whether it earns some money.
  • Avoid selling to audiences with many free alternatives unless the paid value is very clear.

Relevant if

  • You are building a similar ai tool with public-source distribution risk.
  • You need to validate who will repeatedly pay before investing in product polish.

Less relevant if

  • You already control a reliable acquisition channel for the exact buyer segment.
  • The product is an internal tool with no need for public distribution.

Pre-build tests

  • Run a landing-page or concierge test with the narrowest buyer segment before building the full workflow.
  • Ask users to commit to a paid pilot, not only to join a free waitlist.

Transferable lessons

  • Do the market-size math before building a paid community around a narrow audience.
  • Compare a project against founder opportunity cost, not only whether it earns some money.
  • Avoid selling to audiences with many free alternatives unless the paid value is very clear.