Strategy Block
Solution Overview
A high-level solution slide that connects capability, outcome, and differentiator.
solution-overview1 slidebalanced density
Solution
One system, three outcomes
Present the solution as a simple set of capabilities tied to value.
01
Capability
02
Outcome
03
Moat
OPF Config
blocks:solution-overviewOPF JSON
{
"$schema": "https://openpresentation.org/schema/opf/v1",
"name": "Solution Overview",
"description": "A high-level solution slide that connects capability, outcome, and differentiator.",
"tone": "persuasive",
"narrative": "problem-solution",
"takeaway": "Show the proposed solution at a level executives can understand.",
"tags": [
"content-block",
"gallery:blocks/solution-overview"
],
"design": {
"colorScheme": "deep-purple",
"fontScheme": "poppins",
"background": {
"type": "pattern",
"pattern": {
"preset": "wave",
"foregroundColor": "#ddd6fe",
"backgroundColor": "#faf8f5"
}
}
},
"slides": [
{
"id": "solution-overview",
"layout": "image-beside",
"title": "One system, three outcomes",
"subtitle": "Capability, workflow, and measurable business value.",
"items": [
"Automate the bottleneck",
"Improve handoff quality",
"Measure the result"
]
}
],
"catalogs": {
"default": {
"source": "https://www.pptx.gallery",
"narratives": {
"problem-solution": {
"name": "Problem → Solution",
"summary": "Classic business arc: name the pain, raise the stakes, present your fix, show how it works, prove it, ask. The default for sales decks, internal proposals, and most general business presentations.",
"audienceFit": [
"customers",
"stakeholders",
"executives",
"internal-teams"
],
"duration": {
"min": 5,
"max": 30
},
"tags": [
"business",
"sales",
"general",
"proposal"
],
"beats": [
{
"id": "hook",
"name": "Hook",
"description": "Open with a striking question, statistic, customer quote, or moment that earns the audience's attention. The goal is to make them want to hear what comes next, not to convey information.",
"layout": "statement"
},
{
"id": "problem",
"name": "The Problem",
"description": "Name the pain in concrete terms. Make it visceral and specific — describe who hurts, how, and what they're trying to do today that isn't working. Avoid abstractions; use real examples or scenarios the audience recognizes."
},
{
"id": "stakes",
"name": "Why It Matters",
"description": "Quantify the cost of inaction or the upside of action. Use numbers, trends, customer impact, competitive pressure — whatever makes the audience feel the size of the problem and care about solving it now rather than later."
},
{
"id": "solution",
"name": "The Solution",
"description": "Reveal your approach and what it produces for the customer. Lead with the outcome, not the architecture. Keep it concrete: what does the audience get, and what changes for them?"
},
{
"id": "mechanism",
"name": "How It Works",
"description": "Show the moving parts that make the solution credible. Walk through the key mechanism, workflow, or technical insight that explains why this approach succeeds where others have failed. Enough detail to earn trust; not so much that you lose the room."
},
{
"id": "evidence",
"name": "Proof",
"description": "Demonstrate the solution works. Use customer logos, before/after metrics, demos, case studies, third-party validation — whatever de-risks the claim. One strong piece of proof beats three weak ones."
},
{
"id": "ask",
"name": "The Ask",
"description": "State a clear, specific call to action. What do you want the audience to do, decide, or commit to next? Make the smallest credible ask that moves things forward, and make it unambiguous.",
"layout": "list"
}
]
}
},
"tones": {
"persuasive": {
"name": "Persuasive",
"summary": "Argument-led voice for sales, fundraising, and recommendation-driven decks.",
"description": "Frame every section as an argument that builds toward an ask. Surface objections, answer them, and pair claims with the strongest available proof. Read more like a memo than a report.",
"voiceCues": [
"Lead each section with the claim it's making.",
"Surface the strongest counter-argument and address it.",
"Pair every claim with proof — customer, benchmark, or analyst.",
"End on a clear ask with named owner and date."
],
"avoid": [
"Buried leads.",
"Symmetrical 'on one hand / on the other' framing without a verdict.",
"Information for its own sake — every chart should advance the argument.",
"Passive endings without a clear ask."
],
"samplePhrases": [
"Adopting our runtime cuts inference latency 8× while preserving accuracy.",
"The most common objection — 'we'll be locked in' — is addressed by our open OPF spec.",
"We're asking for a $30M Series B to ship into the enterprise tier."
],
"recommendedNarratives": [
"pitch-deck",
"venture-pitch",
"early-startup-pitch",
"persuasive-sales",
"project-proposal"
],
"tags": [
"sales",
"pitch",
"argumentative"
]
}
},
"colorSchemes": {
"deep-purple": {
"name": "Deep Purple",
"accent1": "#6A1B9A",
"accent2": "#7B1FA2",
"accent3": "#8E24AA",
"accent4": "#9C27B0",
"accent5": "#AB47BC",
"accent6": "#4A148C",
"dark1": "#000000",
"dark2": "#2B0B3E",
"followedHyperlink": "#6A1B9A",
"hyperlink": "#4A148C",
"light1": "#FFFFFF",
"light2": "#F8F2FC",
"summary": "Purple-led palette for innovation and premium positioning.",
"description": "A focused purple palette for decks that need to feel creative, distinctive, and premium.",
"tags": [
"innovative",
"creative",
"premium",
"distinctive",
"modern"
]
}
},
"fontSchemes": {
"poppins": {
"name": "Poppins",
"app": "google-slides",
"languageFamily": "latin",
"languages": [],
"major": "Poppins",
"minor": "Poppins",
"textSample": "Clean and readable",
"type": "sans-serif",
"description": "Poppins is a sans serif OPF font scheme for Latin presentations, using Poppins for both headings and body text."
}
},
"layouts": {
"image-beside": {
"name": "Image beside",
"summary": "A picture or video beside text.",
"tags": [
"Visuals"
],
"direction": "column",
"regions": [
{
"name": "title"
},
{
"direction": "row",
"regions": [
{
"name": "media",
"accepts": [
"image",
"video"
],
"role": "media",
"flow": "none",
"anchor": "middle"
},
{
"name": "body",
"accepts": [
"text",
"list",
"metric",
"quote",
"group"
],
"role": "primary",
"flow": "auto",
"anchor": "middle"
}
]
}
],
"description": "Explain a visual alongside its supporting text. Use the text to direct attention to the meaningful parts of the image.",
"preview": {
"vectorSrc": "https://www.pptx.gallery/layout-previews/image-beside.svg"
},
"design": {
"imageFit": "contain"
}
}
}
}
}
}Open in visual editorOpen in Inspector
Load this config in the gallery's visual editor, or in the Inspector at pptx.dev.
Use Case
Use immediately after the problem slide to show how the answer works.
When to Use
In sales, product, fundraising, and transformation decks.
When to Avoid
Avoid when the audience needs detailed architecture instead of positioning.
Block Structure
image-beside
One system, three outcomes
Capability, workflow, and measurable business value.
- -Automate the bottleneck
- -Improve handoff quality
- -Measure the result
Best Practices
1
Keep feature language tied to outcomes.
2
Do not list every capability.
3
Make the differentiator visible in the headline or first supporting point.
Playground deep link: config=blocks:solution-overview