Sidle runs automated outreach sequences on your Instagram account, at a pace the account survives. Both halves of that sentence took a year to get right.
Built and run every day by a B2B ads agency on its own pipeline, on the same infrastructure beta users get.
A CEO's email runs through a gatekeeper and a spam filter. Their LinkedIn is handled by a team. Their Instagram messages are read by exactly one person, and that person is the buyer.
Nobody triages an Instagram inbox on a founder's behalf. What you send is what they see, in their own hands.
This is another surface where the same buyer meets your name, alongside the email and the ad and the connection request. Being present in more than one place is what makes any of them work.
A short, specific message from a real profile reads like a person, not a sequence. The channel does part of the work for you.
Everyone who tries Instagram outreach meets the same wall. Sidle exists because the answer is not to pick a side of it.
Real conversations, and it works. It also eats an hour a day to reach a handful of people, so it never becomes a channel.
Volume arrives, and so does the restriction. Bursts, odd hours, and a mismatched device are what Instagram is actually looking for.
Sequences run unattended, but every action is spaced through your own hours on limits you set, from one browser and one connection that never change. The safety is not a setting you remember to turn on. It is how the thing is built.
You log in through Sidle's own browser, so the session is born on the machine that uses it. Every action and every read travels through your dedicated proxy, never the server's address.
Daily caps per action, a minimum gap between them, and a sending window in your timezone. Background checks run on an irregular rhythm rather than a machine's clock.
Checkpoints, restrictions, and failed sends pause the account and notify you rather than pushing on. Follow-ups hold when reply data is stale, so nobody gets nudged after they have answered.
Every account runs a separate instance with its own database and subdomain. Your leads, conversations, and session never sit beside anyone else's.
Push contacts from Clay, n8n, Claude Code, or anything that can post JSON. Sidle holds back anyone missing the fields your copy needs, so nothing goes out half written.
Send a handle, a first name, and a company, and the lead enters the sequence on its own. Enrichment stays wherever you already do it.
Every event goes back out the same way, so replies and status can land in your CRM or Slack.
The account follows the prospect and waits like a person would.
Long enough to look considered, short enough to stay relevant.
Like two recent posts, then message. The DM lands in their primary inbox.
Message anyway. The first line has to earn the open from the preview.
Any reply halts the sequence immediately and hands you the conversation.
Outreach is only part of it. The account itself has to look like somebody, which means it needs to be built, warmed, and kept alive.
Set up a dedicated outreach profile rather than risking a personal one. We walk you through the identity, the bio, and the first weeks of activity.
Publish photos and video to the account from the dashboard, on a schedule. A profile with real content reads as a person and gets replies.
Story views, likes, comments, and follows run alongside the messaging, paced under the same limits. The account behaves like an account, not a sender.
Conversations arrive in a shared inbox with labels and filters, and a Slack ping the moment anyone answers. You write every reply yourself.
Funnel by step, reply rates by campaign, and whether they followed back before you messaged. Enough to tell which opener is carrying the channel.
Keys, webhooks, and endpoints for contacts, campaigns, and conversations. Anything the dashboard does, your stack can do too.
A dedicated outreach profile, a mobile proxy in your metro, and content on the page. We do this part with you on a call, because it is the part that decides everything after it.
Post, browse, like, and follow while the account settles. Sidle handles the activity and the schedule. Nothing goes out to a prospect during this stage.
Push contacts from Clay or n8n, write the opener and the follow ups, then set the daily limits you want to start at.
Sequences run themselves and stop the moment somebody responds. Your part is the conversation, which is the part that was always yours.
It is a small group, and the work goes better when the fit is honest on both sides.
No, and we would talk you out of it. Beta users run a dedicated outreach account built for the purpose, which is what we do ourselves. Setting it up and warming it is part of onboarding, and it means your own profile is never exposed to the experiment.
It is the real risk, and pretending otherwise would be dishonest. Instagram limits automated behavior, and the triggers are volume, bursts, odd hours, and a device that does not match the session. Sidle is built against all four, and it stops the moment Instagram signals anything. We ramp slowly with you during the beta, starting from a warmed account rather than a new one.
Yes. Push contacts from Clay, n8n, Claude Code, Zapier, or a plain webhook, and they enter the sequence automatically. Each lead needs a handle plus whatever your copy references, usually a first name and company. Anything missing is held back rather than sent blank. Events flow back out through webhooks so your CRM stays current.
This is the real bottleneck, and it is solvable. We share the Claygent prompts we use to resolve handles from a name, company, and email, along with the enrichment flow around them. Match rates vary by market, which is part of what the beta is measuring.
Fewer than you would like, and that is the point. A healthy account sits in the range of ten a day once warmed, ramped up to gradually. The channel earns its place on reply rate rather than volume, so it belongs next to your existing outbound rather than replacing it.
Your own instance on your own subdomain, account setup and warming done with you, the Claygent prompts for handle discovery, and direct access while you run your first campaigns. It is paid and deliberately small, so the feedback shapes what gets built next. Pricing is discussed on the call once we know your setup.
A few details help us tell quickly whether this channel fits what you sell. If it does, we set up the account and your instance together on a call.
Places are limited while provisioning is done by hand.