Fix sheet: Sending too many connection requests per day

This sheet appended when your report flagged the `volume` weakness.

The number that matters

LinkedIn's algorithmic ceiling on connection requests sits at roughly 20-25/day per account before penalty kicks in, and the penalty only fires when acceptance is under ~30% at that volume. Combine "high volume" with "low acceptance" and you enter a decay loop: requests get shown to fewer people, acceptance drops more, restrictions follow.

The 3 things to fix this week

1. Throttle. Drop daily new-request volume to 15 for 7 days, regardless of how it affects your pipeline math. Acceptance will recover in week 2 because the algorithm rewards account-level health signals over time.

1. Audit your touch 1. Re-read the connection note you are sending. If it has any of: a meeting ask, a calendly link, "I help companies like yours", or "saw your post" without naming what about the post — it is too sales-y and is dragging acceptance down. Use the touch 1 template in the playbook.

1. Split the volume across accounts. Two accounts at 15/day each beats one account at 30/day on every dimension. If you only have one account today, see the single-account fix sheet for the trade-offs of running a pool.

What "fixed" looks like

Acceptance climbs from <15% back to the 25-35% healthy band within 2-3 weeks. The 20-25/day volume ceiling can then be safely held indefinitely — accounts in that band can run for 6-12 months without a restriction.

How BIGM solves it

We run aged-account pools and split the same total daily volume across 4-6 warmed accounts. Each one stays well under the 20/day ceiling, the pool aggregate matches what you would otherwise send from one account, and ban risk drops to near zero because no single account is bearing visible volume.