Your Job Search Needs a CRM: How to Track Applications Like a Sales Pipeline

Sales has Salesforce. Support has Zendesk. Marketing has HubSpot. Job seekers have a spreadsheet they stop updating in week three. Here's how to fix that.

There is a pattern I've watched play out with every serious job seeker I know. Week one, they open a fresh Google Sheet. It has beautiful columns: Company, Role, Date Applied, Status, Contact, Resume Version, Notes. Week two, they're still updating it. By week three, the sheet has rows that just say "applied" and nothing else. By week four, they've stopped opening it.

Meanwhile, actual sales professionals — people whose job it is to track 50+ active opportunities through a pipeline — never use spreadsheets. They use Salesforce or HubSpot. Not because those tools are cheap or simple, but because manually tracking a pipeline of 50 open-ended processes is genuinely hard, and spreadsheets fail at it.

Your job search is a pipeline of 50+ open-ended processes. It deserves the same infrastructure.

The anatomy of a sales pipeline (and why it applies)

Every sales CRM has roughly the same architecture. Understanding it makes clear why it maps so cleanly to job search:

• Accounts (companies you're targeting)
• Contacts (specific people within those accounts — recruiters, hiring managers, referrals)
• Opportunities (individual deals — in our case, individual roles you've applied to)
• Stages (a defined progression — in sales: Discovery → Qualified → Proposal → Negotiation → Closed)
• Activities (calls, emails, meetings — in our case: applied, phone screen, onsite, offer)
• Conversion rates (the % moving from each stage to the next)

Every one of those concepts exists in job search. The translation is almost comically direct:

Running sales without a CRM means losing track of deals, forgetting follow-ups, and having no visibility into what's actually working. Running a job search without one means the same thing — you're just the sales team.

What a job-search CRM should actually track

If you want to run this manually (and you can), these are the fields that matter. Most spreadsheets miss half of them.

Per-role (opportunity-level)

• Stage — Applied / Phone Screen / Technical / Onsite / Offer / Rejected / Ghosted / Withdrew. Ghosted is its own stage because it's diagnostically different from rejected.
• Days since last movement — the most-ignored-but-valuable metric. If a role has been sitting in "Applied" for 21 days with no update, it's almost certainly ghosted. You should stop mentally expecting it to come back.
• Channel — how you applied. Direct via company site? LinkedIn? Referral? Recruiter outreach? This is the single most important variable to segment on.
• Resume version used — which version of your resume did you send. Track this religiously; you'll want the data later.
• Recruiter-reached — did you contact the recruiter or hiring manager after applying? (Usually doubles response rate.)
• Referral source — if you were referred, by whom. Tracks which of your referrers actually help.

Per-company (account-level)

• Interest tier — A / B / C. You should want the A tier more than the B tier. Spending equal effort on a B-tier company as an A-tier one is a strategic mistake.
• Target role — the specific title you're going after, not just "any engineering role."
• Warm contacts — people you know there. Even vaguely. These matter later.

Rolled-up (pipeline-level)

• Conversion rate per stage — out of 100 applications, how many got a phone screen? Out of 20 phone screens, how many got to onsites? This is how you find the stage where you're hemorrhaging.
• Conversion rate per channel — what % of direct-apply vs. referral vs. LinkedIn Easy Apply converted to phone screens?
• Ghost rate — what % of your applications never got any response at all? This is a key signal of mis-targeting.

The data patterns that matter

Once you're tracking all of this, certain patterns jump out. These are the ones I see most often in real pipelines:

Pattern 1: Channel has a bigger effect than resume. Most people worry about their resume first. The data usually shows that how you applied (direct / referral / Easy Apply) matters more than what you sent. Referrals commonly convert 10× better than cold applications. LinkedIn Easy Apply commonly converts worse than direct apply.

Pattern 2: Ghost rate predicts mis-targeting. If your ghost rate (applications that got no response at all) is above 80%, you're applying to roles where you're systemically out of consideration. This could mean you're applying too senior, you're missing a credential the role expects, or the role's already been filled internally. Either way, the fix is to change what you're applying to — not to keep applying harder.

Pattern 3: Resume variants show real differences. If you're tailoring per role (as you should be), you'll accumulate 3–5 resume variants. After 30 applications, you'll usually see one variant meaningfully outperforming the others. The winning variant is usually the one where you cut the most, not the one where you added the most.

Pattern 4: Response latency predicts outcome. Responses that come within 48 hours convert to offers at a much higher rate than responses that come after 2 weeks. The 2-week responses are usually the company's backup candidates. Useful to know when managing your own expectations.

Why a spreadsheet fails at this

Every column above is technically trackable in a spreadsheet. The reason spreadsheets fail isn't capacity — it's activation energy. Every time you update a row, you have to:

1. Open the sheet.
2. Find the right row.
3. Update the status.
4. Remember to update dependent fields (stage change → reset days-since-movement counter, etc.).
5. Mentally calculate conversion rates across your whole pipeline.

Step 5 alone is usually enough to stop people. When you have 70 rows in a sheet, mentally computing "what's my Applied-to-Screen conversion rate for my senior applications where the channel was direct-apply?" is so painful that nobody does it. So the data exists and it's unusable.

A tool built for this problem handles the derivations automatically. You just update the stage, and conversion rates update themselves. That's 90% of the value.

Getting started if you want to DIY

If you don't want to use a tool, here's a lean spreadsheet template that works:

Sheet 1 — Pipeline Company | Role | Channel | Applied Date | Current Stage | Days Since Last Movement | Resume Version | Recruiter Contacted (Y/N) | Notes

Sheet 2 — Conversion rates (computed with formulas from Sheet 1) Stage breakdown | Count | Conversion % from previous stage

Segment Sheet 2 by channel. Re-compute weekly.

This will take you 30 minutes to set up and probably 2 minutes per application to maintain. It's a real system. It's not as good as a real CRM, but it beats the vast majority of people who are applying with no data.

Where tools (including ours) come in

The reason we built Hppr AI was specifically to remove the activation energy on tracking. Every application you submit through the Chrome extension is automatically recorded. Stages update by detecting responses in your email. Conversion rates compute live. You get the insight that a real CRM gives you without the 2-minute-per-row tax.

If you want the tool side of this, Hppr AI has a free tier. If you want to do it manually with a spreadsheet, the template above will serve you well — and honestly, just deciding to track your applications as a pipeline is 80% of the value. The tool is the remaining 20%.

The bigger point: every other high-stakes workflow in modern work has a system of record. Your career deserves one too.