FrameworkExecutive Messaging

How to Write a Compelling Executive Summary like a Top Dollar Consultant

An SVP once asked how long his team had engaged us for, when we'd been paid $0 to date. Here's the Situation, Complication, Recommendation summary behind that moment, and how to write one with your champion.

By Nate Nasralla6 min read
The short answer

A consulting-style executive summary for a sales deal follows the SCR framework: Situation, Complication, Recommendation. The Situation lays out what's changing at the company and the goal they're working toward. The Complication names the problem in the way, its root causes, and what it'll cost if nobody acts. The Recommendation gives the approach and its decision criteria, then your solution and the alternatives.

On this page
    Questions answered

    Frequently asked questions

    What should an executive summary include?

    Three sections. The Situation covers what’s changing at the company and the goal they’re working toward. The Complication covers the problem standing in the way, its root causes, and what it’ll cost if it’s left unchecked. And the Recommendation covers the approach and its decision criteria, the solution you found and why, and the alternatives being considered.

    How is an SCR executive summary different from a 1-page business case?

    Both are business cases you build with your champion. The 1-page business case has five blocks: a priority-driven headline, the problem statement, the recommended approach, target outcomes, and the required investment. The SCR summary has three sections, ordered to start with what the executive already accepts, build the tension, and then make the recommendation.

    What’s the difference between an executive summary and an executive brief?

    An executive brief is internal: your team’s one-page prep before meeting a customer’s executive, including how you might lose the deal, so it stays on your side. An executive summary is written for the customer’s executives, built with your champion and in their words.

    Simplify complex sales: get the latest frameworks.

    Short, practical frameworks for executive messaging, business cases, multithreading, and sales enablement.

    © Nate Nasralla · Complex sales training & advisory

    A few years ago, I was on a call with an SVP at a $5B cloud communications company (I realize that sounds like the start of every lame LinkedIn post out there, so hang with me).

    He asked how long his team had engaged us for. Had they signed on for just this year, or set up something longer-term? I was a little confused, since neither was true. We were still working out if and how we'd structure our work together.

    Then he asked:

    "You mean we haven't actually bought anything from you yet?"

    I told him that was right. "That's surprising," he said.

    He'd assumed we had some type of consulting agreement or services retainer in place, the kind his team would easily spend $100,000 on. But we'd been paid $0 to date. We were just running our sales process.

    He assumed that, because we'd brought him specific data backing a clear and direct recommendation. Plus, everything we presented was built with two internal champions, in their branding. And when an executive is surprised they're not paying you yet, a contract is soon to follow. The back half of your sales process melts like butter dropped into a cast-iron skillet. No stalling on the decision, no back-and-forth on scope, no friction with procurement. It all just happens, fast.

    So in this post, I'm going to show you the framework we used to guide our discovery early on, and then, to make our recommendation to the three SVPs we were working with. It's called the "SCR."

    What's a consulting-style executive summary?

    It's a short doc that walks an executive through a decision in three parts: Situation, Complication, and Recommendation.

    I'm calling it a consulting-style framework because SCR comes out of Barbara Minto's work at McKinsey, where it was used to simplify a complex decision for executives. When I wrote Brief & Brilliant, it was also the second most-used business case framework inside our platform at Fluint, right behind the 1-Page Business Case.

    Each part answers one question:

    What goes inside the executive summary?

    The whole thing fits on one page, with your champion's name at the top.

    Typically, I lay it out like this: 

    Consulting-style executive summary template with Situation, Complication, and Recommendation sections

    Here's a short word on each section:

    1. Situation. Start with the facts and the company's priorities, the things that are already known and accepted.

    Because if you don't get agreement here, the next two sections fall apart. So if you think the executive would push back on a bullet, rework it with your champion before you write anything else. Then close the section on the goal, in terms of where the executive wants to take the company.

    2. Complication. This is why the situation needs action now, and why things will get much worse if nobody resolves it.

    Without enough tension here, decisions stall out. So list the root causes too, since they set up the recommendation that's coming, and put a cost on leaving it alone.

    3. Recommendation. The specific course of action you're recommending.

    Which will always be more than just "buy my product." So in the solution bullets, include the dates, projects, and people invested, plus a short word on proof points and the outcomes after acting.

    What does a finished executive summary look like?

    Now, back to that SVP. Here's the SCR message we used, with the share numbers left as X and Y:

    Did you catch whose voice that's in?

    "Our core VoIP product," "our product is already lagging," "our M&A."

    That's the company talking, because two of their own people helped write it. The specific data is there too, in the share they'd lost over three years. And the recommendation is a strategy they could own (buy the technology rather than build it), while we only show up in the last sentence, as the scouting partner that makes it work.

    Where should the problem sit inside the summary?

    Notice the Situation above never states the problem. That's because where it goes depends on how aware the executive already is of it:

    And in an RFP or an active buying process, you can flip the order and lead with the R. Most deals stall for lack of a decision and resistance to change, but if the buying team is already past the S and the C, and is actively comparing who to partner with, jump straight to the recommendation.

    Be aware, though, if you're late to the party: another vendor has likely already shaped how the buying team sees the S and C.

    Who should write a good exec summary?

    You draft it, with your champion.

    The template's byline says "Developed by," followed by your champion's name and the key deal players, and every section is in their first person ("we've seen," "our goal is," "we believe").

    The 1-page business case breakdown has the full reasoning for putting your champion's name on it.

    And then, when your champion sends it up the chain and around the org, give them a forwardable email to send it with. For the version they can remember and repeat without the page in front of them, use the 4-sentence soundbite.

    So pick one deal where an executive has to make the call, even an early one, and write three Situation bullets your champion would agree with as written. If they'd push back on any of them, that's your next conversation.