01·Introduction: signals over static lists
Fewer tools on the UI, more demand for reliable automation underneath.
Last updated: 4/14/2026
A decade ago, many of us expected revenue stacks to get ever more bespoke—endless Zapier branches, custom objects for every edge case, and operators who doubled as part-time software engineers. Some teams still look like that. But the median moved the other way: reps asked for fewer tabs, and executives asked for clearer utilization of what they already pay for.
Since roughly 2020, a few patterns show up in almost every stack review. First, complexity landed hardest on individual sellers, who simply want to sell. Second, budgets did not disappear—but buyers consolidated spend into suites that promise “good enough” list, sequence, and enrichment in one place. Third, outbound noise exploded, which made intent-style signals more attractive: a defensible reason to interrupt someone is that their behavior changed, not that they appear on a purchased list.
All-in-one platforms still need pipes: identities, LinkedIn-shaped data, messaging surfaces, and guardrails. Someone has to maintain those integrations as products change. Edges focuses on that layer—typed LinkedIn Actions, predictable auth, and patterns you can embed in SaaS or internal tools—while your product team owns the UX.
Regardless of UI fashion, B2B teams remain anchored on LinkedIn for discovery, social proof, and direct outreach. That makes LinkedIn API automation a durable building block: not a side quest, but infrastructure for how revenue actually coordinates today.
AI agents add another twist: smaller surface UIs with more autonomous loops behind them. The winners will still need governed access to fresh identity and engagement primitives—not screenshots in a chat window.
Next we walk through how SalesTech evolved from spray-and-pray to intent-aware motions—and where LinkedIn shows up in each intent category.