WantRemoteJob
WantRemoteJob was a self-funded job board for real permanent remote IT roles.
View original storyProduct snapshot
What it was
WantRemoteJob listed permanent remote IT jobs and planned to support screening, testing, and final-offer workflow in one place.
Who it was for
Problem / value
Make it easier to find and post truly remote permanent IT roles.
Core workflow
- post permanent remote IT jobs
- find truly remote roles
- screen applicants
- manage offer workflow
Product form
Pricing model
Planned $99 fee for a 30-day employer job post; no revenue was generated.
Competitors or alternatives
What happened
Summary
WantRemoteJob was built as a remote IT job board, but the founder found too little verified supply, no paid employer traction, and too much ongoing operational work.
Outcome
WantRemoteJob generated zero revenue and was shut down after the founder concluded it would not pay off and needed more time and people.
Core risk
A job board was built before verified employer supply, payment intent, and curation capacity were proven.
Shutdown reason
The founder cited insufficient market research, little data, thin true-remote job supply, and too much ongoing business and operational work.
Demand signal
The founder found only about 10-20 truly remote positions to show, and many listings that looked remote still had office, timezone, contractor, or HR restrictions. The product was built before the supply problem and employer payment path were proven.
Distribution issue
The founder had a targeted contact list, but that was not enough to create a reliable employer-side supply loop. Search, email marketing, and broader buzz were left aside, while cooperation with companies interested in permanent remote work remained underdeveloped.
Timeline
- idea formed around permanent remote IT jobs in mid-2017
- product built in about three months of full-time work
- contacts invited to try the product
- only about 10-20 true remote positions available to show
- project shut down after zero revenue and $5,000-$6,000 of expenses
Before you build
Why it matters
Listings marketplaces need trustworthy supply and paying demand. A developer can build the board quickly, but cannot code around missing employer commitment or weak supply quality.
Primary check
Validate true job supply, employer payment, and ongoing curation work before building a full job board and screening workflow.
Checklist
- Manually collect and verify 20 listings before coding.
- Ask employers to pay for a small listing package upfront.
- Track how many job seekers or buyers get a useful match from the first supply batch.
- How many verified supply items can you show today?
- Will listers pay before the board has scale?
- Who keeps listings fresh and removes low-quality supply?
- What restrictions make supply less valuable than it appears?
Relevant if
- You are building a job board, marketplace, or directory.
- Your product depends on fresh listings from third parties.
- You assume a niche has enough verified supply because demand is personally relatable.
Less relevant if
- You already have paying listers and fresh supply.
- You are building an internal hiring tool, not a public marketplace.
Pre-build tests
- Run a spreadsheet or newsletter version first.
- Manually match job seekers and companies in one role category.
- Interview HR teams about true remote requirements before building screening tools.
Transferable lessons
- Validate true supply before building the board.
- Collect payment from employers before adding workflow features.
- Estimate ongoing curation, support, legal, and business setup work.
- Use a contact list to test transactions, not just interest.
If you build this today
Start as a manual matching service for one narrow role category. Verify every employer posting, collect payment for a small number of real listings, and only build screening or offer workflows after both job seekers and companies repeat the process.