SiteArcade
SiteArcade solved real website-maintenance pain for authors and reached about $1k MRR. The founder later reported high support burden, scattered feature expectations, and a market that behaved more like low-budget B2C than professional B2B.
Visit productProduct snapshot
What it was
SiteArcade is a SaaS platform for authors that builds and maintains author websites with automatic Amazon syncing, branding, hosting, domains, email, and press-kit features.
Who it was for
Problem / value
Turn book metadata and author inputs into a professional, auto-updating website with less technical effort.
Core workflow
Authors created websites, synced book data from Amazon, hosted custom-domain sites with branded email, and generated pages or press kits for marketing.
Core dependency
The product needed author willingness to pay enough annual revenue to cover support and feature complexity.
Product form
Pricing model
Public pricing page lists annual plans at $75/year, $150/year, and $300/year, with no monthly plans and payment due only when the user is ready to publish.
Competitors or alternatives
What happened
Summary
SiteArcade marketed itself as a fast author website builder with website, domain, email, Amazon import, design, marketing, book showcasing, and hosting features.
Outcome
The Indie Hackers shutdown note says the product had flat $1k MRR, authors wanted WordPress plus SiteArcade features, and support cost more time than annual subscription revenue justified.
Core risk
Vertical Saas Willingness To Pay And Support Burden
Timeline
- Founder project page says work began on February 1, 2020.
- Public pricing and marketing pages remain accessible as of 2026-05-20.
- Founder reported a shutdown decision on Indie Hackers dated December 19, 2023, saying the platform gave authors a full migration year.
Before you build
Why it matters
SiteArcade solved real website-maintenance pain for authors and reached about $1k MRR. The pre-build question is whether independent authors, traditionally published authors, and self-published authors have enough urgency, budget, and repeat behavior to support this workflow through a channel you can keep reaching.
Primary check
Validate annual pricing, support load, and must-have author features before shipping a full vertical website platform.
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 independent authors, traditionally published authors, and self-published authors without a one-off launch spike?
- What evidence would show Vertical Saas Willingness to Pay and Support Burden before you build more?
- Define which segment among independent authors, traditionally published authors, and self-published authors pays first and why the problem is urgent now.
- Prove the workflow happens often enough to justify buying.
- Test one acquisition channel for independent authors, traditionally published authors, and self-published authors before relying on launch traffic.
- Write down why a buyer would switch from WordPress, Squarespace, and Carrd-style website builders.
Relevant if
- You are building a web app for independent authors, traditionally published authors, and self-published authors.
- The product promise is specific: Turn book metadata and author inputs into a professional, auto-updating website with less technical effort.
- You have interest, signups, usage, or founder confidence but have not proven paid repeat use.
- Buyers can already use WordPress, Squarespace, and Carrd-style website builders or avoid switching altogether.
Less relevant if
- You already have paying independent authors, traditionally published authors, and self-published authors 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 independent authors, traditionally published authors, and self-published authors.
- 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 WordPress, Squarespace, and Carrd-style website builders and ask what would make the buyer switch now.
Transferable lessons
- Validate whether a niche audience behaves like B2B or B2C before pricing and support assumptions harden.
- Treat enthusiastic solution feedback as weaker than evidence of repeated payment and low-touch onboarding.
- Estimate support cost for non-technical users before committing to low annual pricing.
- Beware vertical products where customers want a full incumbent platform plus your differentiated features.