Pilot program buy-in: use internal marketing to sell it inside first

This is part 3 of a five-part series on no-excuses customer experience, and the part about pilot program buy-in. Part 1 introduced the excuses and the seven rules, part 2 covered rules 3 to 5, and this part takes rule 6. Still to come are part 4 on measurement and part 5 on lifetime value.

The pilot is designed. It is modest and sensible: for three months, every support ticket that closes without a resolution note gets a call from a person within three days. You have the list, the script, a volunteer team and a rough idea of what you want to measure. You send the plan to the steering group and wait.

What comes back is not a no. It is worse. It is a series of small, reasonable questions from people who were not in the room when the idea was born. Compliance wants to know about call recording. The service lead wants to know who covers the volunteers’ queues. Finance asks how this fits with the retention tool that was bought last year. Somebody’s manager asks whether this is a marketing thing or a service thing. Three weeks later the pilot has been “sequenced after the platform migration”, which is the corporate word for buried.

Nothing about the pilot was wrong. It just went outside before it went inside. Pilot program buy-in is the active support of the people who could stop, starve or quietly ignore a pilot, secured before it launches, and it is the thing the plan never asked for.

Key takeaways

• A customer experience pilot almost always fails politically, by losing attention or a sponsor, before it ever gets the chance to fail statistically.
• Buy-in is different from approval: approval is a signature, buy-in is a person who will be asked how the pilot is going and wants a good answer.
• Internal marketing for a pilot is rule 3 pointed inward: treat colleagues as an audience with their own channel, timing and words.
• A one-page pitch, sent first to the people who could stop the pilot, turns a proposal into a plan that several people helped write.
• Customer verbatims are the one kind of evidence that arrives in a meeting with its own authority, and a pilot should collect them from day one.

What pilot program buy-in is (and what a signature is not)

Rule 6 of no-excuses customer experience is “Sell it inside before you sell it outside.” Of the seven rules it is the one people most often skip, because it does not feel like customer work. It feels like politics, and most people who care about customers got into this line of work to avoid politics.

1. Start with the customers you already have.
2. Act on what you already know.
3. Talk to customers like a person: their channel, their timing, their words.
4. Make coming back easy: remove friction at the moment of return.
5. Give the frontline a reason and a way.
6. Sell it inside before you sell it outside.
7. Measure it, or it did not happen.

Buy-in is not approval. Approval is a signature on a plan, and a signature is silent when the pilot runs into trouble in month two. Buy-in is a set of people who expect to be asked about the pilot and would rather have a good answer than a shrug. In a company of any size there are five of them, and they are rarely all in the steering group: the sponsor whose name goes on it, the manager whose team’s time it borrows, the owners of the adjacent systems and programs it touches, the person who controls the money, and the frontline people who will actually make the calls.

Miss any one of the five and the pilot has a hole in it that will be found. The compliance question, the queue question and the “is this marketing or service” question at the top of this post are what those holes sound like.

Why a pilot fails politically before it fails statistically

Look at how pilots actually die. Rarely from bad results. Usually they never produce results at all, because they lose attention, lose a sponsor, or lose a turf argument in month two. The statistics never get a chance to fail. The politics failed first. There is a whole post on why pilots stall from lack of organizational attention, and its short version is that enthusiasm at launch is not a structure.

The fix is to treat your colleagues the way you would treat a customer segment: as an audience with their own channel, their own timing and their own words. That is rule 3, pointed inward. The service lead reads the queue report, not the strategy deck. Finance thinks in the budget cycle, not the sprint. The frontline responds to a customer’s story, not a slide about strategic priorities.

Internal marketing for a pilot: five things the audience needs

A sponsor who will be asked about it. Not a name on a slide. Someone senior enough that when the pilot comes up in a meeting they are not in, the people in that meeting know the sponsor will hear about it. The test is simple: will anyone ask this person “how is your callback pilot going?” If nobody would, you do not have a sponsor yet, you have a signature.

A story that fits in a hallway. Two sentences, in plain words, that a colleague could repeat to another colleague at the coffee machine without your slides. Something like: “We are calling back everyone whose ticket got closed without a fix. Several of them had already given up on us and never said so.” If the story needs a diagram, it will not travel.

One small, visible win, early. Not the result. A result. In the first two weeks, find one customer who was about to leave and stayed, and tell that story, with permission, to the sponsor and to the team whose queue you borrowed. Momentum inside a company is made of specific people, not aggregate charts.

Objections named before others name them. Every objection you heard from the steering group could have been in your plan on page one. “This will overlap with the retention tool” is an easy question to answer if you answer it first and a suspicious one if someone else raises it. Write the objections down. Put the three strongest in the pitch, with your answer. You will look like someone who has thought about it, because you will have.

Customer verbatims as evidence. Numbers get argued with. A customer’s own words, read aloud, mostly do not. A line like “I raised it twice and nobody came back to me, so I assumed you did not want the business” cannot be dismissed by anyone in the room, because nobody in the room can say that customer is wrong. Verbatims are the one kind of evidence in a company that arrives with its own authority. A pilot should collect them from day one, not for the final report but for every conversation along the way.

How to write the one-page internal pitch

Keep it to one page, because anything longer will be summarized by someone else, and their summary will be worse than yours. This is the structure I use.

1. The customer problem, in a customer’s words. One verbatim, then one sentence on how often it happens.
2. What we will do. Two or three sentences. Who, for whom, for how long.
3. What we expect to change, for whom, compared with what. The three measurement questions from part 4, answered in advance.
4. What it costs. People, hours, any money. Be precise about small numbers; it builds trust for the large ones later.
5. What we will decide, and when. The date on which someone will say scale, stop or change, and who that someone is.
6. The three objections, answered.
7. The sponsor’s name. At the top, not the bottom.

