GhostJob
The founder reports 23 MAU, $0 MRR, 0 Chrome Web Store reviews, and no conversions two weeks after the paid tier shipped. The product has a concrete user pain around ghost job postings, but the founder explicitly says demand is not the problem and differentiation is unproven.
View sourceProduct snapshot
What it was
GhostJob is a Chrome extension for job seekers who want to assess whether job postings may be stale, reposted, or unlikely to be real openings.
Who it was for
Problem / value
The extension overlays a 0-100 Ghost Score on Indeed, LinkedIn, and Glassdoor postings using signals such as posting age, repost frequency, industry baseline, and keyword density.
Core workflow
Score a job posting before applying; Detect old or repeatedly reposted roles; Prioritize applications toward likely real openings; See salary insights from public data in the paid tier
Core dependency
The founder described GhostJob as a Chrome extension that detects ghost job postings with a 0-100 Ghost Score overlay on Indeed, LinkedIn, and Glassdoor.
Product form
Pricing model
Founder-reported pricing is a free tier with 10 checks per day, Pro at $6 per month, or $59 lifetime.
Competitors or alternatives
What happened
Summary
The founder described GhostJob as a Chrome extension that detects ghost job postings with a 0-100 Ghost Score overlay on Indeed, LinkedIn, and Glassdoor.
Outcome
GhostJob shows a niche Chrome extension with a clear pain point but no paid conversions after shipping its paid tier.
Core risk
Niche Chrome Extension Had Usage But No Paid Conversion After Launching Pro.
Timeline
- Founder reported day 19 after launch
- Founder reported 23 MAU
- Founder reported $0 MRR two weeks after shipping the paid tier
- Founder reported 0 Chrome Web Store reviews
Before you build
Why it matters
This is a direct small-extension lesson: a real problem and some MAU do not prove that users will pay, review, or trust the signal enough to upgrade.
Primary check
Validate a paid job-search workflow and repeat use before expanding a browser extension around a narrow pain point.
Checklist
- Can you name the first buyer segment and the repeated job they need solved?
- Can you reach that segment without relying on one fragile channel?
- What happens if the platform, API, or data source changes terms or blocks access?
- What evidence would disprove the Niche Chrome extension had usage but no paid conversion after launching Pro. risk?
- For niche extensions, track reviews, activation, and paid conversion alongside MAU.
- Validate that the paid feature changes user behavior before building a multi-release roadmap.
- A competitor's apparent user count can suggest demand, but it does not prove your differentiation or price.
- If the audience is episodic and cost-sensitive, lifetime pricing may reveal more than monthly willingness to pay.
Relevant if
- You are building a similar chrome extension with public-source distribution risk.
- Your product depends on another platform, search channel, API, or third-party data source.
- You need to validate who will repeatedly pay before investing in product polish.
Less relevant if
- You already control a reliable acquisition channel for the exact buyer segment.
- The product is an internal tool with no need for public distribution.
Pre-build tests
- Run a landing-page or concierge test with the narrowest buyer segment before building the full workflow.
- Ask users to commit to a paid pilot, not only to join a free waitlist.
- Prototype the highest-risk platform or data dependency first and document fallback options.
Transferable lessons
- For niche extensions, track reviews, activation, and paid conversion alongside MAU.
- Validate that the paid feature changes user behavior before building a multi-release roadmap.
- A competitor's apparent user count can suggest demand, but it does not prove your differentiation or price.
- If the audience is episodic and cost-sensitive, lifetime pricing may reveal more than monthly willingness to pay.