Logging. Enrichment. Routing. It’s the GTM work that eats a startup’s week. Agents can own it so your team gets back to selling.

On October 28, HubSpot and Dust run Build, Buy, or Hire? live. No panel. We build your first automated workflow in HubSpot and Dust, including a post-call automation and a Slack account ownership layer, and you take the build home.

Join the Live Build

You applied in March. You got the polite no, or you got nothing. Either way you told yourself the same comforting thing everybody tells themselves: at least I'm in their system now. Next time something opens up, I'll already be there.

Here is what nobody tells you. That system is a software subscription, and a lot of employers are about to cancel theirs.

Employ, the company behind JazzHR, Lever and Jobvite, released its annual Recruiter Nation report yesterday, built on a survey of more than 1,200 US recruiters and HR managers. Satisfaction with primary recruiting systems fell from 82 percent last year to 69 percent this year. And 64 percent said they are at least somewhat likely to change systems in the next 12 to 24 months. Read that again. Roughly two out of three hiring teams are considering replacing the exact database your application is sitting in.

When that swap happens, not everything makes the trip. Active candidates come across. Dormant records frequently do not. Your application does not get deleted because a recruiter decided you were unqualified. It gets left behind because nobody flagged it as worth the migration cost.

Migrations are not a copy and paste of everything. Teams triage. The industry playbook is consistent across vendors: move active candidates, open requisitions, recent interview notes, offer history and compliance records. Archive or drop the rest. Guidance commonly singles out profiles untouched for a year or two as the first category to leave behind.

There is a structural reason beyond cost. Historical applicants are attached to the job they applied for. If the old requisition is not rebuilt in the new system, that candidate has nowhere to land. Greenhouse, for example, treats historical data migration as a separate project from active candidate migration, running four to six weeks behind while live recruiting continues.

So the question is not whether a company likes you. It is whether your record reads as active on the day the export runs.

Most candidates treat an application as a submission with an outcome. Systems treat it as a record with a last-touched date. That date is the single field that decides whether you are high-value data or cleanup.

Activity means something concrete: a reply to a recruiter email, a new application to a second role, an updated profile in the careers portal, a response to a talent community message. A thank-you note you sent through a recruiter's actual inbox usually does nothing, because it never touched the record. A reply inside the system does.

Practical move this week: pull up the five employers you most want to work for, find the last time you touched anything inside their careers portal, and do one real action on each. Update the profile. Apply to one adjacent open role. Answer the newsletter they send you.

You can see this happening from the outside if you know the tells. The apply link changes domain, for instance moving from a myworkdayjobs.com URL to a job-boards.greenhouse.io URL, or the reverse. Automated emails start arriving from a different sender domain and land in a different inbox folder. Your old portal login stops working or sends you to a signup page you already completed. The status tracker that said "under review" for two months suddenly shows nothing at all.

Any one of those is a strong signal the employer changed platforms. Treat it as new information, not a glitch, because it changes what you should do next.

If you are mid-process when a company cuts over, you are in the riskiest spot. Teams handle in-flight requisitions three ways: freeze everything and migrate, run both systems in parallel, or move department by department. Every one of those creates a seam where a candidate stalls, duplicates, or drops.

You will not be told any of this is happening. Silence during a cutover looks identical to silence after a rejection. If you have gone quiet for two weeks in an active process and you noticed any of the tells above, send one narrow message:

That is not a nudge for a status update, which recruiters ignore. It is an operational question with a real answer, and it quietly re-touches your record on the day you send it.

TLDR AI is a free daily email curated by Anthropic and ex-Google engineers: the new tools worth trying and the research worth understanding, summarized for 1.1M+ readers.

Subscribe for free

Here is the upside almost nobody uses. Within one system, reapplying too soon can work against you. The recruiter opens one profile that carries every prior cycle, including the rejection, and some platforms enforce cooldowns.

After a migration, that history may simply not exist in the new instance. The dedupe check that would have surfaced your March rejection has nothing to match against. If a company you were rejected by six months ago has visibly changed platforms, that is a legitimate moment to re-enter as a fresh candidate rather than a repeat one.

Do not fake a new identity. Use the same name and email. Just stop treating a stale rejection as a permanent mark when the filing cabinet it lived in was thrown out.

The one party guaranteed to keep continuity across an employer's platform change is you. Keep a simple sheet: company, role title, requisition number, date applied, portal URL, recruiter name and email, last contact date.

That file is what lets you send the message above with specifics instead of vagueness. It is also what lets you say, nine months later, "I applied to req 10086355 in March and interviewed with Dana in April," to a recruiter whose new system has no idea either thing happened. Specificity you can produce is more durable than data they promised to keep.

The system forgets. Make sure you do not.

The professionals pulling ahead aren't working more. They're using Claude.

Our free guide will show you how to:

Transform your workflow with AI and stay ahead of the curve with this comprehensive guide to using Claude at work.

Get The Free Guide