Send it to the people who could stop the pilot before you send it to the people who could approve it. Ask each of them what is missing. Most of what they say will improve the plan, and the rest is the price of their name on the list of people consulted.

Then, when you finally put it in front of the steering group, it is no longer a proposal. It is a plan that six people already helped write, and people rarely bury what they helped build.

A worked example (illustrative)

The figures are round and invented, to show what a filled-in page looks like rather than to set a benchmark.

The problem: “I raised it twice and nobody came back to me.” About 400 tickets a quarter close without a resolution note. The plan: two service agents, three hours a week each, call every such customer within three days, for one quarter. The expected change: customers who are called keep buying at a higher rate over the following six months than a random one in ten who are not called. The cost: roughly 150 agent hours, no new spend, and one report a month from the analyst who already runs the service dashboard. The decision: at the end of the quarter, the head of service says scale, stop or change, with the comparison in front of her. The objections: overlap with the retention tool (it targets lapsed customers, this targets open wounds), queue coverage (agreed with the service lead, two hours a day moved to the afternoon shift) and call recording (existing consent covers service callbacks, confirmed with compliance). Sponsor: the head of service, named at the top.

Every line on that page is an answer to a question someone was going to ask anyway. The difference is who asked it first.

Approval vs buy-in: how to tell which one you have

The two are easy to confuse in the week after the steering group says yes. They behave very differently in month two.

	Approval	Buy-in
What it looks like	A signature, a line in the minutes	A name on the plan and a slot in someone’s calendar
Who gave it	A committee	Five specific people
When the queue gets busy	The volunteers are pulled back	The service lead defends the two hours a day
When a rival program appears	“Sequenced after the migration”	The sponsor asks which one has a customer verbatim
What it costs to get	One meeting	Six short conversations before the meeting
How to test it	Nobody can, until it fails	Ask whether anyone would ask the sponsor about it

If the answer to the last row is no, go back to the five conversations. It is cheaper than restarting the pilot next year under a new name.

What quietly kills pilot program buy-in

The pitch goes to approvers first. The steering group hears the idea before the queue owner does, and the queue owner learns about it from the minutes. Everything they say from then on is defensive, and reasonably so.

The story has jargon in it. “A closed-loop intervention on unresolved-ticket cohorts” cannot be repeated at a coffee machine. If the hallway version does not exist, the pilot exists only in your deck.

Success is announced before it exists. An early win is one specific customer, told with permission. A chart after two weeks is a promise, and promises that do not land poison the next pitch as well as this one.

Sales was never asked. In any company with an account team, a callback program touches their customers. Whether sales cares about your program is decided by whether they were consulted before it started, not by how good the results are.

When internal marketing is not the problem

Internal marketing is powerful and it is not a universal solvent.

When the pilot is a poor idea. Selling a weak plan well produces a well-supported failure. If the customer problem is not real, or the action does not plausibly touch it, no sponsor will save it. Check the verbatims before the pitch, not after.

When there is no measurement plan. Buy-in gets a pilot launched. Only a comparison, agreed in advance, gets it renewed. A pitch without item 3 filled in is asking people to support something that can never be shown to have worked.

When the company is mid-reorganization. Sponsors change jobs, budgets freeze and attention goes elsewhere. The right move is often to wait a quarter, or to shrink the pilot until it needs only one team and no money, rather than to sell harder.

Where to start

1. Name the five people who could stop the pilot. Sponsor, queue owner, adjacent program owners, budget holder, frontline lead. Real names, not roles.
2. Write the hallway version. Two sentences. Read it to someone outside the project and ask them to repeat it back.
3. Collect three customer verbatims from the last quarter that describe the problem the pilot addresses, in the customers’ own words.
4. Draft the one page with all seven items, including the decision date and the three objections.
5. Hold five short conversations with the people from step 1 before anything goes to a steering group. Ask each what is missing, and change the page.

FAQ

What is pilot program buy-in?

Pilot program buy-in is the active support of the people who could stop, starve or ignore a pilot, secured before it launches. It differs from approval, which is a signature on a plan. Buy-in shows itself when a sponsor expects to be asked about the pilot and a queue owner defends the time it takes.

How do you get an executive sponsor for a pilot program?

Choose someone senior enough that people in meetings they do not attend still expect them to hear about the pilot, and bring them a customer’s own words rather than a strategy slide. Put their name at the top of a one-page plan that already contains the decision date and the strongest objections answered. The test of a real sponsor is whether anyone would ask them how the pilot is going.

What should a one-page pilot proposal include?

The customer problem in a customer’s words, what will be done and for whom, what is expected to change compared with a defined group, what it costs, the date and owner of the scale-or-stop decision, the three strongest objections with answers, and the sponsor’s name. Keep it to one page so that nobody else has to summarize it. Send it to the people who could stop the pilot before the people who could approve it.

How do you handle objections to a customer experience pilot?

Write the objections down before anyone raises them and put the three strongest in the plan with an answer next to each. Common ones are overlap with an existing tool, who covers borrowed staff time, and compliance around customer contact. An objection answered first reads as diligence; the same objection raised by someone else reads as a gap.

Why do customer experience pilots fail?

Most fail before they produce a result, by losing a sponsor, losing attention or losing a turf argument in the second month. The remedy is structural: a named owner, a decision date on the calendar, a comparison group held out from the start and support from the people whose time and systems the pilot borrows. Results rarely get the chance to be the problem.