Mutual Action Plan: How SEs and AEs Build One (+ Template)

Most guides to mutual action plans are written as if a deal has one seller. It doesn't. In any complex B2B deal there are two: the account executive who owns the commercial path and the sales engineer who owns the technical one.

My position is simple: a mutual action plan that doesn't split ownership between the SE and the AE is a to-do list, not a plan. This guide covers how SEs and AEs build one together, milestone by milestone, and ends with a role-tagged mutual action plan template you can copy today.

What Is a Mutual Action Plan (and Why SEs and AEs Need One Together)

Definition: A mutual action plan (MAP) is a shared, buyer-facing document that lists every milestone between today and a signed contract, with a named owner and a date on both the buyer side and the seller side. You'll also see it called a mutual success plan, a joint execution plan, or a close plan.

What the standard definition misses is who sits on the seller side. The AE runs discovery, pricing, procurement, and signatures. The SE runs the technical proof: requirements, security review, integrations, the demo, and any hands-on evaluation.

Those are two different workstreams with two different buyer audiences. One product leader who used to run a sales engineering team described how his buyers split their deal rooms exactly this way:

"The infosec and technical content is for one audience and then the other one that rep is more managing is you know, is for like the sales content."
- [Principal Product Manager, sales software]

If your MAP doesn't reflect that split, one of two things happens. The AE ends up tracking technical milestones they can't judge, or the SE finds out about the plan after the AE has already promised dates. Before you build anything, make sure you are qualifying the buying committee well enough to know which stakeholders sit on which track.

Mutual Action Plan vs. Mutual Success Plan vs. Close Plan

These three terms get used interchangeably, and in many teams they describe the same document. When teams do draw a line, it usually falls along two questions: who can see it, and where it ends.

• Mutual action plan. Buyer-facing and co-owned. It runs from today to a signed contract, with a buyer owner and a seller owner on every row.
• Mutual success plan. Also shared with the buyer, but often framed around the outcome rather than the signature. Teams that use this label tend to extend it past the contract into implementation and the first results the buyer expects.
• Close plan (or sales close plan). Often the seller's internal version: the steps, risks, and dates the AE needs to hit the forecast. It becomes a mutual action plan the moment the buyer sees it and agrees to it.

My advice: keep one document and let the buyer see it. An internal close plan that disagrees with the plan the buyer is working from is how forecast dates drift away from reality. If you want a refresher on the stages these plans sit on top of, see our breakdown of the B2B sales process.

Why Mutual Action Plans Break Down Without Clear SE/AE Ownership

Every rep wants the same thing from a MAP: a buyer who opens it, updates it, and pulls the deal forward alongside them. Very few get it. The same former sales engineering leader put it bluntly:

"That's what every sales rep wants, is they want to be able to do a mutual action plan and have the prospect leaning in with them and updating stuff. But that's a challenge. Even when we do it in a Google Doc or a spreadsheet or something that we then share and make the customer a collaborator on"
- [Principal Product Manager, sales software]

I think the real cause is upstream. When nobody on the seller side clearly owns a milestone, the buyer has no one to answer to, so the plan goes stale.

Ambiguity breaks MAPs in two predictable directions:

• Technical milestones stall when no one owns them. The security questionnaire sits in someone's inbox. The POC environment never gets provisioned because the AE assumed the SE was on it and the SE never saw the request.
• Commercial milestones stall when the SE arrives late. Procurement asks a technical question two weeks before signature, the SE hasn't seen the deal, and the close date slips while they catch up.
• Capacity makes both worse. When SEs are fully booked, AEs can't get technical help at the moment the buyer is ready, and momentum dies.

That third point came up again and again. One SE manager at a restaurant-operations software company described it like this:

"When we have AES are like, oh well I have someone who really needs a demo but the SEs are booked and it creates a lot of that chaos."
- [Manager, Solutions Engineering, restaurant operations software]

A clear ownership split is the cheapest way to shorten your sales cycle, because it removes the waiting time between "someone should do this" and "this person is doing it by Thursday."

The Role Split: What an AE Owns vs. What an SE Owns in a MAP

A MAP with a single "seller" column hides the handoffs, and handoffs are where deals leak. If you're unclear on the boundary, start with what a solutions engineer actually owns in a modern sales team.

Here is how I'd divide it:

