Strategy Block
Value Proposition
A value statement block that aligns audience need, promise, proof, and differentiation.
value-proposition1 slidebalanced density
Value
Promise, proof, payoff
Organize value around the customer job rather than internal feature names.
01
Need
02
Promise
03
Proof
04
Payoff
OPF Config
blocks:value-propositionOPF JSON
{
"$schema": "https://openpresentation.org/schema/opf/v1",
"name": "Value Proposition",
"description": "A value statement block that aligns audience need, promise, proof, and differentiation.",
"tone": "persuasive",
"narrative": "sparkline",
"takeaway": "Translate a solution into a compact customer value proposition.",
"tags": [
"content-block",
"gallery:blocks/value-proposition"
],
"design": {
"colorScheme": "steel-blue",
"fontScheme": "open-sans",
"background": {
"type": "pattern",
"pattern": {
"preset": "openDmnd",
"foregroundColor": "#e2e8f0",
"backgroundColor": "#faf8f5"
}
}
},
"slides": [
{
"id": "value-proposition",
"layout": "pillars",
"title": "Promise, proof, payoff",
"subtitle": "A value proposition organized around the customer job.",
"blocks": [
{
"text": "Need"
},
{
"text": "Promise"
},
{
"text": "Proof"
},
{
"text": "Payoff"
}
]
}
],
"catalogs": {
"default": {
"source": "https://www.pptx.gallery",
"narratives": {
"sparkline": {
"name": "Sparkline",
"summary": "A tight comparison arc showing the transformation from an inferior state to a superior one, anchored by contrast.",
"description": "A tight comparison arc that shows the move from an inferior state to a superior one, anchored by contrast. Make the painful before state vivid, reveal the product, decision, or event that changes the trajectory, present the new reality in concrete terms, then prove it with data or testimonial. The tone is contrastive: it makes the gap between old and new viscerally clear. Best for product demos, case study summaries, ROI presentations, and before-and-after technology comparisons; typical decks run 4-6 slides.",
"audienceFit": [
"prospective-buyers",
"skeptical-stakeholders",
"evaluation-committees"
],
"duration": {
"min": 3,
"max": 15
},
"tags": [
"contrast",
"transformation",
"product",
"roi"
],
"beats": [
{
"id": "before-state",
"name": "Before State",
"description": "Make the current pain or limitation vivid with numbers, stories, or visuals that make the problem real.",
"instructions": "Make the current pain or limitation vivid.",
"type": "text",
"layout": "two-column"
},
{
"id": "contrast-moment",
"name": "Contrast Moment",
"description": "Introduce the change agent, product, or decision that shifts the trajectory.",
"instructions": "Introduce the decision, product, or event that changes the trajectory.",
"type": "text",
"layout": "statement"
},
{
"id": "after-state",
"name": "After State",
"description": "Show the improved reality. Make it concrete and specific instead of relying on vague benefit language.",
"instructions": "Show the new reality created by the change.",
"type": "text",
"layout": "text"
},
{
"id": "proof",
"name": "Proof",
"description": "Validate the after state with metrics, testimonials, or third-party evidence.",
"instructions": "Validate the change with evidence.",
"type": "metric",
"layout": "metrics"
}
]
}
},
"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": {
"steel-blue": {
"name": "Steel Blue",
"accent1": "#4A66AC",
"accent2": "#629DD1",
"accent3": "#297FD5",
"accent4": "#7F8FA9",
"accent5": "#5AA2AE",
"accent6": "#9D90A0",
"dark1": "#000000",
"dark2": "#182238",
"followedHyperlink": "#3EBBF0",
"hyperlink": "#9454C3",
"light1": "#FFFFFF",
"light2": "#EAEDF6",
"summary": "Cool steel blues for credible, data-forward presentations.",
"description": "A steel-blue palette that combines credibility, precision, and calm. Useful for analysis-heavy decks.",
"tags": [
"calm",
"precise",
"measured",
"professional",
"analytical"
]
}
},
"fontSchemes": {
"open-sans": {
"name": "Open Sans",
"app": "google-slides",
"languageFamily": "latin",
"languages": [],
"major": "Open Sans",
"minor": "Open Sans",
"textSample": "Modern and sleek",
"type": "sans-serif",
"description": "Open Sans is a sans serif OPF font scheme for Latin presentations, using Open Sans for both headings and body text."
}
},
"layouts": {
"pillars": {
"name": "Pillars",
"summary": "Related ideas arranged in equal columns.",
"tags": [
"Groups of items"
],
"design": {
"contentBox": false,
"listBullet": "none"
},
"direction": "column",
"regions": [
{
"name": "title"
},
{
"name": "pillars",
"accepts": [
"text",
"list",
"metric",
"image",
"group"
],
"role": "primary",
"flow": "grid"
}
],
"description": "Show the main themes or principles behind an idea. Give each item a short heading and a comparable amount of detail.",
"preview": {
"vectorSrc": "https://www.pptx.gallery/layout-previews/pillars.svg"
}
}
}
}
}
}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 when a deck must translate product features into customer value.
When to Use
For sales decks, launch narratives, website-to-deck translation, and partner pitches.
When to Avoid
Avoid if you need a feature matrix or technical spec instead.
Block Structure
pillars
Promise, proof, payoff
A value proposition organized around the customer job.
- -Need
- -Promise
- -Proof
- -Payoff
Best Practices
1
Use customer language.
2
Keep each value point short.
3
Avoid internal product taxonomy.
Playground deep link: config=blocks:value-proposition