Newest signal 503h oldHow the evidence is collected →

← All ideas
Build candidate· mediumMembers only

Application tracker that auto-logs from Gmail + job board emails for active job seekers

A lightweight tracker for job seekers that automatically parses recruiter emails and application confirmations into a single timeline, replacing the manual spreadsheet.

Re-researched — no candidate cleared the gates. The verdict below predates candidate-relative attribution. When this idea was re-examined, every candidate generated for it was blocked:
  • the deterministic verdict came out negative — the evidence argued against building it (VERDICT_KILL)
  • the outcome the product promises is not controlled by the product (CONTROLLABILITY_GATE_FAILED)
  • not enough evidence dimensions were resolved to decide either way (COVERAGE_BELOW_MINIMUM)
Thresholds are published at /methodology.

9 signals across 3 platforms, including 1 showing money already moving.Evaluated Aug 14, 2026 · thresholds published at /methodology

productivityb2c1-2 monthsdifficulty 3/5

Turn this into a build spec

One Universal Core, then the exact file layout your platform expects — CLAUDE.md, .cursor/rules, a Lovable knowledge base, a Bolt prompt under its 400-word ceiling. Evidence travels with it.

32 credits · every platform format after it is 5

Reading an open idea needs nothing. Generating a spec from it calls a model and costs real money, so it needs an account and credits — the cost is shown before you spend anything.

Building this?

Tell everyone else. It shows on this page and on the idea cards, and it collects in your dashboard. Ship it and add the link — we fetch it and re-check it weekly.

Sign in to tell others you're building this.

62
Signal momentum

Supporting evidence3

  • Job applicants explicitly describe maintaining spreadsheets manually to track applications, interviews, and recruiter emails across multiple threads.

  • Related complaint about job seekers juggling five disconnected tools for resume, skills, and interview tracking suggests fragmentation beyond just spreadsheets.

  • Adjacent PH launches (career page monitoring, CV tailoring, application form filling) show a cluster of founders shipping small tools into this same job-search workflow, indicating a validated user base willing to try point solutions.

Falsifying evidence4

  • Only one product (OfferTrail) is named in this exact cluster and it has no verified revenue, so there is no proof anyone pays for tracking specifically.

  • The signal is a single intent mention (S-1841) with severity 35, the lowest-severity signal in the cluster — this is a thin basis for committing two months.

  • A spreadsheet is already free and adequate for most job seekers; the complaint is about tedium, not inability, which weakens willingness to pay for a dedicated app.

  • Most adjacent demand in this cluster is actually about upstream pain (finding jobs, tailoring CVs, monitoring postings) rather than tracking after the fact, so building a tracker may miss where the real willingness to pay sits.

Most likely cause of death

The founder builds a polished tracker, but job seekers churn within one job search cycle (weeks to a couple months) because the pain is real but not persistent or costly enough to justify a subscription, and free spreadsheets or notion templates remain 'good enough'; without a wedge into the higher-severity upstream pains (finding/tailoring/applying, S-1830/S-1902/S-2898) or a recruiter-side revenue model (S-2130/S-2780/S-2783 suggest recruiters have deeper pain and budget), the product stays a nice-to-have utility with no retention or expansion path.

Demand ladder

A complaint is not a customer. Weighted ×1 / ×3 / ×8 / ×15.

Complaint 1 ×1
Would pay 7 ×3
Already paying 1 ×8
Verified revenue 0 ×15

Counted from clustered complaint signals. No candidate-relative commercial check was applied, so no revenue is attributed to this idea.

Verified revenue: not established for this idea. No record ties a revenue figure to a product selling what this would sell.

Momentum

Is this problem getting louder or quieter?

not enough history

Saturation

How many people are already on it. Most sites hide this.

42 views·0 specs·0 building
01

Problem evidence

Who feels this, how often, and why what they use today does not fix it.

Who feels it
Active job seekers running 20-100+ applications at once, mostly knowledge workers who already keep a spreadsheet. Secondary and better-funded sufferers in the same evidence block are recruiters and small HR teams, who are a different buyer.
How often
Daily during an active search, then zero. Search cycles in this block are not measured; the working assumption is 4-12 weeks of intense use followed by total abandonment once hired.
Why current fixes fail
The failure is tedium, not inability. The spreadsheet works — it just requires the seeker to re-open it after every recruiter reply, and the replies arrive in email while the sheet lives in another tab (S-1841, S-3054). Concretely: Thursday evening, after firing off eight applications through three different boards, the seeker has eight confirmation emails, two auto-rejections and one scheduling request sitting in one inbox, and copying them into the sheet is the last thing they do before giving up on it. Two weeks later the sheet is stale, so the seeker follows up on a role that already rejected them or misses an interview (S-3054). But no fix 'fails' hard enough to leave a wound: the free spreadsheet still holds, and the cost of the failure is embarrassment, not money (X-202). Meanwhile the pains the same people describe as bigger — finding roles, tailoring the CV, filling the same forms — happen upstream and are untouched by a tracker (S-1830, S-2898, S-3028, X-203).

Job seekers manually maintain spreadsheets to track applications, interviews and recruiter threads, and explicitly want to stop.

medium confidence

Status updates scatter across dozens of email threads, and the concrete failure mode is a forgotten interview or a follow-up on an already-dead role.

medium confidence

Tracking is the lowest-severity pain in its own cluster: S-1841 sits at severity 35 while adjacent job-search pains sit at 50-65.

high confidence

Most demand in this cluster is upstream of tracking — monitoring career pages, finding roles, rewriting CVs, filling forms — so a post-hoc tracker addresses the smaller half of the workflow.

high confidence

Job seekers also lose time on postings that are stale, filled or never real, which a tracker of things you already applied to does not prevent.

medium confidence

Recruiter-side pain in the same block is rated materially higher (65-75) than any job-seeker tracking pain, and one recruiter signal is already tagged as spend.

medium confidence

No record in this block shows a job seeker paying for tracking specifically; OfferTrail is the only named tracker and has no verified revenue.

high confidence

Ten of twelve signals come from Product Hunt launch copy, i.e. founders describing a problem to sell a product, not users complaining. Only S-394 (HN) and S-2130 (forum) are unprompted user voice, and neither is about job-seeker tracking.

high confidence
02

Who buys it

The person who feels the pain and the person who signs are rarely the same.

Who buys it is part of membershipThe buyer, the budget it comes out of, and what these people already pay for.
03

Product concept and MVP

Two versions: the one you deliver by hand first, and the one you build.

Product concept and MVP is part of membershipThe concierge version, the buildable version, and the features deliberately left out.
04

Competitors and alternatives

Including the free workaround people use today, which is usually the real competitor.

Competitors and alternatives is part of membershipDirect products, indirect ones, the workarounds, and where the gap actually is.
05

Pricing model

modelled

A proposal, not an observation. Benchmarks come from the data; the ladder is ours.

Pricing model is part of membershipA tier ladder with the reasoning behind each price point.
06

Revenue scenarios

modelled

Arithmetic on the assumptions listed underneath. Change an assumption and the number changes.

Revenue scenarios is part of membershipBase, upside and aggressive cases with every input written out.
07

Market size

modelled

Reachable customers, not a top-down industry figure.

Market size is part of membershipHow many buyers exist, what they spend, and how many you could realistically reach.
08

Go to market

Named places, not channel categories. These signals came from somewhere.

Go to market is part of membershipWhere the first ten customers come from, then the first hundred.
09

Roadmap

Each version ships something a user can use. No infrastructure-only phases.

Roadmap is part of membershipVersion by version, with what belongs in each.
10

Pivot paths

Where this goes if the first version does not land — and the number that says it did not.

Pivot paths is part of membershipAdjacent directions, and the measurable trigger for taking one.
11

Risks and kill criteria

The thresholds at which the honest move is to stop. Written before you are attached to it.

Risks and kill criteria is part of membershipRanked risks, and the numeric conditions under which to walk away.
12

Validation plan

Seven days that cost nothing but time and can kill the idea before you build.

Validation plan is part of membershipA day-by-day plan and the interview questions that do not lead the witness.
13

Sources and freshness

Every reference opens the original post. This is the part you should check first.

How sure are we, per claim

Where the data is thin, we say so instead of rounding up.

demand
Low
payment
No data
market size
Low
competitor gap
Low

16 references from 9 signals · evaluation written Aug 13, 2026.

Related opportunities

Nearest by what the problem actually is, not by category label.

Eleven more sections behind this one

Who signs the cheque, what the space already charges, the seven-day validation plan, and the thresholds at which you should stop. Three ideas are open in full so you can judge the depth before paying.

42 people have looked at this · 0 turned it into a spec · 0 say they're building it