The rule of thumb: if a milestone can be blocked by a technical question, the SE owns it. If it can be blocked by a budget, contract, or executive, the AE owns it.

AE-owned milestones

The AE owns everything that moves money and authority. That means pricing and quoting, procurement, executive alignment, contract redlines, and signatures.

The AE also owns the buying committee map: the economic buyer, the vetoes, and who has gone quiet. One product marketing director described the value of this visibility: knowing "who's actually really engaging versus, like who may be a detractor here or who has chosen not to engage."

SE-owned milestones

The SE owns technical discovery, POC or pilot setup, security and compliance review, integration scoping, and the custom demo build. If your team blurs these, it helps to be clear on how a POC differs from a demo, because the two carry very different effort and commitments.

Hands-on access should be a milestone the buyer earns, not a default. Buyers we spoke with described granting a sandbox only on large deals, after a business case and executive buy-in. The SE also owns technical accuracy, and one buyer described the right reflex when an AE is out of their depth:

"Like if a rep is being asked a question that they don't know the answer to, we often just tell them like, look, that is a good opportunity to set up another call and pull in a technical expert."
- [Principal Product Manager, sales software]

Shared milestones

Three milestones need both sellers: discovery outputs, the demo itself, and the business case. The demo is the most common failure point, which is why both sellers should agree on a clear demo agenda before the call, not during it.

The business case is shared because the AE owns the commercial value and the SE owns the proof that it's achievable. If either signs off alone, the buyer's CFO will find the gap.

When to Introduce the MAP, and Who Presents It First

Timing is where most competitors agree, and I mostly agree with them. Introduce the MAP once you have confirmed a real problem and a buyer willing to invest time, not on the first call. Too early and it reads as presumptuous; too late and you're documenting a deal that has already drifted.

The part nobody discusses is who speaks first: the AE introduces the plan, the SE presents the technical track. That signals to the buyer that the technical evaluation has an owner of its own, not an afterthought.

A practical timeline:

1. End of first discovery call. The AE previews the idea: "If this is a fit, we'll build a shared plan together."
2. After technical discovery. The SE has enough to draft technical milestones and success criteria.
3. Joint working session. Both sellers walk the buyer through a draft, and the buyer edits it live.
4. After each major milestone. The plan is revised, not rewritten, and dates are re-confirmed.
5. Before procurement. The AE re-presents the remaining path to signature with named buyer owners.

Step-by-Step: How an SE and AE Co-Build a Mutual Action Plan

This is the core workflow. Each step has a clear owner and a clear output, so neither seller is guessing what the other has done.

Step 1: AE captures business goals and buying committee in discovery

The AE runs a structured sales discovery process and leaves with three things: the business outcome the buyer wants, the date that outcome matters by, and the names of everyone who can say yes or no.

This step decides the quality of everything after it. An SE manager told us what happens when it goes wrong:

"When there's poor discovery, you know, it kind of puts you in this position where it's like, well, I guess we're going fishing with the demo."
- [Manager, Solutions Engineering, restaurant operations software]

Step 2: SE translates technical requirements into milestones

The SE takes the discovery notes and turns requirements into dated, testable milestones. "Needs SSO" becomes "SSO configured in sandbox, validated by the buyer's IT lead, by March 14."

The SE also narrows scope here. Every requirement that isn't tied to the buyer's stated outcome becomes a leave-behind, not a demo segment.

Step 3: Joint milestone-mapping session with the buyer

Both sellers join one working session with the buyer's champion and, ideally, their technical lead. The AE walks the commercial path; the SE walks the technical path; the buyer corrects both.

Do this live, with the buyer typing. A plan the buyer edited is a plan the buyer owns.

Step 4: Assign named owners on both the buyer side and seller side

Every row gets two names: one buyer, one seller. "Legal" is not an owner; "Priya, legal counsel" is.

Seller-side, every row is tagged AE or SE. If a row has both, split it into two rows.

Step 5: Weekly AE/SE co-review cadence before the buyer-facing check-in

Fifteen minutes, every week, before the buyer call. The AE and SE review what slipped, who is going quiet, and what each will say.

This is what keeps the MAP a living document. Skip it and the plan goes stale within two weeks.

What to Include in Your Mutual Action Plan Template

Here is what the template needs, with the SE/AE twist on each:

