Customer advocacy from scratch: a 90-day plan and ready-to-use program framework

Table of Contents

• Define the goal first, then choose the advocates
• The three stages of the first 90 days of customer advocacy
• Days 1-30: foundation – why does the program exist and who should be part of it?
• Value for the customer: why should they say “yes”?
• Days 31-60: pilot – do customers actually want to engage?
• Days 61-90: system – can successful activities be repeated?
• A ready-to-use customer advocacy program framework
• What do you need to make the program work?
• A minimal customer advocacy program framework
• How should you measure the first 90 days?
• Customer advocacy from scratch – summary
• FAQ – frequently asked questions about customer advocacy
  • 1. What is customer advocacy?
  • 2. How should you select the first customers for a customer advocacy program?
  • 3. How many advocates do you need at the beginning?
  • 4. What activities can customer advocacy include?
  • 5. How should you measure the effectiveness of a customer advocacy program?

Customer advocacy is easy to confuse with simply collecting customer endorsements. A company secures a few case studies, a customer agrees to appear on a webinar, someone leaves a review, and Sales gets the contact details of a person willing to join a reference call.

At first glance, everything looks good. The problem is that “customers sometimes say good things about us” does not mean the company has a customer advocacy program. This is one of the biggest traps at the outset. Individual activations are necessary, but they do not create a system on their own. A program only begins when the company knows which customers it wants to engage, why those customers would want to participate, how to make that engagement regular, and how to use their voice without turning the relationship into a series of marketing requests.

The first 90 days should therefore focus not on maximizing the number of endorsements, but on building a foundation that will make it possible to generate them consistently later on.

The most common mistake when launching customer advocacy starts with a seemingly reasonable question:

Which customers can we invite to the program?

The problem is that this question comes too early. Before a company selects its first advocates, it needs to determine what it actually needs them for. Customer advocacy can support sales, generate customer references, build brand credibility, create case studies, strengthen a community, support events and product development, or increase the visibility of customer-side experts. Each of these objectives, however, requires a somewhat different program.

If the priority is sales, particularly valuable advocates will be customers willing to speak with prospects, describe the implementation, and help address concerns before a purchase. If the objective is building brand credibility, greater value may come from case studies, expert commentary, reviews, and speaking engagements. In turn, when the company wants to develop its product, a particularly valuable advocate may be a customer who has no interest in appearing publicly but regularly provides high-quality feedback and is happy to take part in closed sessions with the product team.

That is why a strong advocate base does not come from a list of the “most satisfied customers.” It comes from answering this question:

How will we know in 90 days that customer advocacy is genuinely starting to help the business?

Only then can the company make informed decisions about whom to invite, what to involve them in, and under what terms.

The simplest way to structure the launch is to divide the first three months into three stages:

Days 1-30: foundation

Days 31-60: pilot

Days 61-90: system

Each stage has a different purpose. In the first month, the company defines why the program exists and who it wants to build it with. In the second, it tests its assumptions with a small group of customers. In the third, it turns individual successful activities into a repeatable process.

Problems begin when an organization jumps straight to the second stage. Marketing needs a customer story, so it finds a customer. Sales needs a reference, so it contacts someone else. An event organizer needs a panelist and asks another person. Within a few weeks, plenty of activity is taking place, but no one is quite sure who owns the relationship, what customers prefer, or whether the same people are being asked to do everything.

The purpose of the first 90 days is to turn this chaos into a well-functioning system.

The first month should not begin with a mass invitation to customers. This is the time to design the foundations. First, the company needs to define the program’s primary objective, the process owner, and the criteria for selecting potential advocates. At this stage, it is worth preparing:

• one primary program objective;
• an ideal advocate profile;
• an initial list of potential participants;
• a catalog of possible activities;
• rules for contacting customers;
• a basic method for recording the history of each relationship.

The most important thing is to define a potential advocate properly. A high NPS or a positive Customer Success assessment can be a useful signal, but it is not enough. A satisfied customer will not always want to support the brand publicly. They may not have approval from their organization, may not feel comfortable on camera, may not have time for events, or may simply see no value in doing so.

Behavior reveals much more. A strong candidate may be someone who already recommends the product spontaneously, regularly provides feedback, actively participates in the community, comes back with ideas, shares implementation results, or proactively offers to introduce the company to other organizations. This still does not guarantee participation, but it shows something more important than declared satisfaction: a willingness to build a relationship that goes beyond simply using the product.

It is also worth assuming from the outset that there is no single type of advocate. One person may be excellent on a webinar. Another may be happy to speak with a prospect but unwilling to appear in a public case study. A third may leave a review and provide a quote. A fourth may become a highly engaged partner for the product team without ever appearing in marketing content.

That is why, during the first month, it is worth creating a simple customer profile that includes not only contact details but also the person’s areas of expertise, relationship history, preferred formats, constraints, previous activations, and the person responsible for the relationship.

The most important question at this stage is:

Do we know why this particular customer should become an advocate and how their participation can also create value for them?

