SEO and marketing decision
SaaS.fyi
A small, SEO-friendly directory with submission and admin review is realistic for one technical user to build and maintain; the main value you can't reproduce is the site's existing brand/audience.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$50one-off30 h to build
$0/mo3 h/mo upkeep
No published price to break even against.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- A minimal self-hosted SaaS directory where an editor can accept submissions, publish curated listing pages and collections, and let visitors search and browse tools.
What it still won’t have
- The SaaS.fyi brand, audience and editorial trust
- Any traffic or backlinks the live site has
- The site-maintained badge program and featured placement on SaaS.fyi
What remains hard
- Brand trust
Hand-picked software. Zero algorithms.
First-year cost
No published price
SaaS.fyi does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal hand-curated SaaS directory using Next.js (React) + SQLite (via Prisma) deployed to Vercel. Core features in scope: submission form with logo upload and email notification; authenticated admin UI to review/edit/approve listings and assign collection & tags; public listing index, collection pages, and detail pages with external link and badge image; search and tag filtering; sitemap and basic SEO metadata; CI tests for submission flow, admin actions and search. Out of scope: recommendation engine, paid gateway for listings, multi-tenant organizations, analytics beyond simple pageviews. Include error handling, input validation, file-size checks for uploads, automated tests, and a documented deploy script for Vercel.
How we checked
How the score was reached
- Build verdict base78
- 3 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score85
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productSaaS.fyi — homepage
- official pricingAmie — listing on SaaS.fyi (pricing shown)
- official docsCollection: SaaS directories and launch platforms
Integrity checks
What held up, and what did not.
