Six SDRs, six ways to write a first message. Give the team one playbook you can read.

The short answer for an SDR manager

A LinkedIn outreach tool for SDR teams has to solve two things at once: every SDR writes differently, and the manager cannot see the difference until it costs a deal. GTM Bud, used through Claude or ChatGPT, fits a team of 3 to 8 SDRs if you accept one condition. The team works in one GTM Bud account that one person directs. In return you get one reply playbook in readable text, one base campaign cloned per segment, and a weekly review that is a question in a chat.

If the condition is wrong for your team, this is the wrong setup, and the section on limits below says why. This page is for a manager whose SDRs stay. If your SDR left and the reps must cover, read AI LinkedIn outreach for sales teams.

What a team can and cannot share

We checked the product for this page. Here is the plain list.

Shared in one GTM Bud account	Not available
Several LinkedIn sender accounts, one for each SDR	A separate login for each SDR
One account reply playbook, plus one playbook per campaign	Roles or permissions (who may launch, who may approve)
Campaigns that can be duplicated for each segment	A report per SDR through the connector
Results per campaign, with the time they were calculated	A sender name in the campaign list or the results
A check that keeps one person out of two campaigns	Reply routing to the SDR who owns the segment

The left column is what makes a shared approach possible. The right column is what you replace with a routine: who is signed in, who sits in the review, how campaigns are named. One thing exists outside the chat: on gtmbud.com, the overview of a campaign that has two or more LinkedIn senders shows a By sender table.

Do not solve the right column by handing the manager’s password to six people. Whoever is signed in can confirm a launch and approve a reply, and you would lose the one control this setup gives you.

The shared approach in four parts

1. One base campaign. Build it with your best SDR in the room. The sequence carries their wording. This is the moment their skill gets written down.

2. One copy per segment. Duplicate the base and change the audience. A team of six with six segments has six campaigns with the same messages and different buyers.

3. One playbook, two levels. Team rules go in the account playbook. Segment rules go in the campaign playbook. Your AI shows the exact new text and saves it only after you approve it in the chat, and each save keeps the earlier text in the version history.

4. One weekly review. Thursday at 3 pm, 30 minutes. One question to the AI, one table, one decision per segment: keep, change the audience, or end.

The Thursday review: a session

A session in Claude. The tool names are real, the team is invented, and result numbers are left out because they would be yours.

you    Thursday review. List the segment campaigns.
ai     list_campaigns
       6 campaigns named "Seg: ..." (5 active, 1 draft)

you    Results for each active one, in one table. Put the
       as-of time in the last column.
ai     get_campaign_results  (5 calls)
       Table returned: connection requests sent and accepted,
       replies, replies by label (Interested, Warm, Not
       interested), and the count that has no label yet.

you    "Seg: Healthcare IT / Maya" has unlabeled replies.
       Show them.
ai     list_replies
       7 replies. 4 have no label.
ai     get_conversation  (4 calls)
       Proposed labels: 2 Interested, 1 Warm, 1 Not interested.
you    Agreed.
ai     classify_reply  (4 calls)

you    The insurance segment got the same objection three
       times: "we are locked into a contract until renewal".
       Propose a rule for that campaign's playbook.
ai     get_reply_playbooks
       Proposed text shown. Waiting for your approval.
you    Approved.
ai     update_reply_playbook
       Saved. The earlier text is kept.

you    Clone the healthcare campaign for dental groups.
ai     duplicate_campaign
ai     update_campaign_targeting
       Draft created. All criteria passed the check.
ai     start_prospect_preview

A worked example: six segments, one base

The team in this example sells scheduling software and has six SDRs. Lena manages them. All names are invented.

The base campaign. Built on a Monday with Maya, the SDR whose replies get the most meetings by the team’s own count. Audience: “Practice managers and operations directors at multi-site healthcare groups with 100 to 1,000 employees in the United Kingdom.”

The segments. Healthcare groups, dental groups, veterinary groups, physiotherapy chains, care homes, private clinics. One SDR owns each.

The naming rule. “Seg: [segment] / [SDR first name]”. The campaign list and the results do not name the sender of a campaign, so the name carries it. After each duplicate, Lena sets the matching sender on gtmbud.com. The copy also keeps the seller profile of the base campaign, so she has her AI set the seller profile of each copy to the personal LinkedIn profile of the SDR who owns it.

The preview session. Each SDR sits with Lena for ten minutes and marks the previewed people for their own segment. For care homes, the first run showed mostly registered managers of single homes, far below the size range. The SDR marked them Not a fit, and Lena’s AI rewrote the audience to “group operations roles at care home operators with five or more sites”. GTM Bud flagged “five or more sites” as hard to read from a profile and suggested a headcount range in its place.

The team rule in the account playbook. “Never name a competitor. If the lead names one, ask what they would change about it.” Before this, three SDRs handled that question in three ways.

The review question. “Put the six segment campaigns in one table and sort by Interested replies. For the bottom two, show me three previewed people marked Not a fit, so we can see if the audience is the problem.”

Five prompts for an SDR manager

• “List every campaign whose name starts with Seg and tell me which ones are draft, active, paused or ended.”
• “Show me the account reply playbook and each campaign playbook side by side, and point out any rule in a campaign playbook that contradicts the account one.”
• “For the dental segment, list replies that need an answer and write each answer from the playbooks. We will read them together before I approve any.”
• “Duplicate the base campaign for veterinary groups in Ireland, keep every message, change only the audience, and stop after the prospect preview starts.”
• “Print the full message sequence of the base campaign so I can paste it into the team handbook.”

Three objections SDR managers raise

“My SDRs will feel replaced.” Some will, and a page cannot settle that. What changes is the task. Nobody on the team types first messages. Everybody on the team judges fit, reads buyers and improves the rules. Say that before the first session, and build the base campaign from an SDR’s wording, not from yours.

“One account that I direct makes me the bottleneck.” Yes. Each LinkedIn account can send up to 40 replies a day through the connector, and with six senders a busy day is a long review. Two things help: the labels (answer Interested first), and the shared session where each SDR pre-reads their segment. If your team needs six people approving at the same time from six logins, this setup does not provide it.

“Identical messages across segments will read as generic.” The copies start identical so that the first comparison is clean. After two reviews, change the value offer and the messages of the segments that are worth it. GTM Bud checks the new offers and messages before it saves them, and the connector changes the audience, the offers and the messages of a draft only, not of a live campaign. So plan each such change as a new copy.

What stays outside the chat

Each SDR’s LinkedIn account is connected on gtmbud.com, inside the one GTM Bud account. You do not need an SDR’s LinkedIn password for that. Once the account has one connected LinkedIn account, the account page shows a Share Connection Link button: you enter the SDR’s LinkedIn profile URL, send the SDR the link, and the SDR signs in to LinkedIn on their own computer. A link works once and expires after 7 days. The plan counts each connected LinkedIn account, and the page that the SDR opens can show the charge for the added account. On a paid plan, when the account adds to the charge, you confirm it while signed in before the SDR can continue. The sending accounts for a campaign and the sending schedule are set there too. The 14-day free trial starts when you launch your first campaign. Ask each SDR for their agreement before their account sends messages that they did not type.

Setup

One person adds the connector: see GTM Bud for Claude, or the GTM Bud connector page for every app and the full capability list. If RevOps owns your outbound rules, send them AI LinkedIn outreach for RevOps. For what to write in the team playbook, start from how to handle cold outreach replies.