# How to respond when a prospect says they'll pitch you internally
> Stop deals from stalling when a prospect says they'll mention you to their boss. Learn how to provide a champion kit that does the selling for them.
- HTML: https://getkinlead.com/reply-to-prospect-mentioning-internal-champion
- Markdown: https://getkinlead.com/reply-to-prospect-mentioning-internal-champion.md

**Short answer:** When a prospect says they'll pitch you internally, the deal usually stalls because they have to explain your value from memory between other meetings. Give them four paste-ready lines (the problem, what you do, one piece of proof, one ask) and a follow-up schedule that matches their calendar. Then the person holding the budget reads your words instead of a summary of a summary.

## Why 'I'll mention you' stalls the deal

A prospect saying they'll raise your service with their boss sounds like progress. It usually isn't. You've handed the sale to someone who is busy with their own job, doesn't sell for a living, and gets one attempt at describing what you do to the person holding the budget.

The failure is rarely bad intent. The prospect gets pulled into a fire drill, the weekly one to one moves, and by the time your name comes up they remember the price and half of the problem you solve. The boss hears about a tool and files it under later.

What you control is what the prospect has in their hands when the topic comes up. A two-line summary they can paste into Slack keeps you in the room. Rebuilding your pitch from memory does not.

There's a second failure mode. Sometimes the prospect isn't a champion at all. They're being polite, or they need a way to end the call without saying no. A champion kit flushes that out quickly: someone who won't forward four sentences was never going to defend your price in a budget meeting.

**Sending them off to sell it alone**

- You: 'Great, let me know how it goes with your boss.'
- You: wait four days, then send 'just checking in'.
- You: attach a twelve-slide deck as a PDF.
- What the boss sees: a colleague's vague summary and a file nobody opened.

**Handing them something they can paste**

- You: 'Before you raise it, here's a summary you can paste into an email or Slack.'
- You: wait three business days, then ask whether the boss had questions.
- You: keep the summary to four sentences and no attachment.
- What the boss sees: a clear problem, a clear ask, and a colleague who sounds organised.

## Build the champion kit before the call ends

A champion kit is text, not a deck. Nobody opens an attachment from a colleague they half know, and decision makers read Slack on a phone. Build something that survives being forwarded twice and still makes sense on its own.

Four blocks: the problem, what you do, proof, the ask. Write each one the way a non-salesperson would say it out loud to their manager. If a line needs a second line to make sense, cut it.

Copy the examples below, then replace every specific with something from your own conversation. The prospect should recognise their own words in the problem line. A generic kit gets generic treatment, which usually means no reply.

If you don't have a case study yet, name the closest thing you do have: a company of a similar size, a pilot, a reference who will take a call. The boss wants to know someone like them already took the risk.

| | Element | What it does | Example you can copy |
| --- | --- | --- | --- |
| The problem | One sentence in the prospect's own words about the pain. | We lose leads because nobody calls them until the next day. |
| What you do | One sentence, no category jargon. | Acme scores incoming leads automatically so the warm ones get called within the hour. |
| Proof | A similar company, a name the boss might know, or one link. | Northwind, an agency about our size, uses it for the same problem. One-page summary here. |
| The ask | One small next step with a date attached. | Can you do 15 minutes on Thursday with me and Marcus? |

## Write the forwardable message for them

Send two things in one reply: a short note to the prospect, then the block they can paste. Keep them separate so the prospect doesn't have to delete your pleasantries before forwarding it to a VP.

Ask them to change anything that isn't how they'd say it. A summary in their voice lands better than one in yours, and the edit takes them thirty seconds.

Match the length to the channel. Slack takes three lines and no greeting. Email takes a subject line that names the problem, because the boss will search for it again next week.

If the champion wants to add their own numbers, let them. Their budget figure carries more weight than yours, and it's the one the boss will check.

