Health, home and travel decision

Dentalclinicclosetome

A small technical person can reimplement the core directory and paid-listing flow in ~30 hours and operate it for modest monthly costs; there are no evident durable moats on the site pages to prevent replacement.

Visit website

Built by Yuyu, who ships 11 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

$50one-off30 h to build

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

  • Search and browse clinic listings by location; store and serve clinic & dentist records; accept and validate new clinic submissions; render listing pages with reviews and opening hours; support paid 'premium placement' upgrades via a payment provider.

What it still won’t have

  • Existing site SEO, domain age, and organic traffic
  • Established listings and user reviews
  • Brand recognition and any paid-ad sales relationships
  • Built-in analytics or integrations already wired on the live site

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Dentalclinicclosetome 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 location-based clinic directory web app using Next.js (React), PostgreSQL, and Node.js. Core features: (1) data model and migrations for clinics, professionals, reviews, and premium flags in Postgres; (2) authenticated admin UI to approve/edit listings; (3) public search UI with state/city filters and geolocation-based sorting; (4) listing detail pages with hours, contact, and reviews; (5) submission form with image upload and server-side validation; (6) Stripe integration to purchase/promote 'premium placement' and mark listings; (7) deploy on Vercel (frontend) and a hosted Postgres (Supabase or Railway). Out of scope: building a mobile app, training ML models, or automated review moderation. Include error handling, input validation, and unit + integration tests for submission, payment flow, and search APIs.
How we checked3 sources · 2/3 runs agreed · evidence score 81

How the score was reached

  • Build verdict base78
  • 3 cited sources+3
  • Evidence score81

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.

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded