GratisAIcareer · free field guide · local-first · no account
application pipeline gauge / career

Stop a Job Search Running Dry — Free, With Reorder Dates for Every Channel

A job search has a usage rate and a lead time, exactly like a stock item: applications go out weekly, replies arrive weeks later, and nothing warns you when the pipeline is about to run out. Two silent weeks are usually a pipeline that emptied a month ago.

The proof surface

Free path: the tool computes locally in this browser with no key and no account. Where an AI step helps, any free chat assistant works — free tiers exist (Google AI Studio, Groq), but plans and limits change, so check the provider's own page. No third-party service is claimed here as verified: UNCONFIRMED — model has no browsing access this session.

InputChannels as Source | open leads | sent per week | days to first response, plus today's date
Rare deviceWorks out the date each channel runs dry and sorts by it, so the channel with a three-week response time is refilled while it still looks healthy
Outputa pressure gauge per channel, with the needle at the week the channel empties, the past-due channels in the wash and the refill date printed on the dial
Cost$0 · local-first · no account · no card

Why the flat version breaks

A tracker shows what you have applied for, which is history. The date a channel runs out is arithmetic: open leads divided by how fast you use them, minus the days before a reply arrives. That date belongs on the list, not the number of applications.

How to use the application pipeline gauge in four passes

Count open leads, not applications sent

A lead is a live conversation: a recruiter who answered, a referral who agreed to pass a CV on, an advert from a company that replied before. Past applications with no answer are not leads, and counting them makes the gauge useless.

Enter the pace you actually sustain

Two tailored applications a week for months is a real pace; ten a week is a burst that ends in fortnight two. The gauge is a planning tool, so the number needs to survive a bad week.

Use the response time you have experienced per channel

Recruiters reply in days, referral routes and returner programmes in weeks. Those differences are what make the run-out dates diverge, and the divergence is the insight.

Refill the channel whose date has passed, then the nearest one

The gauge sorts by run-out date, and a channel past its date is already empty regardless of how many leads it shows. Send the next batch into that channel before the one that looks more promising.

SAMPLE DATA, NOT A VERIFIED CLAIM: the starter record is a four-channel job search with a referral route that runs dry weeks before the direct-application channel. Replace these values with your own source before you rely on anything.

What breaks first

Measuring activity instead of leads

Applications sent is an activity metric; it feels productive while the pipeline empties. A hundred applications with two replies is a pipeline of two.

Using a best-case response time

If a channel has never answered inside two weeks, a fourteen-day lead time will date the refill too late. Use the median of what actually came back.

Letting the gauge justify applying everywhere

The point is to refill the channels that work, not to spray the market. A channel with no replies after twenty sends is telling you something about the channel.

What you pay otherwise

The usual routeWhat it leaves outCost
A job-board premium planMonthly fee for automated applications into the channel with the lowest reply rate$20–$50 a month
A recruiter at 20 per centPlacement fee on a role the direct channel would have filleda fifth of the salary
Applying only when motivatedChannels that run dry in the quiet weeks, which is when applications matter mostthe months of search
This page + the free application pipeline gaugeComputed in your tab, result on screen before you type anything$0

Try the free application pipeline gauge right here

Load the starter search and change the direct-application pace to 4 a week to watch the run-out date pull forward.

FIRST-LOAD · sample record filed

Take it into the free application pipeline gauge

The companion app runs the same logic with a numbered intake, three starter records, a stateful share link, the one-time printable layer, and the local history shelf.

Open the free application pipeline gauge →

Keep the work if you will use it again

Free coreComplete on-screen result at $0

The full gauge: every channel dated, sorted by run-out date, with days of cover and the past-due channels flagged, unlimited re-runs.

$4 · one-timePrintable copy + saved history on this device

The on-screen result is free and complete. The one-time layer adds a tangible file you keep and the saved history that comes with it.

Go deeper in the companion app →

Boundary: This dates a pipeline from numbers you enter; it does not promise interviews, verify job postings or assess employers. Recruitment practices, data rights and any agency terms are governed by your local rules — check who is holding your details and on what basis.