Learning and careers decision
Roots
A technical user can build a useful web-first replacement (lessons, quiz, subscription) in a multi-week effort, but reproducing the polished native apps, brand, and lifetime purchase trust is non-trivial without the vendor.
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.
$100one-off120 h to build
$15/mo4 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 opens daily lesson → reads 2–3 minute lesson → sees example → answers short reflection → progress recorded; optional quiz to match path
What it still won’t have
- Native iOS and Android apps with App Store polish
- Brand recognition, curated editorial voice, and lifetime purchase marketplace trust
- Deep product UX refinements (microcopy, onboarding flows, animations)
- Any proprietary content licensing or partnerships
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Roots 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 lightweight web-first PWA (React + Vite frontend, Node.js + Express backend, PostgreSQL) that delivers short daily lessons and guided learning paths. In scope: lesson model (title, thinker, path, order, content, example, reflection prompt), lesson viewer UI (2–3 minute read), user auth (email/password + optional magic link), quiz with four questions that maps users to one of four guided paths, progress tracking (per-user completed lessons), subscription gating via Stripe (one paid tier unlocking all lessons; support one-time lifetime purchase as a feature flag), an admin CSV importer for lessons, and basic analytics events. Out of scope: native iOS/Android apps, advanced personalization ML, content authoring UI beyond CSV import. Include server-side validation, error handling, and unit tests for API routes and the quiz mapping logic; provide Dockerfiles and a short README with deploy steps.
How we checked
How the score was reached
- Partly verdict base52
- Evidence score52
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.
Integrity checks
What held up, and what did not.
