Uncategorised decision

ConfettiSaaS.com

A single competent developer can build and run a small, SEO-focused startup directory in about one week; the site’s durable value is audience and editorial curation (not proprietary tech), so self-hosting a replacement is realistic.

Visit website

Built by Lars, who ships 5 products in this index

You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off40 h to build

$40/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

  • User-submitted startup listing -> admin approval -> public listing pages with SEO and category filters; visitors discover listings and backlinks are provided to listed startups.

What it still won’t have

  • existing audience and distribution
  • site editorial curation and credibility built over time
  • permanent backlinks & SEO history
  • any paid promotional/sponsorship relationships managed by ConfettiSaaS

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

ConfettiSaaS.com 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

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

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

Not run yet
Build a searchable SaaS startup directory using Next.js (app router), TypeScript, Postgres (Supabase or Neon), Prisma, and Vercel for hosting. In scope: public listing pages with SEO-friendly meta tags and category routes; a secured submission form that validates input, stores submissions in Postgres, and sends notification email via SendGrid; an admin dashboard to review/approve/edit listings and to feature entries; server-side full-text search and category filters; CSV export of listings; CI/CD, basic rate-limiting, input validation, error handling, and unit/integration tests for submission and approval flows. Out of scope: payments/sponsorship marketplace, Chrome extension, monetization UI. Deliverables must include deployment instructions, environment variable examples, tests, and basic monitoring/alerting for failed background jobs.
How we checked2 sources · 3/3 runs agreed · evidence score 83

How the score was reached

  • Build verdict base78
  • 2 cited sources+1
  • 3/3 assessment runs agreed+4
  • Evidence score83

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 · 2

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded