GratisAI career · 4 min read · free tool
pipeline funnel strip

Find Where Your Job Search Is Actually Leaking

Most job-search advice assumes the problem is volume. Usually it's conversion at one specific stage. This takes your counts — applied, responded, interviewed, offered — computes the rate at each step, marks the stage where the biggest proportion drops out, and tells you how many applications one offer costs at your current rates. Local only; nothing leaves the tab.

Scan report — what this replaces
Funnel
Conversion rate at each stage of your own search
local
What it replaces
'Apply to more jobs' as a diagnosis
$0.00
Input
Four counts and the weeks elapsed
no card
Output
The worst leak and applications per offer
recomputed

What you pay otherwise

RouteWhat you getCost
Career coachSomeone reading the same four numbers$120+/session
Doubling applicationsMore of whatever is already failinghours weekly
Rewriting every CVFixing a stage that isn't the probleman evening
This pageThe stage that's actually broken$0

The workflow

  1. Count only what you can verify

    Applications you actually submitted, responses you actually got, interviews you actually sat, offers you actually received. Estimates here produce a confident-looking funnel built on nothing.

  2. Read the conversion rates, not the counts

    Twenty interviews sounds like a lot until it's 40% of your responses and 2% of your applications. The rate between two stages tells you what's broken; the count alone doesn't.

  3. Fix the worst leak before doing anything else

    A low response rate is a targeting or CV problem. A low interview-to-offer rate is an interview problem. They need opposite remedies, and improving the wrong one wastes weeks.

  4. Use applications-per-offer to plan the search

    If one offer costs you 60 applications, then a three-month search needs about five a week. That's a schedule you can commit to, rather than a vague intention to apply more.

Worked example

Sample: 96 applications over 10 weeks
  Responded    11  (11.5% of applications)
  Interviewed   6  (54.5% of responses)
  Offered       1  (16.7% of interviews)
  Worst leak   applications → responses
  Per offer    96 applications, 9.6 a week
  Uploaded     nothing — computed in the tab

Numbers above are sample data produced by the tool's own pre-loaded example, run in the browser — not averages or measured benchmarks.

What breaks this

Estimating the counts produces a confident funnel built on nothing. Reading counts instead of rates hides which stage is failing. Fixing the wrong stage — rewriting a CV when the problem is interview performance — is the most expensive mistake here.

Try it now

Ninety-six applications with an 11.5% response rate are loaded. Raise the response count to 30 and watch the worst-leak flag move to the interview stage.

Open the funnel →

Go deeper: the printable funnel

The funnel is free forever. The $4 one-time tier adds:

See the paid tier inside the tool →

What this is not. This analyses the counts you enter and cannot verify them or guarantee any outcome. Conversion rates vary hugely by sector, seniority and market — treat the diagnosis as a starting point, not a verdict on your suitability.