After this lesson you will be able to
- Map every role on a buying committee and what each needs to approve the deal
- Build a mutual action plan with dates and owners on both sides
- Multi-thread a deal so it survives a champion leaving or going quiet
- Prepare early for security, procurement and finance reviews instead of reacting late
Map the committee before you need it
Most deals that slip in the last month were not lost in that month. They were lost when a role nobody met appeared with a question nobody had answered. The fix is simple: map the committee in the first few weeks, while there is time to meet everyone.
Ask your champion to walk you through how a purchase like this was approved last time. Who signed? Who reviewed the contract? Did IT or security have to approve? Who in finance looked at it? The answers tell you the real process far better than an org chart does.
For each person, write down their role in the decision, what they care about, how they feel about the project today, and when you last spoke. Update it after every call. A map that is a month old is a guess.
Know what each role needs to say yes
Each member of the committee is answering a different question. Your job is to make sure each one has a good answer before the final meeting. Write your notes from their point of view, not yours.
The economic buyer controls the budget and can approve the spend. They need to see a business outcome worth the cost and a plan that will not embarrass them. IT needs to know the system fits the architecture, how it will be integrated and who will maintain it. Security needs answers on data access, compliance and vendor risk, usually through a formal review. Procurement needs clean terms and a fair price compared with alternatives. Finance needs the cost over time, when it hits the budget and how the return will be measured. Users need to believe it will make their day easier, not harder.
- Economic buyer: outcome, cost, risk to their reputation
- IT: architecture fit, integrations, ownership after go-live
- Security: data protection, compliance, review documentation
- Procurement: terms, pricing, process steps and timelines
- Finance: multi-year cost, budget timing, how return is measured
- Users and team leads: daily workflow, training, what goes away
Reach the economic buyer the right way
Many AEs either never meet the economic buyer or ask for the meeting in a way that makes their champion feel bypassed. The best approach is to make the meeting useful for the champion too.
Explain to your champion that leaders approve faster when they have heard the plan firsthand, and offer to prepare the meeting together. Keep it short, about the business problem and the decision, not a demo. Ask the economic buyer what success looks like in a year, what would make them hesitate, and how they want to be updated. Then follow up in writing with what you heard.
Build a mutual action plan the customer owns
A mutual action plan is a shared list of every step between today and go-live, with an owner and a date for each. It is not your close plan dressed up. It works only if the customer helps build it and agrees the dates are real.
Start from the date the customer wants to be live, then work backward: implementation start, contract signature, legal and procurement review, security review, final business case, technical validation and scenario demos. Ask the customer how long each internal step usually takes. Add their steps, such as a board meeting or budget cycle, that you would never have known about.
Share the plan as a simple document both sides can edit and review it on a regular call. When a date slips, ask why and what needs to change. A plan that never changes is probably not being used.
- Target go-live date and the business reason for it
- Each step, its owner on both sides, and its date
- Security and procurement steps with their real lead times
- Dependencies such as budget approval or a board meeting
- A standing review call and how changes are agreed
Multi-thread so one person leaving does not end the deal
Single-threaded deals are fragile. If your one contact changes jobs, goes on leave or loses influence, you start over. Aim for at least one relationship in each key role, and at least two people who would argue for the project if you were not in the room.
Multi-threading should feel natural to the customer. Offer specific reasons to meet each person: a technical session for IT, a security documentation walkthrough, a cost model review with finance, a workflow session with users. Each meeting should give that person something they need.
For example, a 400-person logistics company evaluating Service Cloud might involve the head of customer service, an IT architect, a security analyst, a procurement manager, a finance partner and three team leads. If your only contact is the head of customer service, the deal is at risk the day that person is busy.
Get ahead of security, procurement and finance
These reviews are predictable, so treat them that way. Ask in the first month who runs each review, what they need, and how long it usually takes. Get the security questionnaire early and start it. Ask procurement for their standard terms and process steps. Give finance a multi-year cost view and a clear way to measure return, built with the ROI calculator at /salesforce-account-executives/roi-calculator/ and the guidance at /resources/agentforce-roi-business-case/ when AI is in scope.
If implementation scope or cost is a concern for finance or IT, bring a delivery partner into a working session so they hear the plan from the people who will do the work. The deal desk at /salesforce-account-executives/deal-desk/ can help on a live deal.
Talk tracks
Early in the deal, mapping the committee with your champion
“Can you walk me through how the last purchase of this size was approved? Who signed, who reviewed the contract, and did IT or security have to sign off?”
Past decisions reveal the real process better than a hypothetical question.
Asking your champion for access to the economic buyer
“Leaders usually approve faster when they've heard the plan firsthand. Could we prepare a 20-minute conversation together so you can present it with me there to answer questions?”
It gives the champion credit and gets you the meeting.
Opening a meeting with the economic buyer
“I want to make sure this project is worth your investment. A year from now, what would make you say it was a good decision, and what would make you hesitate today?”
It surfaces the success measure and the hidden objection in one question.
Introducing a mutual action plan
“Would it help to write down every step between now and go-live, with owners on both sides? You know your internal steps better than I do, so I'd like you to correct the dates.”
Asking them to own the dates makes the plan real.
Requesting a meeting with IT or security
“Security reviews take time, and I'd rather start them now than hold you up later. Who runs that review, and can we get the questionnaire this week?”
It shows you respect their process and prevents a late delay.
Your champion goes quiet
“I haven't heard from you in a couple of weeks, and I want to make sure the plan still works for you. Has something changed, or is there someone else I should be talking to while things are busy?”
It gives an easy way to share bad news and opens a new thread.
Buying committee map and mutual action plan
Use it on a live deal. Tick items off as you go; nothing you tick leaves this page.
Common mistakes
Relying on one champion
When they leave or get busy, the deal stops. Build relationships in every key role.
Going around your champion to the economic buyer
It damages trust. Prepare the meeting together so the champion looks good.
Writing the action plan alone
A plan the customer did not build is just your forecast. Ask them to set and own the dates.
Discovering security and procurement in the final month
These reviews have lead times you cannot compress. Ask about them in the first month.
Ignoring the users
Users who feel left out can quietly slow a decision and later hurt adoption. Involve them in scenario sessions.
How you will know it is working
- Customers edit the mutual action plan and add steps you did not know about
- You have met the economic buyer before the proposal stage on most deals
- Security and procurement reviews start before the final business case
- Deals survive a contact leaving without resetting to an earlier stage
Questions
How many people should I be talking to on a typical deal?
There is no fixed number. Aim for at least one relationship in each role that has to approve the deal, plus a couple of users. Larger or more regulated customers will need more.
What if my champion won't introduce me to the economic buyer?
Ask why, gently. Often they are worried about losing control or looking unprepared. Offer to prepare together, keep the meeting short and let them lead it. If access is still refused, treat it as a serious risk to the deal.
Is a mutual action plan the same as a close plan?
No. A close plan is your internal view. A mutual action plan is shared with the customer, includes their internal steps, and has owners on both sides. It works because the customer agrees to it.
When should I start the security review?
As soon as the customer is seriously evaluating. Ask who runs it and request the questionnaire early. Reviews often take weeks, and starting late is one of the most avoidable causes of slipped deals.