- **you:** Before you take this to Dana, I put the summary below together so you don't have to write it from scratch. Change anything that doesn't sound like you.
- **draft:** Hi Dana, I've been talking to Marcus at Acme about the gap between a lead coming in and someone calling them. Acme scores leads automatically so the warm ones get called the same day. Worth 15 minutes on Thursday with the two of us?
- **them:** That's close to how I'd say it. I'd drop the two-page mention, it's one screen. Sending it to Dana now.
- **you:** Perfect. If she asks about setup time, the second line answers it. Forward that part as is.

## Set a follow-up clock that matches their calendar

The kit is out and the clock is running. Internal pitches move on the company's calendar: a Monday standup, a Thursday one to one, a monthly budget review. Plan follow-ups around that schedule instead of expecting a same-day answer.

Skip 'just checking in'. Ask something the prospect can answer in one line and give them a reason to reply that isn't guilt.

Send the kit to the prospect, not the boss. Going around them, even with good intentions, turns your champion into a spectator and gives the boss a reason to route the decision back to procurement.

1. **Same day.** Send the kit while the conversation is fresh. If they mentioned the boss on a call, send it within the hour, before their next meeting starts.
2. **Three business days.** Wait until the next weekly one to one has probably happened. Three business days covers a weekend and a Monday standup.
3. **One-line check-in.** 'Did Dana get a chance to look at the summary, or is it sitting in a queue?' This is answerable in five words and doesn't demand an update that doesn't exist.
4. **New information.** If there's still nothing, bring something new: a short note about how a similar company handled the same problem. New information gives the champion a reason to reopen the thread.

> The deal isn't real until the person with the budget has read something you wrote. Everything before that is a friendly conversation.

## When the boss replies with questions

Most internal pitches come back as a question relayed secondhand: 'My manager wants to know how this compares to what we already run' or 'She asked how long setup takes.' Answer it so the champion can forward your answer into the same thread.

Answer the question that was asked, then add one line of context the boss needs. Don't attach a deck, don't ask for a meeting in the same message, and don't explain the product again from the top.

- Reply in the format the question arrived in: one short paragraph the champion can paste back.
- Name the alternative the boss is already thinking about and say where you differ in one line.
- Put price, setup time and contract terms in writing, because those are the lines that get re-read.
- Offer the smallest useful next step, usually 15 minutes with the boss and the champion on the same call.

> A question forwarded from a boss is the best signal you'll get. It means your summary was read by someone with authority.

## Doing this with Kinlead

Kinlead finds people on LinkedIn who match the customer you describe and scores each lead from 0 to 100 against that profile, so the conversations worth a champion kit start with buyers rather than browsers. Leads under the fit line aren't kept.

Set a campaign to hand the conversation to you at the first reply. When someone says they'll raise it internally, you write the summary, not an agent.

Replies from every campaign land in [one inbox classified by intent](/features/unified-inbox), with interested replies first, and you get an email when someone answers. Outreach sends from your own LinkedIn account at a human pace, inside the send window and daily limits you set, so your inbox isn't full of half-conversations.

## Related

- [How reply hand-off works](https://getkinlead.com/features/unified-inbox.md)
- [Find leads that match your buyer](https://getkinlead.com/features/lead-groups-and-scoring.md)
- [Book a demo](https://getkinlead.com/demo.md)

## Common questions

**What if the prospect won't send anything I wrote?**

Ask what they'd change, then let them write it their way. Send a short list of the four points to cover and leave it there. What comes back tells you how well they understood the problem.

**Should I ask to meet the boss directly?**

Only when the prospect offers it or has already forwarded something. Asking on the first mention looks like you're going around them, and it gives the boss a reason to hand the decision to procurement.

**How short should the pasted summary be?**

Short enough to read on a phone without scrolling. Four sentences usually covers it: the problem, what you do, one piece of proof, one ask with a date.

**How long do I wait before calling it dead?**

About two weeks after the kit goes over, if a direct question gets no answer, ask whether it's still alive on their side. Then leave the door open and move on to the next conversation.

**Does this work when the buyer is a committee?**

Yes, but send one summary per person with the part they care about first. Finance gets the cost line, the operator gets setup time, and your champion gets a version they can paste into the group thread.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
