A first sales hire with no pipeline does not need a list of leads from the founder. In week 1 they need a working outbound campaign, built from what the founder knows and operated by the hire: the founder gives three hours to name the audience, choose the offer and write the reply rules, a LinkedIn campaign goes live on the hire’s own account by Thursday, and from Friday the hire answers each reply that arrives with a playbook. The founder’s weekly cost after that is one 20 minute review.
Callum founded a company that makes scheduling software for veterinary groups. He sold the first 30 customers himself, mostly to people he met at two conferences. Six weeks ago he hired Priyanka, an account executive with five years of experience. On Monday she asked him, politely, which accounts she should work. He had no answer, and three customer calls that afternoon.
The plan runs through the GTM Bud connector in Priyanka’s own Claude or ChatGPT.
Why is the pipeline empty six weeks after the hire?
It is empty because the founder’s pipeline was never a system. It was a person: his contacts, his conference conversations, his memory of who said “call me in spring”.
Each side made an assumption.
- The founder assumed an experienced AE would bring a way to find leads.
- The hire assumed a company with 30 customers had a way to produce them.
Both were reasonable. Both were wrong. Now the hire knows the product well and has spent six weeks on a deck, a CRM cleanup and four calls with old contacts of the founder that went nowhere.
More time is not the fix, since the founder has none. A transfer of knowledge into something that runs without him is.
Who does what?
The founder supplies knowledge, once. The hire operates, every day. Write the split down on day 1 so that nobody waits for the other.
| Job | Founder | New hire |
|---|---|---|
| Say who buys and why | 1 hour, Monday | Asks the questions, types the answers |
| Judge previewed prospects | Marks the first preview | Marks each later preview |
| Choose the offer | Decides | Proposes, with the AI |
| Write the messages | Reads once, cuts what is untrue | Works with the AI until checks pass |
| Reply rules | 1 hour, Thursday | Writes them down, owns the playbook |
| Daily replies and calls | None | All of it |
| Weekly review | 20 minutes, Friday | Prepares and leads it |
One practical point shapes the whole plan. The setup here is one GTM Bud account with one sign-in. The hire signs in and works in it. The founder looks at the hire’s screen on Friday. There is no second login for the founder in this setup, and for this job none is needed.
Monday: get the founder’s knowledge out in one hour
Book one hour and treat it as an interview. The hire asks, the founder answers, and the AI turns the answers into a draft while they talk.
Five questions cover it:
- Which five customers would you most like to have again, and what do they have in common?
- Who signed, by job title, and who tried to block it?
- What was happening at the customer in the month before they bought?
- Which customers were a mistake, and how could we have known?
- What do you say in the first two minutes of a call that makes people lean in?
Callum’s answers gave this sentence, which Priyanka typed:
- “Create a campaign draft named Vet groups UK. The audience is operations directors and practice group managers at veterinary groups with 5 to 60 clinics in the United Kingdom and Ireland.”
Her AI wrote the targeting criteria from it. GTM Bud checked each one and saved the draft. Callum’s answer to question 3 was “they had just bought two or three practices”. Priyanka added that as a criterion. The check did not flag it, as an acquisition is the kind of thing a company page or public web content can show. His answer to question 4, “groups whose owner hates software”, was flagged with a suggested rewrite, since no profile states that.
Then the preview, which takes one to three minutes. Callum marked each person in the preview himself, out loud. “Good fit, she ran rotas at a hospital group before.” “Not a fit, that is a single referral hospital, not a group.” Priyanka typed each Not a fit reason into the mark and kept all of them in her notes. Those reasons are the most useful onboarding she has had in six weeks.
Tuesday and Wednesday: the hire builds the campaign
The hire does this part alone, and that is the point. Building the campaign is how she learns the pitch.
The seller profile. For this draft she sets the company website and her own personal LinkedIn profile URL, not the founder’s. The messages will come from her account, and the lead should find the same person on the call. GTM Bud reads the website and the profile. If her LinkedIn profile still describes her last job, Tuesday morning is the time to rewrite it.
The offer. Her AI gets the value offer brief and proposes offers from the website, the audience and the notes from Monday’s interview, which she pasted in. She brings three to Callum on a five minute call. He picks one and corrects one: “A rota gap report for one clinic, from four weeks of your current schedule. Not a ‘free audit’, we do not audit anything.”
The messages. Her AI gets the sequence brief and writes the messages, and GTM Bud checks them. When a check fails, the result names each problem, and she works through them with the AI until the sequence saves. Then she sends the saved text to Callum with one request: “Strike any sentence that is not true.” He removes a claim about integration with a practice system that is still in beta.
Her LinkedIn account. She connects it on gtmbud.com and sets a sending schedule there. The connection opens a sign-in window where she signs in to her own LinkedIn.
Thursday: launch, and write the playbook before the first reply
Launch in the morning. Write the playbook in the afternoon, with the founder, for one hour.
For the launch she asks her AI for the readiness check, and it reports each item as met or not met. Then she asks for the launch. Her AI shows a preview with the first message of each channel, and GTM Bud launches after she confirms.
The playbook is the more important hour. A reply playbook is the set of standing rules that the AI follows when it writes an answer to a lead. For a new hire it does a second job: it is the founder’s answer to every hard question, written down once.
Priyanka asked Callum how he answers the eight things leads say most. Six made it into the playbook:
- Price. Give no figure in a message. Say that it depends on the number of clinics, and offer the call.
- “We use a spreadsheet.” Do not attack it. Ask how they cover a vet who calls in sick.
- “Send me something.” Offer the rota gap report, and ask for four weeks of schedule.
- Integration. Name only the two practice systems that are live. For any other, say that she will check and answer on the call.
- The call. 25 minutes with Priyanka. Her slots are Monday, Wednesday and Friday from 10:00 to 12:00.
- A lead who knows Callum. Say so to Callum the same day. He writes to them himself.
Her AI showed the exact text and saved it after she approved it in the chat. Each later save keeps the earlier version, so Callum can see how the rules changed as she learned.
Trade-off: A playbook written by the founder makes the hire sound like the founder in week 1. That is right for week 1. By week 6 the hire should be changing rules from what leads tell her, and the founder should let her.
Friday onward: the hire’s day, and the founder’s 20 minutes
From Friday, the hire’s outbound day is one request and the calls that follow from it.
- “List the replies that need an answer in Vet groups UK. Write an answer for each one from the playbook and show them to me one at a time.”
Her AI writes each reply and shows it. She reads, edits and approves, and GTM Bud instructs the AI to send only the exact text she approved. That is an instruction to the AI and no more than that, so the reading is her job. By default, up to 40 replies a day can go out from one LinkedIn account, from the chat and the GTM Bud Inbox together.
Her first real one. An operations director wrote: “We just took on three practices in Kent and the rotas are chaos. How long does setup take?” The playbook had no setup time in it, so the AI did not state one. It wrote:
“Three new practices at once is when rotas break. I do not want to guess a setup time without seeing how Kent is scheduled today. Could we take 25 minutes on Wednesday or Friday between 10:00 and 12:00?”
She approved it, labeled the reply Interested, and added the setup range to the playbook after asking Callum.
The founder’s 20 minutes. Friday at 16:00, on her screen:
- Results for the campaign: requests sent and accepted, replies by label.
- Two conversations she found hard, read aloud.
- One rule to add or change in the playbook.
He gives judgment. She keeps the keyboard.
What the plan will not do for either of you
It will not tell the founder whether the hire is good at closing. It gives her conversations to close, which is the first time that question can be answered. It will not fill the CRM: the connector has no CRM integration, so she logs each new contact herself. It will not exclude your 30 existing customers by itself. She removes a customer from the campaign when she sees the name, and after Monday’s interview she knows them. The stronger step is outside the chat: the account page on gtmbud.com has an Excluded companies list, and GTM Bud contacts nobody at a company on it. And it will not promise a number of meetings in month 1. That depends on the audience and the offer.
If the hire you are planning is an SDR and not an AE, read when to hire your first SDR before you post the role. For the stage before any hire, see our guide to founder-led sales. And for the reply routine in more depth, see how to handle cold outreach replies.
Frequently asked questions about a first sales hire with no pipeline
Why does a first sales hire so often start with an empty pipeline?
Because the founder sold through a personal network, and a network cannot be handed over. The hire arrives expecting leads, the founder expects the hire to find them, and neither has said so. Six weeks in, the hire has learned the product and has nobody to tell about it.
Should the campaign send from the founder LinkedIn account or from the new hire account?
From the new hire account, with the seller profile of the campaign set to the hire personal LinkedIn profile. Leads then talk to the person who will take the call. Use the founder account for a second campaign later, aimed at senior buyers who expect to hear from a founder.
How much founder time does this plan need?
About three hours in the first week: one hour for the audience and the preview, one for the offer and the messages, and one to write the reply playbook with the hire. After that, 20 minutes on Friday to read the results together. The founder does no list building and sends no messages.
Whose GTM Bud account should it be?
One account, and the new hire signs in to it and works in it each day. The founder joins the Friday review on the same screen. This setup has one sign-in and no second login for the founder, so agree from day 1 who operates it. It should be the person whose job is sales.
What if the new hire still has no conversations after a month?
Then look at the evidence before you judge the person. Check how many requests were accepted and what the replies said. A campaign that reaches the wrong people is a targeting fault, and one that gets no acceptance is an audience or profile fault, because the connection request carries no note. Neither tells you anything yet about how the hire sells.
Give the hire a campaign, not a list
A first sales hire with no pipeline is a knowledge problem, and three founder hours solve it: an interview on Monday, a reading of the messages midweek, and a playbook on Thursday. The hire builds the campaign, launches it on her own LinkedIn account, and answers replies as they arrive. Have the hire add the connector with the steps on GTM Bud for Claude and create the GTM Bud account in the sign-in window, then book Monday’s hour.