About
Built on Swarmhit.
Spun off for the teams who used it most.
Cadency is outreach software for teams that send volume on LinkedIn and email. It started as a playground for our own infrastructure, sales teams adopted it, and we made it a product of its own.
Where it comes from
Cadency is a product built on top of Swarmhit.
Swarmhit is outreach infrastructure: the LinkedIn and email engine, the sender safety layer, the proxies, the warm-up, the data, exposed through an API that other software is built on. Cadency began as our own playground for that infrastructure, an application we built to exercise the API end to end, the way a customer would.
It was never meant to be sold. It was meant to make sure the infrastructure held up when a real campaign, with real senders and real volume, ran through it every day.
What happened
Sales teams started using the playground.
Teams who came to us for the API asked to use the application instead. They did not want to build an outreach tool; they wanted to run several LinkedIn accounts and many mailboxes from one place, on infrastructure that did not fall over at volume. The playground was already doing that.
So we made a decision. Rather than keep it as an internal tool, we spun it off, gave it its own name, and offered it to the people who had been asking for it: sales teams that send volume, and the GTM agencies that run outbound for them.
Who builds it
Software engineers from lemlist and GTM operators.
The Cadency team is made of software engineers who previously built at lemlist, and of GTM practitioners who have run outbound for their own companies and for clients. We know the space from both sides: what breaks inside an outreach product at scale, and what a team actually needs from it on a Monday morning.
The product is the result of years of work in this space, not a weekend clone. Every ceiling, every pacing rule, every retry in the engine exists because something once went wrong without it.
The infrastructure
The same engine other tools are built on.
Cadency runs on the Swarmhit infrastructure that other outreach software already runs on through the API. That is the part we are proudest of and the part you never see: accounts that stay healthy, mailboxes that keep landing, volume that does not degrade the sender pool.
We are transparent about this on purpose. You should know what your outreach runs on, who operates it, and what happens when LinkedIn or a mailbox provider changes the rules. The answer is the same team, the same engine, the same day.
- Engine
- Swarmhit
- Channels
- LinkedIn and email
- Exposed as
- Cadency, and the API
How we work
Transparent by default.
Prices are published, including what happens at 50 senders and 2M emails a month. Our comparison pages say where the other tool is the better pick. If Cadency is the wrong fit for how you sell, we will tell you on the access call rather than after the first invoice.
Access opens in small batches because onboarding a team that sends volume is work we want to do properly: senders connected, ceilings set, mailboxes warmed.
Ready when you are.
We will tell you if it fits.
Tell us who you sell to and how many senders you have. If Cadency is the wrong tool for it, we will say so.
Request access