Fetcher Data Is Deleted After Nov 19. Rescue Half-Sent Sequences First
Fetcher shut down Oct 16 after Juicebox bought its assets. Get data out before Nov 19, find lost replies, and resume stalled sequences before switching tools.
Fetcher shut down on October 16, 2026, ten days after Juicebox announced it was buying the company's assets. If your team ran outreach through it, some of your candidates probably got the first email of a three-step sequence and nothing after it, and some of their replies may never have reached you. Whatever account data is left gets deleted after November 19. So do things in this order: rescue the half-sent sequences first, and choose a Fetcher alternative after that.
What did Juicebox actually buy from Fetcher?
Juicebox bought Fetcher's intellectual property and other assets. It did not buy the running business, and Fetcher turned its product off on October 16, 2026. None of your candidates, threads or sequences move to Juicebox or anywhere else unless you move them yourself.
This is how the timeline went:
- October 2: Fetcher emails its customers.
- October 6: Juicebox announces an agreement to acquire Fetcher's "intellectual property and other assets."
- October 16: The platform shuts down. Running sequences stop at whatever step they had reached, and replies to messages sent through Fetcher's own email service stop arriving. This was also the last day to request a full data export. Requests made by then are supposed to be fulfilled even if the files arrive later.
- November 19: Email support ends, and so does Juicebox's offer to Fetcher customers.
- After November 19: Remaining account data is scheduled for deletion.
Fetcher admitted two weeks was a short window. It was founded in 2016, raised $38.9M in total, and says it served more than 1,500 customers and over 5,000 recruiters. Juicebox has raised $116M from Sequoia and DST Global, says it serves 5,000+ companies, and lists Cursor, Lovable, Ramp and Notion as customers. Christopher Calmeyn, Fetcher's co-founder and CEO, called Juicebox "the most compelling product on the market right now." In the same news week, Metaview raised $60M, another sign that AI recruiting tools are consolidating.
The mistake I'd warn against is reading this as "Juicebox bought Fetcher," because that phrasing suggests continuity. An asset purchase means there is no Fetcher roadmap. Juicebox's announcement also says nothing about Fetcher's human sourcers, so teams that relied on Fetcher's human-reviewed batches lost a service, not just software. And nobody cleans up after you: customers have to export their data and revoke mail and ATS access themselves.
Why are half-sent sequences worth more than the new tool?
Most replies come from follow-ups, so a candidate who got one email out of three still has most of their likely reply ahead of them. Those stalled sequences are the most valuable thing a former Fetcher team still owns.
Ashby data on more than 500,000 sequences, reported by Pin, shows a single email gets about a 7% reply rate and three emails get about 23%. A fourth email adds nothing measurable. A 2026 survey of 1,000 recruiters found a similar pattern: 8.1% replies with one email and 17.6% with a four-step sequence, and 54.1% of all replies came from follow-ups.
Fetcher's shutdown took those follow-ups away from every sequence that hadn't finished. That leaves two deadlines, and neither one is about which tool you pick. The deletion date is fixed. Thread warmth fades every week, as the subject line and opening pitch from early October slip out of the candidate's head. The tool can wait. Those two can't.
How do you get Fetcher pipeline data out before November 19?
If you requested a full export by October 16, chase the delivery through Fetcher's email support before November 19. If you didn't, rebuild the pipeline from your ATS and your recruiters' sent folders this week.
- Confirm your export status. Email Fetcher support, get written confirmation of what is coming, and ask when it will arrive. Support ends November 19.
- Pull the ATS side. Anything Fetcher synced to your ATS should still be there. Export it as a dated snapshot.
- Record the sequence step for every candidate. You need four fields: last step sent, date sent, replied yes or no, and role. The step field is what lets you migrate recruiting outreach sequences without starting them over.
- Save the template copy for each step. If you have the exact wording of steps one through three, the next message can read as a continuation and not as a new introduction.
- Revoke Fetcher's access. Remove its access to your mailboxes and your ATS. An asset sale does not clean up those permissions for you.
If you missed the October 16 export deadline, the ATS and your recruiters' sent folders are the best record you have. They are messier, but they won't be deleted on November 19.
Should you search inboxes before re-engaging anyone?
Yes. Replies to Fetcher's own mail service stopped arriving after October 16, so some candidates who look silent actually answered. Find those answers before you send anything new.
Check these places:
- Recruiters' own inboxes. Search each candidate's name and email address from October 2 onward. Some people reply to the recruiter directly instead of the original thread.
- ATS activity logs. Look for notes, stage changes or forwarded messages added by hand.
- Other channels. Candidates who got no answer by email sometimes message the recruiter somewhere else.
- Hiring managers. If an email named the manager, the candidate may have written to them directly.
Getting this wrong is costly. Imagine a candidate who said "yes, let's talk" in mid-October and now gets "just checking in." They'll assume you lost their reply, and you did. With 54.1% of replies coming from follow-ups, the shutdown cut off the stretch when more than half your answers would have arrived, which makes every reply that did arrive worth finding before you send a single "checking in" email.
How do you re-engage passive candidates without restarting at step 1?
Split your exported list into people who replied before and people who never did. Then pick up each sequence where it stopped. Don't re-run the intro.
Pin's data shows why the split matters. A nudge sent to candidates who had replied before going quiet got a 26.2% reply rate within 14 days. The same kind of nudge to candidates who had never replied got 8.7%.
| Segment | What they have seen | Next move |
|---|---|---|
| Replied, thread still live | A real conversation | Personal note from the recruiter, picking up the conversation |
| Replied, then went quiet | Intro plus an exchange | Short nudge, honest about the tool change |
| Got 1 of 3, no reply | One cold email | Send step 2 as a follow-up |
| Got 2 of 3, no reply | Two cold emails | Send the final step |
| Got all 3, no reply | The full sequence | Stop. Save them for a different role |
The trap is the import button. If you load the whole batch into Juicebox or any other tool and start every sequence at step one, people who already read your opener get it again. A duplicate cold intro reads like a mass email, and it burns the touch that should have been step two or three.
Before you send step two, confirm each person still holds the role you're writing to them about. Lists built in September are at least six weeks old, and some candidates will have moved. Refolk is useful for this: you describe the person in plain English and get their current profile back from GitHub, LinkedIn and the open web, so the follow-up goes to the job they have now.
Should you replace Fetcher with software or a sourcer?
Software replaces Fetcher's product, but only a person replaces its human-reviewed batches, and hiring that person means searching a small, noisy talent pool. Refolk's index counts about 5,735 people in the US with sourcer-type titles, and 480 in the UK.
Teams that leaned on those batches now have nobody filling the top of the funnel. Each week spent arguing about whether to buy software, hire a sourcer or call an agency is another week open roles sit with an empty shortlist.
If you do decide to hire, here is the market you're hiring from. These counts come from Refolk's index of professional profiles and use current titles.
| Segment | Count | Note |
|---|---|---|
| US sourcer-type titles | 5,735 | Sourcer, Talent Sourcer, Technical Sourcer, Sourcing Specialist |
| UK sourcer-type titles | 480 | Same titles |
| US Technical + Senior Technical Recruiters | 29,293 | Refolk's index |
| US:UK sourcer ratio | 11.9x | 5,735 / 480 |
| US tech recruiters per sourcer | 5.1 | 29,293 / 5,735 |
Fetcher said it served over 5,000 recruiters, almost as many as the 5,735 US people with sourcer titles. Not every Fetcher user was a sourcer, so treat this as a sense of scale only. Still, it shows how much sourcing work one tool was carrying.
US employers of sourcers in the sample include Rippling, EvolutionIQ and SLB. In the UK they include Deloitte, HSBC and JPMorganChase. Treat both counts as upper bounds: "Sourcing Specialist" is also a procurement title, and in Refolk's samples about 5 of 25 UK profiles and about 2 of 25 US profiles were procurement or operations roles, such as Senior Buyer or Procurement Specialist. A title-keyword search returns those buyers alongside recruiters, which is why title-only search misleads in this market.
Describing what the person actually does gets around the problem. In Refolk, you can write the brief the way you would explain it to a colleague, and the people who buy supplies drop out of the results.
What should a Fetcher alternative do that Fetcher didn't?
Pick a tool that sends from your own mailbox, can import a candidate at a specific sequence step, and lets you export everything on any day. Then the next shutdown won't cost you replies.
Use these questions when you evaluate:
- Whose mailbox sends the email? Replies to Fetcher's own mail service were lost after October 16. Mail sent from your own domain keeps arriving no matter what happens to the vendor.
- Can you import at step N? If the tool can only start a sequence at step one, you'll end up sending duplicate intros to everyone you're trying to save.
- Is export self-serve and complete? Fetcher customers had two weeks' notice. Test a full export during the trial.
- Does it write back to your ATS? If every reply, step and stage change is in Ashby or Greenhouse, that becomes the record that outlasts the vendor.
- Is it software, a service, or both? Be clear about whether you're replacing Fetcher's software, its human sourcers, or both.
Juicebox is the obvious option. Fetcher's own transition guide maps Fetcher Assist to Juicebox Agents and lists 50+ ATS integrations, including Ashby, Greenhouse, Lever, Workday and Bullhorn, and Juicebox's offer to Fetcher customers runs until November 19. That offer expires the same day support ends and the deletion clock starts, and that's a reason to do the triage this week, not a reason to sign before you've done it. Export your data, check every inbox, sort the list into the five segments above, and only then compare vendors.
FAQ
Did my Fetcher account transfer to Juicebox automatically?
No. Juicebox acquired Fetcher's intellectual property and other assets, not the business. Customers can move to Juicebox, but nothing transfers automatically. You have to export your data, rebuild sequences in whatever tool you choose, and revoke Fetcher's mail and ATS access yourself.
Can I still export my Fetcher data?
October 16, 2026 was the last day to request a full export. Requests made by then are supposed to be fulfilled even if the files arrive after the shutdown. Email support ends November 19, and remaining account data is scheduled for deletion after that. If you never requested an export, use your ATS records and your recruiters' sent folders as the record of your pipeline.
How many follow-ups should I send to candidates whose Fetcher sequence stopped?
Send enough to reach three total touches, counting the emails they already got. Ashby data on more than 500,000 sequences shows about 7% replies after one email, about 23% after three, and no measurable gain after that. A candidate who got one email should get two more, a candidate who got two should get one more, and a candidate who got all three should be saved for a different role.
The data behind this
Try it on the search you came here for
Stop building boolean strings. Just describe the person.
Type one sentence. I plan the search, read GitHub, public LinkedIn and Crunchbase records, and the open web as it is right now, and hand back a ranked list with the reason next to every name.
01Describe them
One plain sentence. Role, city, stack, stage, whatever matters to you.
02I read the web live
GitHub, public LinkedIn and Crunchbase records, the open web. Not a database that went stale last quarter.
03You read the shortlist
Ranked, with the reasoning under every name. Open a profile, ask a follow-up, narrow it down.
- Staff backend engineers in NYC who shipped Rust in production
- Series A fintechs in SF under 50 people, growing headcount this year
- Maintainers of fast-growing Rust web frameworks on GitHub
- No boolean, no filters, no seat to buy. One box.
- Read at search time, so a profile updated yesterday counts today.
- Every step visible as it runs, every name with its reason.
500 free credits on sign-up. No card, no demo call. See real searches.