Learning and careers decision

True Work From Home

A capable engineer can build a useful job-board replacement in about a week, but replicating the site's curated verification, existing extension/mobile apps, and brand reach makes a full replacement impractical for a single developer.

Visit website

Built by Hamid Siddiqui, who ships 3 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-off34 h to build

$40/mo6 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 browses searchable remote job listings, saves/applies, and builds a public resume/profile.

What it still won’t have

  • Manually hand-reviewed / curated verification process and trust signals
  • Existing Chrome extension and mobile apps
  • Large indexed inventory and potential brand traffic
  • Any paid employer relationships or posting workflows

What remains hard

  • Execution qualityTrue Work From Home is now on mobile
  • Brand trustTrue Work From Home hand reviews every listing before publishing - but you should still verify each company independently before applying.
  • Execution qualityGet the Chrome extension
Read the build prompt

First-year cost

No published price

True Work From Home 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 minimal remote-job board using Next.js (React) frontend + Node.js/Express API, Postgres (managed like Supabase) for storage, and Redis for short-term caching. Core features in scope: job listing ingestion (manual admin posting UI), category & keyword search, pagination, job detail pages, account signup/login (email auth), public user resume/profile builder, saved jobs, and email alerts for saved searches (SendGrid or SES). Out of scope: automated large-scale scrapers, Chrome extension, native mobile apps, employer billing/paid posting. Include basic admin moderation pages, input validation, error handling, unit+integration tests, CI config, and a Docker-based deploy to a single cloud VM with instructions for managed Postgres provisioning.
How we checked3 sources · 2/3 runs agreed · evidence score 55

How the score was reached

  • Partly verdict base52
  • 3 cited sources+3
  • Evidence score55

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! 3 moats quoted from the page