@openpresentation/opf 0.1.0

package/dist/spec/catalogs/narratives/marketing-strategy.json

@@ -0,0 +1,111 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "marketing-strategy",
+  "name": "Marketing Strategy",
+  "summary": "Comprehensive go-to-market strategy arc structured around the 4Ps. Use for category launches, annual marketing plans, and any deck where the audience needs to see customer, market, competition, and tactics in one coherent picture.",
+  "audienceFit": [
+    "marketing-leaders",
+    "executives",
+    "cross-functional-partners"
+  ],
+  "durationRange": {
+    "minMinutes": 30,
+    "maxMinutes": 60
+  },
+  "tags": [
+    "go-to-market",
+    "marketing",
+    "strategy",
+    "planning"
+  ],
+  "beats": [
+    {
+      "id": "introduction",
+      "name": "Introduction",
+      "description": "Open by establishing the product or service this strategy is for, and what window of time it covers. One slide that tells the audience exactly which world they're being asked to weigh in on.",
+      "instructions": "Establish product/service specifics",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "objective",
+      "name": "Objective",
+      "description": "State the marketing goals in measurable terms: revenue, pipeline, awareness, share. Two or three goals, ranked. Goals without ranking get equal energy and equal mediocrity.",
+      "instructions": "Share marketing goals",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "customer",
+      "name": "Customer",
+      "description": "Detail the target audience. Segments, jobs-to-be-done, decision criteria, where they live in the buying cycle. Specificity here is the foundation everything else stands on.",
+      "instructions": "Detail target audience",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "market",
+      "name": "Market",
+      "description": "Describe the market landscape: size, growth, segments, behavioral trends. Use external data for credibility and your own research for nuance. Show how the market is changing, not just how big it is.",
+      "instructions": "Discuss market landscape",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "competition",
+      "name": "Competition",
+      "description": "Map the competitive set honestly. Direct, indirect, and substitutes. A 2x2 or feature-comparison framework helps; what matters is that the audience trusts your read of the field.",
+      "instructions": "Analyze competitive environment",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "strategy",
+      "name": "Strategy",
+      "description": "Articulate the marketing approach in one sentence and a single supporting frame. Positioning, primary motion, where you choose to play and not play. Clarity here is what makes the tactics that follow coherent.",
+      "instructions": "Elaborate marketing approach",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "product",
+      "name": "Product",
+      "description": "Highlight the unique value the product brings to the strategy. Lead with the customer outcome; tie it directly back to the customer beat. Avoid feature soup.",
+      "instructions": "Highlight unique value",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "price",
+      "name": "Price",
+      "description": "Justify pricing and packaging. Show the logic — cost-plus, value-based, competitor-anchored — and the levers you'll use over the period. Price decisions are strategy decisions.",
+      "instructions": "Justify pricing strategy",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "place",
+      "name": "Place",
+      "description": "Describe distribution channels and the role each plays. Direct, partner, marketplace, retail. Channel mix is often where strategies quietly succeed or fail.",
+      "instructions": "Discuss distribution channels",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "promotion",
+      "name": "Promotion",
+      "description": "Reveal the campaign and content tactics that bring the strategy to market. Pair each tactic with the audience and metric it serves. Avoid listing channels for their own sake.",
+      "instructions": "Reveal promotional tactics",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "summary",
+      "name": "Summary",
+      "description": "Recap the strategy in a single page: customer, position, motion, expected outcome. End with the decision or commitment you need from the audience.",
+      "layoutHint": "title-left",
+      "instructions": "Recap key points",
+      "slideType": "text"
+    }
+  ]
+}

package/dist/spec/catalogs/narratives/performance-improvement-plan.json

