Before You Build
Web AppShut Down

RPG Campaign Starter

RPG Campaign Starter accepted payments, got a small amount of early usage, and was abandoned after fast feedback from the tabletop RPG niche. The founder’s public postmortem points to niche familiarity, existing alternatives, and willingness-to-pay research before monetizing a thin MVP.

View original story

Product snapshot

What it was

RPG Campaign Starter was a paid MVP aimed at helping tabletop RPG players start campaigns for games such as Dungeons & Dragons, Pathfinder, and Starfinder.

Who it was for

tabletop RPG game mastersDungeons & Dragons playersPathfinder playersStarfinder players

Problem / value

It attempted to save game masters preparation time by packaging campaign-starting material as a purchasable tool or content product.

Core workflow

Game masters used campaign starter material to begin tabletop RPG campaigns faster and test whether a niche audience would pay.

Product form

web apppaid MVP

Pricing model

Accepted payments; exact public price was not found in the sources used.

Competitors or alternatives

free community-created tabletop RPG contentlow-cost RPG campaign resourcesexisting Dungeons & Dragons and Pathfinder campaign material

What happened

Summary

The founder said RPG Campaign Starter was his first full product that accepted payments.

Outcome

The founder said he shut down the website 36 hours after launching it.

Core risk

Weak Domain Fit And Willingness To Pay Validation

Timeline

  • Founder launched the product around March 18, 2023.
  • Founder shut down the website 36 hours after launch.
  • Indie Hackers newsletter later summarized the abandonment as a post-launch feedback case.

Before you build

Why it matters

This is a direct solo-builder case where a narrow paid MVP reached users quickly but ran into community-fit and alternative-product issues almost immediately.

Primary check

Price-test with the target RPG community before packaging paid content where free or cheap alternatives already exist.

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 weak domain fit and willingness to pay validation risk?
  • Validate paid alternatives in the target community before charging from day one.
  • Prefer problems from communities the builder understands or can research deeply.
  • Use critical launch feedback to decide whether to narrow, reposition, or stop quickly.

Relevant if

  • You are building a similar web app 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

  • Validate paid alternatives in the target community before charging from day one.
  • Prefer problems from communities the builder understands or can research deeply.
  • Use critical launch feedback to decide whether to narrow, reposition, or stop quickly.