If the answer is “because they are satisfied,” the program’s foundation is still too weak.

Customer advocacy becomes one-sided when the company thinks only about what it needs from the advocate. The conversation then becomes a constant refrain:

• We need a customer reference.
• We need a quote.
• We need a speaker.
• We need someone for a case study.

Each of these needs may be legitimate, but customers do not join an advocacy program to solve the vendor’s content problems.

That is why the value on the other side of the relationship needs to be defined within the first 30 days. It might be an opportunity to showcase the success of the customer’s own team, build an expert profile, speak to a valuable audience, connect with other customers, gain early insight into the product roadmap, or have a genuine influence on product development.

Value will look different for different people. An executive may want to showcase a transformation delivered by their team. An expert may care about greater visibility within the industry. A product user may value the opportunity to influence new features most of all. Someone else may simply enjoy sharing experience with people facing similar challenges.

Tip: a good program does not try to invent one reward for everyone. It looks for the point where the company’s interests and the customer’s interests align naturally.

The second month is when assumptions need to be tested against reality. Instead of opening the program to one hundred customers, it is better to start with a small group. A dozen or so people are enough to test the invitation process, different types of activations, information flow, and the most common barriers. During the pilot, it is worth tracking, among other things:

• how many customers accept the invitation;
• which forms of collaboration they choose;
• how long it takes to obtain approvals;
• which activations require the most work;
• what barriers arise on the customer side;
• whether participants want to engage again.

The last point is particularly important. A one-off agreement to appear on a webinar may result from a good relationship with the account manager or simply a willingness to help. A customer’s readiness to take part in another activity shows something more: that they genuinely see value in the relationship.

The pilot is also the right time to test several formats rather than just one. Customer advocacy can include a simple recommendation, a quote, a review, a reference call, a case study, a webinar, a customer roundtable, expert content, an event appearance, or a feedback session. These formats differ in the level of involvement they require, the amount of time they demand from the customer, and the approval process.

It is not worth starting every relationship with the most demanding format. A full case study may require an interview, data, several rounds of approval, and sign-off from the legal team. The same person, however, may be perfectly comfortable joining a closed conversation with another customer or providing a short expert comment. The program should be able to match the activation to the individual instead of expecting every advocate to do everything.

The second month is when the company should begin to see the first patterns. Customers may be very willing to join peer-to-peer conversations while avoiding public speaking. The challenge with case studies may not be a lack of willingness, but a legal approval process that takes several weeks. Or an invitation to an advocacy program may perform worse than a specific invitation to join a community of experts.

The pilot is intended to reveal these patterns before the program grows. That is why the most important question is:

Are we building a format customers want to return to, or are we simply getting better at persuading them to accept one-off requests?

These are two very different situations.

The third month begins when the company already has its first participants, several completed activations, and enough observations to stop relying solely on intuition. The most important task now is to organize the process.

Customer advocacy typically involves several teams. Marketing needs customer stories. Sales looks for references. Customer Success understands the relationship. Product wants feedback. PR may need expert commentary. An event manager needs speakers. Each of these teams has legitimate needs, but the customer sees one company.

If no one coordinates the whole process, the best advocate quickly becomes the default answer to every request. That is why, at this stage, it is worth establishing a simple workflow:

• a team submits a request;
• the program owner selects a potential advocate;
• the person responsible for the customer confirms whether the timing is appropriate;
• the customer receives a specific proposal, including the scope and expected time commitment;
• the activation is carried out and recorded;
• after it is completed, the customer is informed about the outcome.

This process does not need to be complex. It is more important that everyone follows the same one.

Consulting the relationship owner is particularly important. A customer may be an excellent advocate but currently be dealing with an implementation issue, negotiating renewal terms, or waiting for an escalation to be resolved. An automated request for a reference sent at such a moment shows that the program is disconnected from the customer’s reality.

Closing the loop after an activation is equally important. If a customer appeared on a webinar, it is worth sharing audience reactions and the most interesting questions. If a case study was created, the customer can be told where it is being used. If a reference call took place, it is good to explain that it helped a prospect make a decision. An advocate should not hear from the company only when another request appears.

The most important question at the end of the third month is:

Can we increase the number of advocates without increasing chaos at the same rate?

If every new customer requires someone to search for information manually, obtain approvals from scratch, and check with five teams to see who contacted them most recently, the program is not yet ready to scale.

After the first 90 days, the program should be built around six elements:

• objective,
• selection,
• value,
• activation,
• process,
• measurement.

Each element answers a different question. The objective explains why customer advocacy exists. Selection defines which customers are worth engaging. Value answers why participation makes sense for the customer. Activation describes the available forms of involvement. Process protects the relationship between teams and the customer. Measurement shows whether the program is creating something more than a list of completed activities.

The biggest mistake is to build only the fourth element. A company creates a catalog: webinar, case study, review, referral, event. It knows what it can do with an advocate, but still does not know why, with whom, when, or what the outcome is supposed to be.