@@ -0,0 +1,87 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "performance-improvement-plan",
+  "name": "Performance Improvement Plan",
+  "summary": "Structured PIP arc that helps a struggling employee see expectations clearly, understand the gap, and walk into a credible improvement path. Designed to be respectful, specific, and outcome-focused — not punitive.",
+  "audienceFit": [
+    "employee",
+    "manager",
+    "hr-partner"
+  ],
+  "durationRange": {
+    "minMinutes": 30,
+    "maxMinutes": 60
+  },
+  "tags": [
+    "workforce",
+    "hr",
+    "performance",
+    "manager"
+  ],
+  "beats": [
+    {
+      "id": "introduction",
+      "name": "Introduction",
+      "description": "Begin respectfully and set a constructive tone. Be clear about what this conversation is and isn't. The opening shouldn't catastrophize or sugarcoat — clarity is kinder than either.",
+      "instructions": "Begin respectfully and positively",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "set-expectations",
+      "name": "Set Expectations",
+      "description": "Detail the level of performance expected in the role. Specific behaviors, deliverables, and standards. Expectations the employee can't quote back are expectations they can't meet.",
+      "instructions": "Detail desired performance",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "identify-problems",
+      "name": "Identify Problems",
+      "description": "Name the gap between expected and observed performance. Use specific examples and dates rather than impressions. Avoid characterizing the person; focus on the work product and the impact.",
+      "instructions": "Highlight struggles and weaknesses",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "possible-solutions",
+      "name": "Possible Solutions",
+      "description": "Suggest improvement strategies tailored to the gaps named above. Behavior changes, structural changes, support structures. Frame them as paths the employee can choose, not orders to follow.",
+      "instructions": "Suggest improvement strategies",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "offer-resources",
+      "name": "Offer Resources",
+      "description": "Make explicit what tools, coaching, training, or peer support is available. Resources demonstrate that the organization is investing in the outcome, not setting the employee up to fail.",
+      "instructions": "Propose help and tools",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "motivate-change",
+      "name": "Motivate Change",
+      "description": "Connect improvement to what the employee values: their growth, their team, their career. Inspire action without minimizing the seriousness of the situation.",
+      "instructions": "Inspire improvement action",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "follow-up",
+      "name": "Follow Up",
+      "description": "Schedule the check-ins. Frequency, format, criteria for progress. Predictable follow-up turns a PIP from a threat into a plan.",
+      "instructions": "Schedule progress check-ins",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "conclusion",
+      "name": "Conclusion",
+      "description": "Close with confidence in the path forward and a clear restatement of what success looks like. End the meeting having both raised the bar and reaffirmed the relationship.",
+      "layoutHint": "title-left",
+      "instructions": "Encourage and remind success",
+      "slideType": "text"
+    }
+  ]
+}

package/dist/spec/catalogs/narratives/performance-review.json

@@ -0,0 +1,111 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "performance-review",
+  "name": "Performance Review",
+  "summary": "Analytical review of individual, team, or company performance grounded in metrics. Walks through results, key drivers, wins, challenges, and the adjustments that will shape the next period.",
+  "audienceFit": [
+    "leadership",
+    "managers",
+    "teams"
+  ],
+  "durationRange": {
+    "minMinutes": 20,
+    "maxMinutes": 60
+  },
+  "tags": [
+    "data-driven",
+    "review",
+    "operations",
+    "metrics"
+  ],
+  "beats": [
+    {
+      "id": "briefing",
+      "name": "Briefing",
+      "description": "Frame what this review covers: the period, the unit, the standard you're measuring against. One slide that lets the audience know exactly what they're being asked to evaluate.",
+      "layoutHint": "title-center",
+      "instructions": "Outline presentation objective",
+      "slideType": "text"
+    },
+    {
+      "id": "results",
+      "name": "Results",
+      "description": "Lead with the headline result. On track, ahead, or behind, and by how much. Resist softening — clear numbers up front earn credibility for the analysis that follows.",
+      "instructions": "Summarize performance findings",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "key-metrics",
+      "name": "Key Metrics",
+      "description": "Walk through the pivotal indicators. One chart per metric, clear comparison period, target or benchmark visible on the same frame. Help the audience see the data the way you do.",
+      "instructions": "Review pivotal indicators",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "team-performance",
+      "name": "Team Performance",
+      "description": "Examine collective achievements and how the team contributed. Avoid generic praise; cite specific moves and the people behind them where the audience would expect it.",
+      "instructions": "Examine collective achievements",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "highlight",
+      "name": "Highlight",
+      "description": "Spotlight one standout contribution that defined the period. A landmark deal, a launch, a fix, a hire. One vivid example sticks longer than a list of accomplishments.",
+      "instructions": "Show key contribution",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "analysis",
+      "name": "Analysis",
+      "description": "Dig under the metrics. What drove the numbers, what held them back, what's signal versus noise. Analysis is where the audience learns whether you actually understand the system you're reporting on.",
+      "instructions": "Uncover data insights",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "success",
+      "name": "Success",
+      "description": "Reinforce the past triumphs that show the system works. Briefly — the audience came for what's next, not a victory lap. Wins earn permission for the harder slides ahead.",
+      "instructions": "Reinforce past triumphs",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "challenges",
+      "name": "Challenges",
+      "description": "Name the obstacles encountered honestly. What didn't move, what regressed, what the team is still wrestling with. Understated challenges read as missed signal, not modesty.",
+      "instructions": "Highlight encountered obstacles",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "adjustments",
+      "name": "Adjustments",
+      "description": "Identify the changes you're making in response. New tactics, reallocations, sunsets. Each adjustment should map to a challenge above — adjustments without diagnosis feel arbitrary.",
+      "instructions": "Identify necessary changes",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "strategy-evolution",
+      "name": "Strategy Evolution",
+      "description": "Show how the strategy itself evolves heading into the next period. Refinements, sharpened bets, dropped initiatives. The audience should see continuity as well as change.",
+      "instructions": "Plan for improvement",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "discussion",
+      "name": "Discussion",
+      "description": "Open the floor with two or three specific prompts. End the review actively — questions you want answered, decisions you want made — so the meeting yields more than the deck.",
+      "layoutHint": "title-left",
+      "instructions": "Promote active discourse",
+      "slideType": "text"
+    }
+  ]
+}

