LinkedIn limits are unforgiving and the sequence tree branches in ways email does not. Both are easy to configure wrongly and expensive to correct afterwards.
The branching is the part that goes wrong
Email sequences are mostly linear. A LinkedIn sequence is a tree: what happens if the connection is accepted, what happens if it is not, what happens if they reply before the next step, whether a message goes to a non-connection at all.
Left at defaults these branches produce sequences that message people who never connected, or that keep sending after someone has already replied. Both are visible to the recipient and both look careless.
Seats are not interchangeable
Which account sends to which segment matters. A seat with an existing network in a region performs differently from a fresh one, and a seat already near its weekly limit should not be given the largest segment. The matching is explicit rather than even.
Not a lead builder, not a reply handler
It takes approved leads and builds the campaign. Sourcing them is upstream, and handling what comes back is downstream, both as separate skills.
Runs well with
Skills compound. These are the ones we usually install alongside it.