• Objective and value statement. One or two sentences in the buyer's words describing the outcome and why it matters now. The AE drafts it; the buyer approves it.
• Stakeholders. Every buying-committee member with their role, their track (commercial or technical), and their paired seller.
• Milestones. The ordered steps from discovery to go-live. Tag each one AE, SE, or Buyer so ownership is never inferred.
• Dates. A target date for every milestone, plus the final date the buyer cares about.
• Success criteria. What "done" means for each technical milestone, written by the SE and agreed by the buyer's technical lead.
• Resources. Links to the demo recap, security documentation, pricing proposal, and anything else a stakeholder needs.
• Status. Not started, in progress, done, or blocked. Blocked rows should say who is blocking and what unblocks them.

Keep one source of truth for these assets. If the security documentation lives in one system and a copy lives in the plan, one of them will be out of date by week three, and the buyer will find the wrong one.

Mutual Action Plan Template: SE/AE Role-Split Example

Here is the template itself. Every row is tagged by owner type, which is the thing generic templates leave out.

The example dates are illustrative, not a benchmark.

Notice where the Shared rows sit. They cluster at the moments where one seller's work becomes the other seller's input: the working session, the demo, and the business case. Those are the rows your weekly co-review should check first.

Common Handoff Breakdowns Between SEs and AEs (and How to Fix Them)

Most MAP failures aren't failures of the document. They're failures at the handoff between the two people building it. These are the five I see most often, with the fix for each.

1. The SE is looped in after the MAP is already built. The AE drafts dates alone, and the SE inherits a POC timeline they never agreed to. Fix: no MAP goes to the buyer until the SE has signed off on every SE-tagged row.
2. The AE over-promises technical scope. A buyer asks for a feature, the AE says yes, and the SE discovers it needs a workaround. Fix: any technical commitment becomes an SE-owned row with success criteria, validated before it's promised.
3. Poor discovery forces a whole-product demo. The SE walks in without context and shows everything, and the buyer tunes out. One SE manager described the default all too well: "I guess I'm going to demo the Pro. Like, the whole product." Fix: agree a narrow scope for each demo in the co-review, and send a leave-behind for everything else.
4. No shared view of milestone status. Fix: one plan, one status column, reviewed together weekly.
5. Headcount becomes the default fix. When handoffs are unclear, teams hire another role to sit between them. A head of strategic sales at an IoT connectivity company named the cost directly:

"I would love to solve that some of that programmatically rather than through a role or you know, like, like headcount is an expensive way to solve that."
- [Head of Strategic Sales, IoT connectivity]

Fix: define the handoff as a row in the MAP with a named owner and a date. Process scales; extra headcount mostly adds another handoff.

Where Buyer Hubs Fit: Hosting the Mutual Action Plan Next to Your Demos

Full disclosure: this is us. Storylane builds Demo Suite, so weigh this section accordingly.

The mechanism is simple. Three rows in the template above depend on the buyer seeing the product when the SE isn't in the room: the demo recap, the scoped demo, and the hands-on evaluation. That is exactly where SE capacity breaks.

The other problem is location. A MAP in one tab, the demo recap in an email thread, and the security docs in a shared drive means every stakeholder has to assemble the deal themselves. A digital sales room fixes that by putting everything behind one link. Storylane's version is Hubs: a per-deal room that holds demos, videos, case studies, pricing, and PDFs, so the plan itself can sit right next to the demos it refers to.

The part that matters for a MAP is tracking. Hubs show which stakeholder opened the room, what they watched, and how long they stayed, with time spent and completion per asset. Before your weekly AE/SE co-review, that tells you whether the InfoSec reviewer actually opened the security documents and whether the economic buyer ever looked at the business case. You can also get a Slack or Teams alert when stakeholders engage.

A marketing lead at a cybersecurity software company, planning SE enablement, described the intended recap use: "So this is what I showed you. Here's a self guided version of what I was able to show with you on the call."

Where we don't fit: if your deals close in one call, you don't need a MAP, and you don't need a deal room either. And if your team has no discipline around the SE/AE split, no tool will create it for you. Fix the process first.

Mutual Action Plan Software: What an SE/AE Team Should Look For

You can run a MAP in a spreadsheet, and many teams should start there. When you evaluate dedicated software (usually sold as part of deal room software), judge it on whether it makes the SE/AE split easier, not on its feature count.

Here is what to look for:

