Lynkin · Free tool
LinkedIn warm-up planner
Build a conservative 4-week invite and message ramp for companion-first LinkedIn automation. Print it, set caps in Lynkin, and adjust from accept rates — not vanity volume.
Reviewed by Sarah, Marketing Manager (sarah@neojn.com) · 2026-09-01
Plan inputs
This planner suggests conservative daily ceilings — not LinkedIn policy and not a guarantee. No tool can promise zero restrictions. Pair with warm-up guide and safety.
| Week | Invites / day | Messages / day | Operator notes |
|---|---|---|---|
| Week 1 | 9 | 6 | Pair companion; enable warm-up; watch ignore rates daily. |
| Week 2 | 13 | 9 | Raise slowly; pause if LinkedIn shows warnings. |
| Week 3 | 16 | 12 | Raise slowly; pause if LinkedIn shows warnings. |
| Week 4 | 20 | 15 | Hold at target only if accept rates stay healthy. |
Printable checklist
- Keep LinkedIn open with the Lynkin Chrome companion paired during work hours.
- Set risk caps in-product at or below this schedule (Brand-new or rarely used).
- Review accept/ignore rates twice weekly; lower caps if ignores spike.
- Pause automation immediately on any LinkedIn warning — see account restricted guide.
- Own replies in inbox CRM the same day — volume without ownership looks spammy.
Ready to run this in product? Start a free Lynkin trial · Warm-up & risk caps
Warm-up planner FAQs
Is this schedule “safe” according to LinkedIn?
No vendor schedule is an official LinkedIn policy. These ceilings are conservative operator heuristics. Pace by accept/ignore rates and pause on warnings.
Does Lynkin enforce this plan automatically?
Set warm-up and daily risk caps in Lynkin to match or stay below the plan. The companion executes on your live tab within those caps.
What if my target is higher than 50 invites/day?
This planner caps suggestions deliberately. Higher volume usually needs stronger proof that accept rates and reply ownership can keep up — not just bigger numbers.
Can I use this without Lynkin?
Yes — the schedule is free guidance. Lynkin helps apply warm-up, caps, and Activity Control in a companion-first stack.
Related: Warm-up guide · Connection limits · Is automation safe?