Health, home and travel decision
Native Plant Seeds
A single competent developer can build and operate a useful replacement in about a week; the site is a small regional lookup without evident durable moats.
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
- User selects county + soil type + moisture → query plants database → show species list with images, attributes and planting notes → allow filtering/sorting and show FAQ/attribution.
What it still won’t have
- Any proprietary curation or endorsements the site owner might provide
- Existing site SEO/brand and historical traffic
- Potential non-public plant sourcing or commerce features (if any)
- Hosted image CDN and any paid analytics the site currently uses
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Native Plant Seeds 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 small plant-finder web app using React (Vite) frontend, Node.js + Express backend, and PostgreSQL for data. Core features in scope: county selector (list of Southern Ontario counties), soil type and moisture filters, API endpoints to query plants by county+filters, plant detail pages with image and Wikimedia attribution, an admin CSV/JSON import script to seed plant records, CI configuration and deploy to Vercel (frontend) + Render/Heroku (backend) or a single Vercel monorepo, basic page-view analytics, and unit tests for API routes. Out of scope: payments/commerce, multi-region support beyond Southern Ontario, mobile native apps, and training ML models. Require input validation, error handling, logging, and automated tests for API endpoints and import script.
How we checked
How the score was reached
- Build verdict base78
- Evidence score78
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 · 1
Every page the run actually retrieved.
- official productNative Plant Seeds — homepage
Integrity checks
What held up, and what did not.
