Back to insights

Five Roles in the Committee Sale

Almost no enterprise sale is a simple back-and-forth between two people. It's an ensemble piece, and treating it like one long conversation repeated in more rooms is one of the costliest mistakes an experienced seller can make.

Sales team at a business conference

Almost no enterprise sale is a simple back-and-forth between two people.

It's an ensemble piece, and treating it like one long conversation simply repeated in more rooms is one of the costliest mistakes an experienced seller can make. The same message, delivered the same way, to five different people with five different stakes in the outcome, will land differently in every room. In some of those rooms, it won't land at all.

In my experience, five roles recur often enough in committee sales to be worth naming individually. I've given each one a name from the stage rather than the org chart, and I want to explain why.

The traditional sales vocabulary, champion, economic buyer, technical evaluator, blocker, is accurate, but it describes what each person does in the process. The theatrical terms describe what each person needs from the story. That distinction matters because your job in a complex sale isn't just to navigate a decision process. It's to make sure the right argument reaches the right person in a form they can act on. Thinking about each stakeholder as a role in a scene, rather than a function in a workflow, tends to surface the right questions faster.

If you've spent time in enterprise sales, you'll recognize every one of these people. You've just been calling them something else.

The Protagonist

What sales teams typically call this person: the champion.

The Protagonist is your champion, the person who has staked something personal on the outcome. Their credibility, their project, their reputation for making good calls. That personal stake is what makes them useful, and it's also what makes them vulnerable.

The reason I use Protagonist rather than champion is that champion implies someone cheering from the sidelines. A Protagonist is the one carrying the story forward. They have the most to gain if the decision goes right and the most to lose if it doesn't. That distinction shapes how you work with them.

A champion is not simply someone who likes your solution. A champion is someone who needs this decision to reflect well on their own judgment, publicly, long after the ink dries. A person who likes your product but has nothing personally at risk will not fight for you when the room turns skeptical.

Your job with the Protagonist is not just to keep them informed. It's to make sure they can carry the argument convincingly into rooms you'll never enter. That means giving them language, not just information. It means helping them anticipate the questions they'll face and preparing them to answer those questions in their own voice, not yours.

The Producer

What sales teams typically call this person: the economic buyer or budget authority.

The Producer controls the budget and is rarely in the room. They approve or veto from outside the process, receiving your argument secondhand, through your champion.

The reason I use Producer rather than economic buyer is that economic buyer focuses on the transaction. A Producer is the one who decides whether the show gets made at all. They're not evaluating your product. They're evaluating whether this decision is worth the risk, and they're doing it almost entirely based on what your champion chooses to pass along.

You're effectively writing dialogue for a character you may never meet.

This is one of the most underestimated challenges in enterprise selling. A nuance that matters to you may not survive the translation. A concern the Producer has may never reach you in time to address it.

The practical implication: help your champion understand not just what to say, but what the Producer is likely to care about.

The Chorus

What sales teams typically call this person: end users, influencers, or the implementation team.

The Chorus lives with the daily operational consequence of the decision. They're the people who will actually use what you're selling, manage the implementation, or absorb the disruption of change.

The reason I use Chorus rather than end users is that end users suggests a passive audience. A Chorus has a voice, and in Greek theater the Chorus often knew things the main characters didn't. That's true here too. The Chorus often has the least formal power and the most accurate information about whether the solution will actually work.

Dismissing the Chorus because they lack budget authority is one of the more reliable ways to lose a deal that looked secure on paper. They may not be able to approve the decision, but they can slow it, complicate it, or quietly undermine it after the fact. More importantly, they often know things about the real problem that no one else in the process will tell you directly.

When the Chorus is skeptical, find out why before you try to address it. Their skepticism is usually specific, and it's usually worth taking seriously.

The Critic

What sales teams typically call this person: the technical evaluator, the skeptic, or the devil's advocate.

The Critic asks the question nobody else will.

The reason I use Critic rather than technical evaluator is that technical evaluator implies a narrow, functional role. A Critic is doing something more important: they're testing whether the argument holds up. That's a service to the room, not an obstacle in it.

Treat them as an obstacle and they'll behave like one. Treat them as the person whose hard-won approval will convince the room, and they often become your most credible witness.

The Critic is not opposed to your solution. They're opposed to being wrong. They ask hard questions because they've been burned before, or because they're responsible for something that depends on this decision going right. When you answer their question well, directly and without defensiveness, you demonstrate something the rest of the room has been watching for.

Don't try to neutralize the Critic before the meeting. Engage them early, take their concerns seriously, and let them see that you're not rattled by scrutiny. That's usually enough.

The Antagonist

What sales teams typically call this person: the blocker, the internal competitor, or the incumbent's advocate.

The Antagonist has a genuine interest in the deal not happening: a competing project, loyalty to the incumbent, general aversion to change, or something more personal that no amount of evidence will fully dissolve.

The reason I use Antagonist rather than blocker is that blocker implies the problem is procedural. An Antagonist has a motive. Understanding what they're protecting is more useful than trying to route around them.

You can't validate your way into an ally here. The realistic goal is not conversion. It's neutralization. That means understanding what the Antagonist is protecting and making sure the decision process doesn't give them an outsized opportunity to block it. It also means not wasting energy trying to win them over at the expense of the people who are genuinely persuadable.

Prepare like you're going into a play, not a pitch

Improv theater has a useful concept called character mapping. Before a long-form show, the ensemble talks through who each character is, what they want, and how they're likely to respond to what happens on stage. Not to script the scene, but to walk in with enough awareness that nothing catches you completely off guard.

A complex committee sale deserves the same preparation.

Before your next stakeholder meeting, write down the five roles and map the people you know against them. Then work through each one:

  • **Protagonist (your champion):** What argument do they need to make internally? What questions will they face that you haven't prepared them for?
  • **Producer (your economic buyer):** What does your champion actually know about what the Producer cares about? What are you assuming they'll pass along correctly?
  • **Chorus (your end users and implementation team):** Who in this group is skeptical, and have you found out why? What do they know about the real problem that you haven't heard yet?
  • **Critic (your technical evaluator):** What is the hardest question this person is likely to ask? Have you answered it, not deflected it, in a way that will hold up in the room?
  • **Antagonist (your blocker):** What are they protecting? Does the decision process give them an opportunity to block that you haven't accounted for?

This isn't a script. It's a rehearsal. You're not trying to predict every line. You're trying to walk in knowing the ensemble well enough that you can respond to what actually happens, rather than the meeting you imagined.

The message that travels without you

A champion once forwarded me, by accident, the email chain she'd used to build internal consensus.

Most of it had survived in her own words, exactly as intended. One nuance about timing had flattened into a firmer promise than we'd actually made. I caught it and corrected the record before it reached the full committee.

That moment has stayed with me.

Writing for an audience you'll never personally address isn't a one-time drafting exercise. It's a habit of checking whether the message that left your hands is still the message arriving in rooms you can't see.

Your champion is not a passive relay. They're an active interpreter. The more clearly you understand what each of the five roles needs to hear, the better you can help your champion translate your argument into something that lands in every room, not just the ones you're in.

Bryan Christie

Author, Act Like You Can Sell

Email me