CampaignStack Reviews and Details

Questions & Answers

1. Which are the primary technologies used for building CampaignStack?

   CampaignStack runs on a TypeScript stack end to end.

   • Frontend: React with TanStack Router, built with Vite, styled with Tailwind
   • Backend: Convex, handling queries, mutations, scheduled jobs, and the real-time subscriptions behind the dashboard and the inbox
   • Outreach execution: a separate Node.js service driving real Chrome browser sessions, each pinned to its own residential proxy
   • AI layer: an MCP server exposing 90+ tools, so Claude and other agents can drive campaigns, leads, workflows, and the inbox
   • Plus a Chrome extension, Stripe for billing, and Playwright and Vitest for the test suites

2. Why should a person choose CampaignStack over its competitors?

   CampaignStack protects the one asset in outbound that cannot be replaced: the client's LinkedIn account. Once it is restricted, no amount of spend brings it back.

   Against tools like Expandi, Dripify, Waalaxy, HeyReach, Skylead, and Dux-Soup, which compete mainly on volume and speed:

   • Daily caps are enforced and visible, set at 80% of LinkedIn's tolerance rather than left to the operator to guess
   • Each account runs on its own residential IP, not a shared pool
   • Nothing leaves an account until it passes a review gate, and auto-send is off by default
   • $99 per workspace per month with unlimited connected accounts, so adding clients does not mean buying seats

   Everything else is still there: campaign orchestration, ICP scoring, buying signals, A/B testing, and one shared inbox across every account and client.

3. What makes CampaignStack unique?

   CampaignStack is a LinkedIn and email outreach platform built around one rule: show the sending limit, and refuse to cross it.

   • Every connected account gets a hard daily budget per action type, capped at 80% of what LinkedIn tolerates
   • New accounts ramp up over weeks instead of running at full volume on day one
   • One dedicated residential proxy per account, never a shared IP pool
   • A persistent browser fingerprint, so the account looks like the same person signing in from the same place each day
   • AI drafts every message, a human approves it in a review queue, and auto-send stays off until you turn it on

   Most tools in this category bury their limits in a settings page. CampaignStack puts the number on the dashboard.

4. How would you describe the primary audience of CampaignStack?

   CampaignStack is built for B2B lead generation agencies running outbound for several clients at once, sized for 5 to 20 client workspaces, where one restricted profile means a lost retainer.

   It also fits:

   • Founders doing their own outbound with no BDR team
   • Sales operators running a group of reps from one dashboard
   • Consultants delivering demand for several clients while working like it is one

   All of them share one constraint: they need volume, and they cannot afford to lose an account getting it.

5. What's the story behind CampaignStack?

   CampaignStack is built by a small team that spent years inside the LinkedIn automation industry, watching client accounts get restricted by tools that sent too much too fast. The pattern was always the same: the tool advertises volume, the agency turns it up, and a few weeks later a client's account is limited and the retainer is gone. Nothing on the market showed you the line you were about to cross. So we built the platform we wanted to use, one that treats a connected account as something you cannot get back.