What is a buying committee map for early SaaS?

A buying committee map is a one-page list of who can buy, who can block, and who only talks.

Early SaaS teams treat "the buyer" as one person. Usually the champion who booked the demo. Then the deal dies in a security review, a budget freeze, or a VP who never saw the product. That was not bad luck. That was a missing map.

Without a buying committee map, you burn demos on champions who cannot buy.

What seats belong on the map?

Name five roles even if one person wears two hats.

1. Economic buyer. Signs or can kill the spend. Often a VP, founder, or finance lead. If you have never spoken to them, you do not have a deal. You have a tour.
2. Champion. Wants you to win and will push inside. Useful. Not sufficient.
3. Blocker. Can stop the deal: security, legal, IT, a competing tool owner, a skeptical peer. Ignoring them does not make them disappear.
4. User. Lives in the product daily. Their pain is real. Their signature often is not.
5. Info seller. Shares context but cannot move budget: analyst, consultant, friendly operator in another team. Warm. Not a close plan.

A warm account vs a warm contact distinction matters here. A warm champion contact inside a cold committee is still a cold account for close purposes.

Why do early SaaS teams skip the map?

Because one enthusiastic champion feels like progress, and mapping feels like enterprise theater.

You are a five-person company. The prospect is a 40-person company. You tell yourself committee maps are for Fortune 500. Then procurement asks for a SOC 2. Legal rewrites the MSA. The VP of the champion's boss asks why this tool exists when they already bought something adjacent. You learn the committee existed. You just met it after the demo.

Firmographic fit vs buyer intent tells you whether the company is in range. The committee map tells you whether the people inside can finish the path.

How do signals map to each seat?

Different seats leave different traces. Treat them separately.

• Economic buyer signals: budget cycle language, "send me a one-pager for my boss," procurement CC, security questionnaire started.
• Champion signals: repeated product use, internal forwards, intro offers, buying window language ("we need this before Q4").
• Blocker signals: "we already standardized on X," security holds, silent IT, competing evaluation threads.
• User signals: feature questions, invite loops, activation events, support tickets that sound like adoption.
• Info seller signals: helpful Slack threads, "you should talk to…," no calendar power.

If your outbound and inbound both speak only to the champion, you are running a single-threaded fantasy. Buyer agents will make this worse if an agent books the champion and your AE still has no map for the rest of the room.

How do I build a buying committee map in practice?

Keep it ugly and current. One page per open opportunity over a dollar threshold you care about.

1. List the five seats. Write names or "unknown." Unknown is allowed. Pretending is not.
2. Mark power. Who can say yes alone. Who can say no alone. Who can only recommend.
3. Attach one signal and one message per known seat. Champion gets the pain story. Economic buyer gets the outcome and the bill. Blocker gets the risk answer.
4. Set a multi-thread rule. No second demo until at least one non-champion seat is identified or a written path to them exists.
5. Update after every call. Champions leave. Blockers appear. The map is a living object, not a kickoff slide.

If the economic buyer is still "unknown" after three meetings, you do not have pipeline. You have a friendship.

What does Signals mean here?

Signals is finding who is in market and who can finish the buy. A committee map turns "someone clicked" into "these seats matter."

Adapt or fail. Map the room before you book the room.

Start Signals, Convert, Grow

FAQ

What is a buying committee map?

A short document that names the economic buyer, champion, blocker, user, and info seller for an account, with power notes and the signal or message that fits each seat.

Do early-stage startups really need this?

Yes, anytime more than one person can stop the deal. That includes most B2B SaaS above a self-serve credit card.

What if one person is champion and economic buyer?

Write both seats with the same name. The map still forces you to check for blockers and users so you do not miss a silent veto.

How is this different from an org chart?

An org chart shows reporting lines. A buying committee map shows who can move money and who can kill the deal for your specific purchase.

When should I fill the map?

Before the second meeting on any opportunity that needs a human close. If you wait until proposal stage, you are mapping a funeral.