Your executive summary should make the decision easier. Use this structure to connect the client's problem, your approach, and the outcome.
Clients do not read proposals in order.
They skim the first page, jump to the investment section, and decide whether the rest deserves attention. Your executive summary has one job: make the decision easy to understand.
Start with their situation
Open by naming the problem in the client's language. Avoid a generic introduction to your background. The client already knows who they invited.
Write: “You are trying to ___, but ___ is getting in the way.” That sentence proves you heard the conversation.
Define the outcome
Describe what changes when the engagement is complete. Use observable outputs: a documented process, a prioritized roadmap, a trained team, or a decision supported by evidence.
Do not promise a result you cannot control. Promise the work and decision support that create a credible path to it.
Explain the approach in three steps
Keep the summary high level:
1. understand the current state
2. make the key decisions
3. deliver and transfer the work
The details belong later. The first page needs a map, not every turn.
Name the client's role
Tell the client what you need from them: access, a weekly decision window, subject-matter interviews, or review of a draft. Clear participation requirements prevent a passive project from becoming a stalled one.
End with the next decision
Close with a specific next step, such as selecting a start window or confirming the project sponsor. “Let me know what you think” creates another open loop.
A strong executive summary is not a sales speech. It is a short, accurate agreement about the problem and the work ahead.
[Make the next client decision easier](https://getconsultkit.com)
ConsultKit makes it systematic
Each app starts at $9/month. Monthly billing only. See the current pricing steps and caps.
The Solo Consultant Brief
Weekly tips on referrals, pricing, and client management — straight to your inbox.
Prefer shorter ideas? Follow @getConsultKit on X.