What size of B2B sales team is this configuration designed for?

Founder-led teams of 4–25 people, typically Series A or B. With fewer than 4 reps the coordination overhead isn't worth automating (a shared Notion doc works). Above 25, you're past founder-led — the configuration shifts toward our GTM-org playbook.

How long does GTM Brigade take to deploy for a founder-led team?

14 days. Days 1–7 cover watchlist build, founder voice-model setup, and Slack routing setup. Days 8–14 are rep onboarding and the first wave of coordinated engagement on watchlist posts. Most teams have inbound landing in reps' Slack DMs by week 3.

Does the founder have to change how they post on LinkedIn?

No. The configuration is built around what the founder already does. We amplify the founder's existing rhythm — we don't ask them to post more, post differently, or hand their account to anyone. The change is in how the rest of the team operates around the founder's posts.

Can reps comment on LinkedIn in the founder's voice without it sounding fake?

Yes, if it's set up right. After the supervised voice-model setup (the user edits the first 20–40 AI suggestions so the model learns their cadence), the AI model drafts comments that match the founder's cadence and opinions. Reps review and adjust before sending — the suggestion is a starting point, not a final draft. The founder reviews the first batch (about a week of output) and either approves the tone or refines it.

What kind of pipeline can a founder-led team realistically expect from LinkedIn?

Highly variable — depends on the founder's existing reach. For founders with 10–40k followers running this motion, 15–30% of new pipeline typically becomes LinkedIn-attributable by day 90. We don't promise specific numbers because the variance is real, but the directional lift is consistent across teams we've onboarded.

For founder-led sales teams (under 25 people)

The problem you're trying to solve

The founder's LinkedIn is your most efficient channel and your biggest single point of failure. Your CEO has a LinkedIn following. Maybe 8k, maybe 40k, maybe 200k. The posts that land — usually one out of every five — produce more inbound than a quarter of paid acquisition. You know this is your most efficient channel. You also know the CEO can't be the only one running it.

Here's what usually happens: the founder posts on Mondays and Thursdays. A handful of replies trickle in. Two are obvious time-wasters, one is a competitor, and one is actually a Series B fintech CRO who'd be a perfect customer. By the time the founder sees it on Friday morning, the thread has moved on, the moment is dead, and the lead was never logged anywhere.

Meanwhile, your eight-person GTM team is doing something on LinkedIn — they're "active" — but no one can tell you what. There's no system. The founder is the brand and the team is supposed to be the brigade, but right now they're just eight people posting independently into their own feeds — exactly the gap the for-founder-led-teams-under-25-people playbook is built to close.

What GTM Brigade configures on day one

For a founder-led team of 4–25 people, the day-one configuration is a 120-profile watchlist, a captured founder voice, and Slack signal routing. We're not asking the founder to change how they post. We're asking the rest of the team to operate as the founder's distribution layer.

The watchlist

We build a 120-profile watchlist together. It's not arbitrary — it's mapped to your ICP and your live pipeline. Roughly:

60 buyers — people who could become customers in the next 4 quarters
30 amplifiers — adjacent voices (advisors, investors, peer founders) whose engagement signals trust to your buyers
30 deal-stage targets — people inside accounts you're already in conversation with

The watchlist lives in every rep's product surface. They see exactly whose posts to engage with, in priority order, every morning.

The founder's voice, captured

We do the first week of supervised drafting with the founder and feed it into the Brigade voice model. From that point on, when a rep wants to draft a comment on a watchlist post, they get suggestions written in the founder's voice — same cadence, same opinions, same vocabulary. The founder reviews the first batch, approves the tone, and then the team can ship without checking with them every time.

This solves the thing that kills most founder-led sales motions: the bottleneck where every customer-facing word has to pass through the CEO.

Signal routing

When a watchlist person posts, comments on the founder's post, or DMs anyone on the team, the signal hits Slack in near real time — with HubSpot context surfaced through our LinkedIn-to-HubSpot sync — and includes:

Who posted (author name)
The post itself (snippet + canonical LinkedIn URL)
The total engagement on it so far
A suggested reply drafted in the founder's voice

When the rep opens the post in the engagement view, HubSpot context (the matched contact, deal stage, deal owner) is visible there — it isn't pushed into the Slack message itself. The first rep available picks it up. The founder doesn't have to.

What the first 90 days look like

By day 14 the watchlist is live, by day 45 the team is operating as a coordinated unit, and by day 90 your tenant reports show a measurable LinkedIn-attributable pipeline lane.

"We went from 'the CEO is doing LinkedIn things' to 'we have a four-person LinkedIn motion' in about six weeks. Inbound from LinkedIn doubled by month three." — Head of Growth, Series A fintech (anonymous)

The shape is consistent across the founder-led teams we've onboarded:

Days 1–14: Watchlist build, voice-model setup, Slack routing wired. Reps start commenting on watchlist posts daily.
Days 15–45: Reps' comment volume on ICP posts goes up 4–6×. Founder's post engagement also rises because the team is finally showing up in the same threads.
Days 45–90: Inbound DMs to the team (not just the founder) become a meaningful pipeline source. your tenant reports show "LinkedIn-sourced" as its own attribution lane.

We don't promise specific numbers because founder-led pipeline depends heavily on who the founder is. We do guarantee that by day 90, the team will be operating as a coordinated unit on LinkedIn — and the founder will be spending less time on it, not more.

What this is not a fit for

Skip GTM Brigade if the founder isn't on LinkedIn, your team has fewer than 4 reps, or you expect LinkedIn to replace outbound entirely. A few honest disqualifiers:

The founder isn't on LinkedIn. If the CEO has 600 connections and posts once a quarter, there's nothing to amplify. Build the channel first, then come back.
The team doesn't have at least 4 people. With fewer reps, the coordination overhead isn't worth automating. A founder-led team of 2–3 can run this manually with a shared Notion doc.
You're hoping LinkedIn replaces outbound. It doesn't. It's the highest-leverage complement to outbound — a place where reps build trust before SDRs ever hit send. The warm-first outbound playbook covers exactly how the two layers stack. Teams that try to use it as a standalone channel get disappointed.

How to know if this is the right play for you

A 30-minute walkthrough with one of our strategists is the fastest qualification path. We'll look at the founder's last 10 posts, sketch what the watchlist would actually contain, and tell you within the meeting whether GTM Brigade is the right tool — or whether you should keep doing what you're doing for another quarter.