Tip: customer advocacy maturity is not about increasing the number of options. It is about getting better and better at matching the right activation to the right person at the right moment.

You do not always need an advanced platform, a dedicated team, and a complex points system from day one. At the beginning, a simple and consistently maintained set of information connecting Customer Success, Marketing, and Sales is enough. At a minimum, you need to:

• know who could be a potential advocate;
• record their preferences and constraints;
• know who owns the relationship;
• see the history of previous activations;
• control the number and frequency of requests;
• record the results of activities;
• regularly discuss new engagement opportunities.

In practice, the biggest problem is often not a lack of strong customer relationships, but a lack of shared knowledge about them. Customer Success knows who is satisfied. Sales knows who has already provided a reference. Marketing remembers the people who joined webinars. Product has its own list of active users. Only when this information is combined does the real customer advocacy potential become visible. Without it, the company is left with separate pieces of the puzzle. It knows it has many satisfied customers. It does not know which of them want to build a more active relationship with the brand.

If you want to start simple, do not design a multi-tier program with dozens of segments from day one. It is enough to answer the six basic questions in the table below:

That is enough to stop treating customer advocacy as a series of spontaneous requests. The goal is not to build a perfect program from day one. The goal is for every new activation to generate information that can also be used to improve the system as a whole.

At the beginning, it is very easy to report what is simplest: how many advocates we have, how many case studies were created, how many customers appeared on webinars, and how many reviews we collected. These numbers are useful, but they primarily describe activity. During the first 90 days, it is better to focus on four things:

1. Program readiness: do we have defined candidates, recorded preferences, and a single process for handling requests?
2. Participation: how many customers accept the invitation, how many actually complete an activation, and how many want to do something again?
3. Quality: are the resulting references, conversations, case studies, and events useful to their audiences and to internal teams?
4. Impact: is customer advocacy helping sales, building trust, supporting product development, strengthening the community, or advancing the other objectives for which the program was created?

The repeat engagement rate is particularly revealing. Ten customers who agreed to one request may look good in a report. Six who want to return after their first activation or accept subsequent opportunities provide a much stronger signal that the program is genuinely creating value.

In other words, after one quarter it is better to be able to say:

“We have 15 active advocates, most of them have defined their preferred formats, nine have engaged again, and reference calls have supported specific sales opportunities”

rather than:

“We ran four webinars, created three case studies, and collected eight quotes.”

Why? The first statement describes a system that is developing; the second describes tasks that were completed.

Effective customer advocacy is not about having a large database of satisfied customers. Nor is it about regularly collecting new quotes, reviews, and case studies. Those are only the visible outputs of activity. A real program begins when the company can identify the right customers, offer them meaningful value, match the form of engagement to the individual, and manage the relationship in a way that can be repeated without exhausting trust.

For these reasons, the first 90 days are best approached in three stages:

• the foundation shows why the program exists and whom we want to engage;
• the pilot shows whether customers actually want to participate;
• the system shows whether successful activations can be repeated and scaled.

The biggest mistake is trying to accelerate the third stage before completing the first. A large advocate list will not help if the company does not know their preferences. More activations will not help if different teams keep asking the same customers for everything. More case studies will not help if nobody uses them afterward.

In short: do not build the program around the question, “What else can we get from our customers?” Build a system in which the right customers have a reason to engage in the right way at the right time.

Customer advocacy without a process is a collection of favors. Customer advocacy with a strong process becomes a system for building trust, social proof, and relationships that genuinely help the business grow.

1. What is customer advocacy?

Customer advocacy is a program for engaging customers who are willing to actively share their experience with a brand or support its development. It can include recommendations, reviews, case studies, reference calls, events, expert content, referrals, or participation in product initiatives. The key point is that these activities are part of a structured relationship rather than isolated requests sent whenever the company needs a piece of content.

2. How should you select the first customers for a customer advocacy program?

It is worth looking at both satisfaction levels and customer behavior. Strong candidates include people who have achieved a concrete result, have a good relationship with the company, actively provide feedback, spontaneously recommend the solution, or have already taken part in additional activities. Their availability, preferences, and any restrictions on speaking publicly also matter.

3. How many advocates do you need at the beginning?

A small group is usually enough for a pilot, for example 8-15 customers. This makes it possible to test the invitation process, different activations, approvals, and communication without building a large infrastructure from the outset. The first objective is not to recruit as many people as possible, but to find a model that can later be repeated.

4. What activities can customer advocacy include?

The range can be very broad: from a short quote, review, or recommendation to a reference call, case study, webinar, event appearance, customer roundtable, customer advisory board, or product session. Not every customer should participate in every format. The program should match the activity to each person’s preferences, experience, and circumstances.

5. How should you measure the effectiveness of a customer advocacy program?

Do not stop at the number of advocates or completed activations. You should also track how many customers engage again, which formats are most valuable to them, whether the resulting materials are used by Sales and Marketing, and whether the activity leaves a measurable trace in business processes. During the first 90 days, confirming that a healthy, repeatable system is taking shape is more important than calculating a sophisticated ROI.