
LinkedIn's classifier no longer looks at what you did today. It looks at what you usually do — and flags the delta. A dormant account that opens a sequencer on Monday morning fails the same behavioral check that a brand-new account fails on day one: no baseline, no acceptance history, no comparative session pattern.
That's the shift most warm-up guides haven't rewritten for. The 4-week templates you'll find on Expandi, PhantomBuster, and Dux-Soup blogs were built for sales teams running many seats through cloud infrastructure. They don't map to a solo consultant with one account, one IP, one device — and no margin for a 72-hour restriction.
This is a compressed, 14-day protocol built for that operator: a consultant who either just created an account, reactivated a quiet one, or is connecting LinkedCamp for the first time. The goal isn't to prove you can send. It's to build a behavioral fingerprint the classifier reads as a working professional before you touch automation.
Why 14 Days Beats the 4-Week Default
The consensus number in the vendor guides is 30 days of manual warm-up before introducing automation gradually. That advice is defensible but calibrated to teams who can afford a month of zero pipeline. Consultants can't.
Fourteen days works because the classifier isn't scoring calendar age in isolation — it's scoring the combination of session realism, acceptance signal, and engagement variety. Enforcement is rarely tied to one isolated action; the algorithm evaluates overall trust signals including account age, acceptance rates, SSI score, session behavior, IP consistency, invitation velocity, and message patterns. If you hit those signals cleanly, two weeks is a defensible baseline. Miss any of them, and 30 days won't save you.
The other reason: automation on a two-week-old account with 40 connections is the fastest path to a restriction notice — the account has no history, no acceptance signal, and no organic activity for the classifier to compare against, so any automated pattern reads as suspicious immediately. The 14-day plan below fixes all three of those gaps in parallel, not sequentially.
Who This Is For (And Who It Isn't)
Built for:
- Solo consultants who just opened a LinkedIn account
- Consultants activating an account that's been dormant for 90+ days
- Anyone plugging a fresh account into LinkedCamp, HeyReach, Expandi, or any sequencer for the first time
- Fractional operators running outreach from their own name (not a team seat)
Not built for:
- Agencies onboarding 10+ client accounts (the multi-account playbook has different IP and inbox constraints)
- Established accounts already sending 15-25 invites/day cleanly — you don't need to warm anything
- Anyone planning to route through a shared cloud IP pool without a dedicated residential proxy
The Guardian-Era Detection Model
Before the protocol, understand what's watching you. Before 2021, LinkedIn allowed roughly 700 connection requests per week. That dropped to ~100 in March 2021, with high-SSI accounts often able to push 150-200 quietly. For four years, the soft ceiling stretched. The 2026 update closed that stretch.
What matters now is the cliff. From 2,400+ LinkedCamp-managed accounts between January and March 2026, restriction rates jump from 4-6% at 70-100 requests/week to 14-18% at 100-130/week — there is no gradual penalty curve. For a new account, the effective ceiling is far lower: most accounts sit in the 100–200 weekly request range, but new accounts, low-SSI profiles, and anyone with a high proportion of unanswered invites can find their effective ceiling at 20–30 per week.
Acceptance rate is the second half of the equation. A good acceptance rate in 2026 is 30-45%; below 20% risks account restriction. During warm-up, this is the number that matters more than volume — a 45% acceptance rate on 5 invites builds trust; a 12% rate on 20 destroys it.
The 14-day protocol is engineered to hit both signals simultaneously: gradual volume ramp and disciplined acceptance floor.
Days 1-3: Browsing Only, Zero Sends
No invites. No messages. No automation of any kind connected to the account. This mirrors the vendor consensus that you should use your LinkedIn account for browsing only for 3–7 days before any outbound activity.
Daily actions (spread across two 20-30 minute sessions, one morning, one afternoon):
- Complete every profile field: photo, banner, headline, About, experience, skills, featured section
- Follow 8-12 companies in your target ICP (do this manually)
- Follow 4-6 thought leaders whose posts you'd naturally engage with
- Scroll the home feed for 5-8 minutes per session — dwell on 2-3 posts
- View 3-5 profiles per session by searching real names, not scraping
- Like 3-5 posts across the two sessions; leave one substantive comment daily
This is boring on purpose. You're teaching the classifier what your normal looks like. Every metric in the 20-Invite Rule breakdown — dwell time, session length, action variety — gets seeded here.
Days 4-6: Ramp to 2-5 Invites, Manual Only
Start sending invites, but keep the daily count in single digits and send them by hand. Two on day 4, three on day 5, five on day 6.
Every invite in this window follows the same sequence:
- Search the person by name or via a saved Sales Navigator list
- Open their profile — dwell 40-60 seconds
- Like or comment on one of their recent posts
- Wait at least 6-8 hours
- Send the invite with a personalized note referencing something specific from their profile or post
Why the delay? Warm up prospects before sending requests: visit profile, like or comment on a recent post, wait 2-3 days, then send a personalized connection request mentioning shared interest or recent content — higher acceptance rates from warm prospects improve your reputation, which gradually increases your limits over time.
Continue the browsing and engagement rhythm from days 1-3. The invites are additive, not replacements.
Days 7-10: Ramp to 10 Invites, Introduce Light Automation
This is where LinkedCamp comes on. Configure your campaign at 10 invites/day, weekdays only, with randomization enabled — meaning a 10-invite cap resolves to somewhere between 7 and 13 sends per day, spread across your business hours. This mirrors what a 20-action limit becoming anywhere between 15-25 actions looks like: natural variance, not fixed pattern.
Non-negotiables for this window:
- Send only during a 4-6 hour working window (matches the 4 to 6 hour working window advice, because LinkedIn pattern-matches on burstiness more aggressively than total volume)
- Randomized delays of at least 90-180 seconds between actions
- No weekend sends — the classifier notices
- Continue manual engagement: 3-5 likes and 1-2 comments daily, on top of what the tool does
- Check acceptance rate every morning; if it drops below 30%, pause and audit your list
Send 20-30 requests per day consistently instead of 150 on Monday followed by nothing — but during warm-up, the ceiling is 10, not 25.
LinkedCamp runs AI-personalized LinkedIn + email sequences on dedicated IPs, with AI agents that book meetings while you focus on closing.
Days 11-14: Ramp to 20, Layer Follow-Up Messages
By day 11 you should have 30-45 accepts in the bank from the previous week. Now the sequence gets its second layer: follow-up messages to accepted connections.
Ramp schedule:
- Day 11: 15 invites/day, first follow-up message activated (send 3-5 days after accept)
- Day 12: 18 invites/day
- Day 13-14: 20 invites/day, weekdays only
Why stop at 20 for a solo consultant, not push toward the 25-30 ceiling? Because your durable weekly cap sits at the number where the restriction curve is flat. The math is covered in detail in the 20-30/day cap breakdown, but the short version: 100 sends/week is the platform-wide cliff, and 20/day × 5 days lands you at exactly that ceiling with zero buffer for a Saturday retry or a Monday burst.
Monitor these numbers daily during the ramp:
- Acceptance rate: Must stay above 30%. Only push toward 20 once you have three consecutive weeks above a 35 percent acceptance rate — if acceptance drops during the ramp, hold the current volume rather than climbing. For a 14-day protocol, the equivalent gate is: hold ramp if acceptance falls below 35% on any two consecutive days.
- Pending invites: Withdraw anything older than 21 days. Keep pending requests under 500 — exceeding 500 signals poor targeting and low acceptance rate, which hurts your reputation; withdraw requests older than 2-3 weeks regularly to maintain account health.
- CAPTCHAs or logout events: Any single occurrence means stop sending for 48 hours and revert to browsing-only.
The Signals That Break the Protocol
Even a clean 14-day ramp gets undone by any of the following. Treat them as hard stops:
- Shared cloud IP. If your automation tool routes through a shared datacenter IP, the classifier can pattern-match your session against dozens of others hitting the same infrastructure. Dedicated residential proxy or bust — the architecture question is unpacked in the cloud vs extension audit.
- Second device mid-warm-up. Logging in from your phone on hotel Wi-Fi during day 8 introduces an IP delta that reads as a session hijack. Pick one device, one network, for the full 14 days.
- Weekend automation runs. LinkedIn has session-time distributions per account. If you've never logged in on Saturday, don't let a sequencer send on Saturday.
- Message templates that don't vary. Sending dozens of near identical messages in a short window is its own detectable pattern. Use spintax or AI variation on every message, including the first follow-up.
- Pushing past 20/day before day 15. The whole point of the protocol is proving the baseline. Cross it early and you're back to day 1 — or worse, in a 72-hour restriction.
Day 14 Exit Criteria
You're ready to run steady-state outreach on day 15 only if all four of these are true:
- Acceptance rate over the trailing 7 days is at or above 35%
- No CAPTCHA, phone-verification, or forced-logout events in the last 10 days
- Pending invites under 100 (well below the 500 threshold, but honest about your queue depth)
- You've had at least 4-6 organic conversations in the inbox — replies that turned into actual back-and-forth, not one-line accepts
If any of those miss, extend the warm-up by 5-7 days at the current volume before ramping further. Don't push to 25 or 30/day; the marginal risk isn't worth the two additional accepts you'd gain.
- LinkedIn's post-Guardian classifier scores the combination of session behavior, acceptance rate, IP consistency, and volume — not any single number
- New and reactivated accounts have an effective ceiling of 20-30 invites/week until they build history, well below the 100/week platform cap
- Days 1-3: browse only. Days 4-6: 2-5 manual invites. Days 7-10: 10/day via automation. Days 11-14: ramp 15→20/day
- Hold acceptance rate above 30% (target 35%+) throughout; if it drops on two consecutive days, freeze the ramp
- Exit criteria on day 14: 35%+ acceptance, zero verification events, pending under 100, real conversations in the inbox
Keep reading

The Claygency Playbook: Clay + LinkedIn Is the New Default
The Claygency category has consolidated in 2026. Here's the reference stack, the handoff points, and the margin math behind every serious lead-gen shop.

3 Agencies, 30 Days: The Post-HeyReach Migration Playbook
Three anonymized lead-gen agencies walk through their exact 30-day rebuild after the HeyReach takedown — architecture audit, warm-up reset, and client comms scripts.

LinkedIn Lead Generation Services: 2026 Pricing Reset
What buyers will pay for LinkedIn lead generation services in 2026 — and the retainer line items they've stopped tolerating. A packaging guide for agency owners.
Ready to try LinkedCamp?
14-day free trial, dedicated IP, AI agents — start outbound in under an hour.