package/dist/spec/catalogs/narratives/persuade.json

@@ -0,0 +1,94 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "persuade",
+  "name": "Persuade",
+  "summary": "Argument-driven keynote arc inspired by Ken Robinson: grip the audience, challenge the status quo, define the problem, anchor it in story and statistic, deliver a major revelation, propose change, and end on a question that stays with them.",
+  "audienceFit": [
+    "general-audience",
+    "policymakers",
+    "industry-peers"
+  ],
+  "durationRange": {
+    "minMinutes": 15,
+    "maxMinutes": 30
+  },
+  "tags": [
+    "keynote",
+    "persuasive",
+    "advocacy",
+    "talk"
+  ],
+  "beats": [
+    {
+      "id": "gripping-introduction",
+      "name": "Gripping Introduction",
+      "description": "Open with a moment, image, or claim the audience can't easily look away from. The first sixty seconds buy you the next twenty minutes — spend them on something specific and emotionally charged, not on housekeeping.",
+      "instructions": "Draw in the audience with a compelling opener",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "challenge-status-quo",
+      "name": "Challenge the Status Quo",
+      "description": "Call out the system, norm, or assumption that needs examination. Be precise about what you're disagreeing with so the rest of the talk can be specific in response. Avoid strawmen — name the strongest version of the view you're contesting."
+    },
+    {
+      "id": "present-problem",
+      "name": "Present the Problem",
+      "description": "Define the issue the audience needs to care about. Concrete, scoped, attributable. The clearer the problem, the more credible the eventual solution."
+    },
+    {
+      "id": "personal-story",
+      "name": "Personal Story",
+      "description": "Anchor the issue in a specific person, place, or moment. Story is what gets the argument past the audience's defenses. Pick a story that personalizes the data without overstating it.",
+      "instructions": "Share significant stories to illuminate the issue",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "statistic-shock",
+      "name": "Statistic Shock",
+      "description": "Drop in a single statistic that recasts the scale of the problem. One number, presented well, lands harder than a dashboard. Cite the source so the audience can repeat it with confidence.",
+      "instructions": "Use impactful stats to highlight the gravity of the issue",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "historical-context",
+      "name": "Historical Context",
+      "description": "Show how the issue evolved. Why it has the shape it does today, what was tried, what was missed. Historical context turns 'this is broken' into 'this stayed broken for these reasons.'",
+      "instructions": "Show the evolution or history of the issue",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "weave-narrative",
+      "name": "Weave a Narrative",
+      "description": "Connect the threads — story, statistic, history — into a single argument. The audience should feel the case clicking together. This is the slide where rhetoric becomes architecture."
+    },
+    {
+      "id": "major-revelation",
+      "name": "Major Revelation",
+      "description": "Deliver the surprising or significant turn. The fact, finding, or reframing the rest of the talk has been earning. The revelation should redirect, not merely confirm.",
+      "instructions": "Deliver a surprising or significant discovery",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "propose-solution",
+      "name": "Propose Solution",
+      "description": "Advocate for the change you want. Concrete enough to be acted on, broad enough to inspire. Pair the solution with the smallest credible first step.",
+      "instructions": "Advocate for change or propose an actionable solution",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "final-question",
+      "name": "Final Question",
+      "description": "Close on a question rather than a summary. The right closing question follows the audience out of the room and into their conversations afterward.",
+      "layoutHint": "title-left",
+      "instructions": "Finish with a thought-provoking question to stimulate audience thinking",
+      "slideType": "text"
+    }
+  ]
+}

