Before You Build
English
English中文日本語
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

RPG Campaign Starter accepted payments, got a small amount of early usage, and was abandoned after fast feedback from the tabletop RPG niche. The pre-build question is whether tabletop RPG game masters, Dungeons & Dragons players, and Pathfinder players have enough urgency, budget, and repeat behavior to support this workflow through a channel you can keep reaching.

Primary check

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

Checklist

  • Who owns the budget for this problem?
  • What repeated event triggers the buyer to use this every week or month?
  • Which channel reliably reaches tabletop RPG game masters, Dungeons & Dragons players, and Pathfinder players without a one-off launch spike?
  • What evidence would show Weak Domain Fit and Willingness to Pay Validation before you build more?
  • Define which segment among tabletop RPG game masters, Dungeons & Dragons players, and Pathfinder players pays first and why the problem is urgent now.
  • Prove the workflow happens often enough to justify buying.
  • Test one acquisition channel for tabletop RPG game masters, Dungeons & Dragons players, and Pathfinder players before relying on launch traffic.
  • Write down why a buyer would switch from free community-created tabletop RPG content, low-cost RPG campaign resources, and existing Dungeons & Dragons and Pathfinder campaign material.

Relevant if

  • You are building a web app for tabletop RPG game masters, Dungeons & Dragons players, and Pathfinder players.
  • The product promise is specific: It attempted to save game masters preparation time by packaging campaign-starting material as a purchasable tool or content product.
  • You have interest, signups, usage, or founder confidence but have not proven paid repeat use.
  • Buyers can already use free community-created tabletop RPG content, low-cost RPG campaign resources, and existing Dungeons & Dragons and Pathfinder campaign material or avoid switching altogether.

Less relevant if

  • You already have paying tabletop RPG game masters, Dungeons & Dragons players, and Pathfinder players who repeatedly use the workflow and renew or expand usage.
  • The product is an internal tool with a mandated user base and no external go-to-market risk.

Pre-build tests

  • Run the workflow manually for a small group of tabletop RPG game masters, Dungeons & Dragons players, and Pathfinder players.
  • Ask one buyer to pay, renew, or sign a dated pilot before building the next version.
  • Test one non-launch acquisition channel and count qualified conversations, not page views.
  • Put the offer next to free community-created tabletop RPG content, low-cost RPG campaign resources, and existing Dungeons & Dragons and Pathfinder campaign material and ask what would make the buyer switch now.

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.