• Real two-way collaboration. Buyers should be able to comment, ask questions, and tick off their own rows. Document sharing alone is a one-way street, and buyers treat it like one.
• Co-owner permissions. The AE and SE both need edit rights to the same plan, and so might a second SE or a manager.
• Buyer-visible status with quiet tracking. You want to check whether the InfoSec reviewer has opened the security docs when you choose to, not get an email every time someone clicks.
• Reusable templates. Recurring tracks like security review should start from a template, not from scratch.
• CRM sync. Milestone status should flow to the opportunity record so forecasting reflects the plan.

Buyers were frank about where incumbents fall short.

One described Highspot as "a buyer hub that's way more complex for what we need." Another warned against a tool turning "into what Seismic turned into which was like kind of duplicate instance of managing our Google Drive content."

Pricing matters too. When you evaluate any vendor, ask how pricing scales with seats, whether viewers cost extra, and what you pay if adoption is uneven across teams.

Best Practices for Keeping SEs and AEs Aligned on the MAP

The template gets you started. These habits keep it alive past week two.

• Operationalize it where the deal lives. Put the MAP in your CRM or deal room, not in a personal drive. If the plan can't be found from the opportunity record, it doesn't exist.
• Revisit it weekly, together. The fifteen-minute AE/SE co-review is the single highest-leverage habit here. It's where slipping dates and silent stakeholders get caught.
• Keep it buyer-facing. A MAP the buyer never sees is an internal forecast note. Share it, and let the buyer edit.
• Give the SE control over technical assets. New AEs in particular shouldn't be picking which technical demo to send. An SE manager told us, "I still would want the SE to own it because in our smaller segments our AES are still so new."
• Close the loop after every call. Send the recap within a day, update the plan, and name the next owner. A MAP that lags the conversation loses the buyer's trust.

Conclusion

Mutual action plans work when both sellers own a visible piece of them. How SEs and AEs build one together comes down to four things: split ownership by milestone type, co-build the plan with the buyer in the room, review it weekly before every check-in, and hand the buyer resources they can use without you.

Start with the role-tagged template above. Tag every row, run the co-review for a month, and watch which rows slip. That pattern will tell you more about your handoffs than any guide can.

If you take one thing from this piece, make it the owner column. A plan where every row says AE, SE, or Buyer forces the conversation most teams avoid: who is actually on the hook for this date. Have that conversation in week one, and the MAP stops being a document you maintain and becomes the way the deal actually runs.

FAQ

What is a mutual action plan?

A mutual action plan is a shared, buyer-facing document listing every milestone between today and a signed contract, each with a buyer owner, a seller owner, and a date. It keeps a multi-stakeholder deal from drifting between meetings.

Who owns the mutual action plan, the AE or the SE?

Both, but for different rows. The AE owns commercial milestones such as pricing, procurement, and signatures, while the SE owns technical milestones such as requirements, security review, and POC setup.

How many milestones should a MAP have?

There is no fixed number. Include every step that can block the deal, from discovery to signature; the illustrative template above uses ten. If you can only list a handful, the deal may be simple enough not to need a MAP.

What's the difference between a MAP and an account plan?

A MAP is shared with the buyer and focused on closing one deal. An account plan is an internal document covering the whole customer relationship, including expansion, risks, and long-term strategy.

When should you introduce a mutual action plan to a buyer?

Introduce it once you've confirmed a real problem and a buyer willing to invest time, usually after the first or second discovery call. The AE should preview it and the SE should present the technical track once technical discovery is done.

Is a mutual success plan the same as a mutual action plan?

Usually, yes. Many teams use the terms interchangeably. When they differ, a mutual success plan tends to extend past signature into implementation and the outcomes the buyer expects, while a mutual action plan stops at the signed contract.

What is a close plan in sales?

A close plan (or sales close plan) lists the steps, owners, and dates needed to get a deal signed. It is often an internal seller document; once it is shared with and agreed by the buyer, it works as a mutual action plan.

Where should a mutual action plan live?

Somewhere both the buyer and the sellers can reach from one link, next to the resources each milestone depends on. That can be a shared doc linked from the CRM, or a digital sales room that holds the plan alongside demos and documents.

Sources

This article cites no third-party statistics. All buyer evidence comes from anonymized Storylane sales-call transcripts, with names and companies removed.

• Storylane, anonymized customer and prospect call transcripts, 2026

Want to see how Hubs and interactive demos fit into your mutual action plan? Book a demo of Storylane.