package/dist/spec/catalogs/narratives/persuasive-sales.json

@@ -0,0 +1,87 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "persuasive-sales",
+  "name": "Persuasive Sales",
+  "summary": "Top-of-funnel sales arc that creates awareness and alignment with a prospective customer. Anchored in a market change, leading to your unique capabilities, supported by proof, ending with a clear call to action.",
+  "audienceFit": [
+    "prospects",
+    "customers",
+    "buyers"
+  ],
+  "durationRange": {
+    "minMinutes": 15,
+    "maxMinutes": 45
+  },
+  "tags": [
+    "sales",
+    "go-to-market",
+    "outbound",
+    "discovery"
+  ],
+  "beats": [
+    {
+      "id": "intro",
+      "name": "Introduction",
+      "description": "Open with a brief framing of who you are and why this conversation is worth the prospect's next thirty minutes. Keep credentials short; the audience cares about their problem, not your résumé.",
+      "instructions": "Name & logo",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "big-change",
+      "name": "Big Change",
+      "description": "Name the market shift the prospect's industry is living through. Make it concrete, recent, and undeniable. The change — not the product — is the reason they should care.",
+      "instructions": "Highlight market shift",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "response-to-change",
+      "name": "Winners and Losers",
+      "description": "Show how the change is creating winners and losers in the prospect's space. Use named examples where you can. The goal is for the prospect to wonder which side they'll end up on.",
+      "instructions": "Show winners & losers",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "benefits",
+      "name": "Benefits",
+      "description": "Paint the outcome a winner experiences: a vivid picture of the prospect's life on the other side of the change. Lead with what changes for them, not with what your product does.",
+      "instructions": "Describe benefits, paint a vivid picture",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "capabilities",
+      "name": "Capabilities",
+      "description": "Reveal the unique capabilities that make those outcomes possible. Frame them as the 'magic gifts' the prospect needs to win the new game. Highlight what's structurally different from the alternatives.",
+      "instructions": "Present unique features as 'magic gifts' to the customer",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "evidence",
+      "name": "Evidence",
+      "description": "Share customer testimonials, case studies, and measurable outcomes from organizations like the prospect's. Pick evidence that maps to the benefits you promised, not generic logos.",
+      "instructions": "Share testimonials",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "call-to-action",
+      "name": "Call to Action",
+      "description": "Ask for the next step in the sales process. Be specific: a pilot, a workshop, a follow-on conversation with a named stakeholder. Make the smallest credible commitment that keeps momentum.",
+      "layoutHint": "title-left",
+      "instructions": "Encourage decision-making",
+      "slideType": "text"
+    },
+    {
+      "id": "close",
+      "name": "Close",
+      "description": "Close with a final image and contact path. Leave the prospect with one line about why they're better off acting now than later, and clear instructions for how to engage.",
+      "layoutHint": "title-left",
+      "instructions": "Logo & contact info",
+      "slideType": "text"
+    }
+  ]
+}

package/dist/spec/catalogs/narratives/pitch-deck.json

