What does a recruiting outreach stack look like in 2026?
Five layers: an ATS as the system of record, a LinkedIn seat for sourcing, an outreach layer that sends, scheduling, and measurement. Only the outreach layer is genuinely contested in 2026. Buy the seat first, skip the bundled contact database, and expect the joins between layers to be manual.
The five layers
System of record is the ATS, and nobody sensible replaces it. Sourcing is your LinkedIn seat, with Sales Navigator where the free filters cannot express the shortlist. Outreach is the layer that actually sends. Then scheduling, which is a calendar link. Then measurement, which is usually a spreadsheet and should probably stay one.
Four of those five are settled purchases you make once and stop thinking about. The contested layer is outreach, because it is the one exposed to platform risk and the one where the vendor market turns over fastest.
That is also where most of the marketing noise is. A stack diagram with nine logos on it is usually four real decisions and five subscriptions that could be cancelled without anyone noticing for a month.
What changed in the outreach layer
The browser-extension generation is the part platform changes break. The open-source LinkedIn MCP cohort is read-first, and their issue trackers show message sending failing when LinkedIn changes its markup. For a profile lookup that is an annoyance. For a req in flight it is a silent failure you notice a week late, when a candidate you thought you had contacted has not heard from you.
The second change is the assistant itself. An MCP server gives it hands: typed tools called against your live account state instead of an assistant that describes what you should go and do. Fifty tools across seven categories, usable from any MCP-capable client, with Claude first-class today on claude.ai, Desktop and Claude Code.
What has not changed is the limit. Caps are enforced server-side at 20 invitations a day and 80 a week for a new seat, with a warm-up ramp that multiplies by 0.5x in week zero and 0.75x in week one. No assistant negotiates that number upward, and any vendor implying otherwise is describing risk, not capability.
Questions for any vendor in the contested layer
Are your limits enforced or suggested? A number typed into a settings field is not a limit, it is a default. Ask what the product does when the cap is reached: refuse the send, or queue it and let it overshoot tomorrow.
What does suppression actually cover? Ask whether it spans every seat in the workspace, whether imported history counts from the moment of import, and what happens when two recruiters on one desk work the same candidate.
What do you publish about account health, and how do you measure it? We measure restrictions per managed seat per rolling 90 days and currently say measuring rather than publishing a figure whose denominator is still small. A vendor quoting a ban rate with no methodology, denominator or date is quoting a marketing line.
The integration question, answered honestly
There are no CRM, ATS, Zapier, HubSpot, Salesforce or webhook tools in this build, and that is a statement about the product rather than a roadmap tease. The join between the outreach layer and your ATS is a person and a CSV.
What that costs you is double entry and a reporting story you assemble yourself. What it buys is that nothing in your pipeline breaks because a vendor changed an API, and there is no second copy of candidate data sitting in a system nobody audited, which is worth more than it sounds once GDPR or DPDP obligations are yours to answer for.
Whether that trade is acceptable depends on your desk, and you should decide it before you buy rather than after. If a synced stack is a hard requirement, buy for the sync. We would rather write that sentence here than have you find it out in month two.
Where to spend, in order
The LinkedIn seat first. It is both the sourcing layer and the asset that gets restricted, so it is the one place where caution compounds. Navigator only when the free filters fail you: Core adds 50 InMail credits a month and does not raise the invitation limit.
Outreach second. Solo is $29 a month for one account, Operator $59 for up to three, Agency $119 for up to ten. Sends are not metered by LinkedBoost and sourcing uses credits. Check the app for the currently applicable trial terms.
Do not buy a bundled contact database for recruiting. We removed external providers in September 2026 and will not re-add them. A list where every name has a defensible reason to be there is what protects the seat, and a purchased list is the opposite of that by construction.
Two stacks that actually fit
Solo recruiter: one LinkedIn seat, Navigator if the filters demand it, Solo at $29, the ATS you already have, and a calendar link. Export the longlist from the ATS and import it before the first send so suppression is live from day one.
Small desk or agency: one seat per recruiter, Operator at $59 for up to three or Agency at $119 for up to ten, one sequence per req, and a single workspace so suppression spans the whole desk rather than one recruiter's memory. The weekly client or hiring-manager update is assembled by hand from the observability tools, because there is no white-label reporting in this build.
On measurement: a three-recruiter desk at full ramp has a ceiling of 240 invitations a week. Our own five seats averaged 41% acceptance across 861 conversations over three years, which is a useful sanity check and a poor substitute for your own number once you have one of your own.
The layers, and which one this product is
| Layer | Typical choice | This product |
|---|---|---|
| System of record | Your ATS | No. Not an ATS, and does not sync with one |
| Sourcing | Your LinkedIn seat, Navigator optional | Search through your seat, plus CSV import |
| Outreach execution | Extension, SaaS, or MCP server | Yes. 50 tools, approval gate on every send |
| Scheduling | A calendar link | No |
| Measurement | Spreadsheet or BI tool | Per-seat observability inside the workspace |
Questions people ask next
What tools do recruiters need in 2026?
An ATS, a LinkedIn seat, something that sends, a calendar link, and a way to measure. Only the sending layer is genuinely contested, and it is the only one exposed to platform risk.
Do I need a contact database for recruiting?
Not for LinkedIn outreach. Sourcing here is your own seat search plus your own CSV imports. External providers were removed in September 2026 and will not return.
Can this replace my ATS?
No, and it does not connect to one. Lead-group columns hold per-candidate outreach state, and anything your ATS needs is entered by a person.
How many seats can one workspace hold?
Up to 10 on Agency at $119 a month, up to 3 on Operator at $59, and 1 on Solo at $29. There is no unlimited tier.
Why this page exists: r/RecruitmentAgencies: "What's your recruitment tool stack in 2026?"
LinkedBoost is the LinkedIn MCP server: your agent sources, drafts, sends and works the inbox, inside caps the server enforces rather than suggests.
Related answers
The tools are identical to the sales build: the same 50, the same seven categories. What changes is the motion. Candidates reply to a specific role and a real reason, requisition deadlines push volume in exactly the direction that collapses acceptance, and there is no ATS integration here to hide behind.
An MCP server gives an AI assistant hands. Without one the assistant can describe what to do; with one it can do it, in your account, against real state. The value shows up only when the task is mechanical, repeated and needs live data.