@@ -0,0 +1,107 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "pitch-deck",
+  "name": "Startup Pitch Deck",
+  "summary": "The canonical investor-pitch arc, drawn from Sequoia and Y Combinator's templates. Optimized for 10–20 minute meetings with VCs and angels. Each beat answers the question an investor will ask next.",
+  "audienceFit": [
+    "investors",
+    "venture-capitalists",
+    "angels",
+    "advisors"
+  ],
+  "durationRange": {
+    "minMinutes": 10,
+    "maxMinutes": 20
+  },
+  "tags": [
+    "startup",
+    "fundraising",
+    "pitch",
+    "investor"
+  ],
+  "beats": [
+    {
+      "id": "opening",
+      "name": "Opening",
+      "description": "Open with the company name, logo, and a one-line tagline that doubles as a positioning statement. Set the visual tone for the deck. Keep it confident and uncluttered — this is the cover.",
+      "layoutHint": "title-left"
+    },
+    {
+      "id": "purpose",
+      "name": "Company Purpose",
+      "description": "State in a single sentence what the company does and why it exists. Should be immediately understandable without industry jargon. Often doubles as the answer to 'so what do you do?'"
+    },
+    {
+      "id": "problem",
+      "name": "Problem",
+      "description": "Describe the pain point you solve. Make it concrete with a specific user or customer scenario. The more visceral and recognizable the problem, the stronger the rest of the pitch lands."
+    },
+    {
+      "id": "why-now",
+      "name": "Why Now",
+      "description": "Explain the technological, regulatory, behavioral, or market shift that makes this opportunity possible today and impossible five years ago. Investors want to know why this is a window, not just an idea."
+    },
+    {
+      "id": "market",
+      "name": "Market Size",
+      "description": "Size the opportunity. Top-down (TAM/SAM/SOM) or bottom-up (units × price). Show how big the prize is if you win, and why this market is attractive to a venture-scale outcome."
+    },
+    {
+      "id": "competition",
+      "name": "Competition",
+      "description": "Map the competitive landscape honestly. A 2x2 matrix or feature-comparison grid is fine; what matters is showing you understand the alternatives and where you uniquely fit. Naïve 'no competition' answers tank credibility."
+    },
+    {
+      "id": "solution",
+      "name": "Solution",
+      "description": "Show how you solve the problem and why your approach is uniquely better. Lead with the outcome for the customer, then show the mechanism. This is where you connect problem to product."
+    },
+    {
+      "id": "product",
+      "name": "Product",
+      "description": "Give the product its own moment. Screenshots or a key visual that captures what users actually see and feel. Pick one strong frame over a montage of small ones."
+    },
+    {
+      "id": "demo",
+      "name": "Demo",
+      "description": "Walk through the core user flow end-to-end. Show real software solving a real problem in a real workflow — not a marketing reel. If a live demo is too risky, use a tightly edited recording with narration."
+    },
+    {
+      "id": "traction",
+      "name": "Traction",
+      "description": "Prove momentum with one credible headline metric. Revenue, users, growth rate, customer logos — whatever best shows the business is working. One strong chart beats five vanity numbers."
+    },
+    {
+      "id": "growth",
+      "name": "Growth Drivers",
+      "description": "Show how the headline metric got there and where it's going. Cohorts, retention, expansion, channel mix — whatever explains the engine behind the number. Investors back the trajectory, not the snapshot."
+    },
+    {
+      "id": "business-model",
+      "name": "Business Model",
+      "description": "Explain how the company makes money. Pricing, unit economics, sales motion, payback period. Should answer: what does it cost to acquire a customer, and what do they pay you?"
+    },
+    {
+      "id": "team",
+      "name": "Team",
+      "description": "Establish why this team uniquely wins this market. Founder backgrounds, relevant experience, prior outcomes, key advisors. Investors back people first; make the case."
+    },
+    {
+      "id": "financials",
+      "name": "Financials",
+      "description": "Show the financial picture: historical revenue, burn, runway, and forward projection. Be conservative-but-credible — investors will discount aggressive numbers and reward defensible ones."
+    },
+    {
+      "id": "ask",
+      "name": "The Ask",
+      "description": "State the round size, intended use of funds, and what milestones the capital takes you to. Be specific — investors should leave knowing exactly what you want and what they get.",
+      "layoutHint": "title-left"
+    },
+    {
+      "id": "closing",
+      "name": "Closing",
+      "description": "Close on a strong final image: logo, contact info, and the one line you most want the investor to remember. Leave space for the conversation that follows.",
+      "layoutHint": "title-left"
+    }
+  ]
+}

package/dist/spec/catalogs/narratives/problem-solution.json

@@ -0,0 +1,61 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "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"
+  ],
+  "durationRange": {
+    "minMinutes": 5,
+    "maxMinutes": 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.",
+      "layoutHint": "title-center"
+    },
+    {
+      "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.",
+      "layoutHint": "title-left"
+    }
+  ]
+}