Guide2026-04-137 min

How to Write Effective Briefs for AI Slide Generation

The quality of your slides depends on your brief. Rules, examples, and templates for KPI dashboards, comparisons, timelines, SWOT, and data tables.

The quality of your SlideForge output depends almost entirely on the quality of your brief. A good brief produces a polished slide in one shot. A vague brief wastes iterations. This guide covers what makes a brief work, with examples for every slide type.

The #1 mistake: being vague

Bad brief: “Make a slide about our revenue.”

Good brief: “KPI dashboard: Revenue $12.4M (+18% YoY), New Clients 847 (+23%), Gross Margin 71% (-2pp), NPS 4.6 (+0.3). Kicker: Q1 2026 REVIEW.”

The bad brief gives the engine nothing to work with — no numbers, no context, no structure. The good brief has specific data, trends, and framing. The engine can render this as a KPI dashboard template in under a second.

Rule 1: Include actual data

Never write “include relevant metrics.” The engine doesn't know your metrics. Always provide the actual numbers, even if they're approximate.

VagueSpecific
“Revenue trends”“Revenue $8.5M Q1, $9.2M Q2, $10.1M Q3, $12.4M Q4”
“Team structure”“Org chart: CEO → CTO (Engineering 12, Data 4), CFO (Finance 3), CMO (Marketing 6)”
“Competitive analysis”“Feature comparison: Us vs Competitor A vs B. Rows: API, MCP, .pptx output, price. We win on API+MCP+price.”

Rule 2: Name the slide type

SlideForge has 50 templates and 24 design system components. If you know what layout you want, say it. The engine matches your brief to the right template automatically, but naming the type helps.

  • “KPI dashboard with 4 metrics”
  • “SWOT analysis for Tesla”
  • “Timeline: 5 milestones from Q1 to Q4”
  • “2x2 matrix comparing build vs buy on cost and speed axes”
  • “Waterfall chart: revenue bridge from $10M to $12.4M”
  • “Funnel: 1000 leads → 200 MQLs → 50 demos → 12 closes”

Rule 3: Describe the visual structure, not just the content

For complex slides, describe how you want the information arranged — not just what information to include.

OK: “Compare three cloud providers on 5 dimensions.”

Better: “3-column comparison table. Columns: AWS, Azure, GCP. Rows: Compute, Storage, AI/ML, Pricing, Enterprise Support. Use checkmarks and X marks. Highlight Azure column as recommended.”

Rule 4: Specify chrome

Chrome = the frame around your content. If you need specific titles, footers, or page numbers, include them in the brief or pass them as the chrome parameter.

{
  "brief": "4 KPI metrics: Revenue $12.4M, Clients 847, Margin 71%, NPS 4.6",
  "chrome": {
    "title": "Q1 2026 Performance",
    "kicker": "QUARTERLY REVIEW",
    "footer": "Confidential",
    "page_number": 3,
    "source": "Internal finance dashboard"
  }
}

Or include it inline: “Title: Q1 Performance. Kicker: QUARTERLY REVIEW. Page 3. Footer: Confidential.”

Rule 5: Use iteration for refinement, not generation

Don't try to get a perfect slide in one brief. Get the structure right first, then iterate on details.

  1. Generate: “2x2 matrix comparing Build vs Buy. Axes: Implementation Cost (low→high) vs Time to Market (slow→fast). Build = high cost, slow. Buy = low cost, fast. SaaS = medium cost, fast.”
  2. Iterate: “Make the Build quadrant header larger. Add a green checkmark icon next to Buy. Change the axis labels to 14pt.”
  3. Iterate: “Add a callout arrow pointing to SaaS with text: Recommended approach.”

Iteration is $0.10 vs $0.20 for a new generation. And the feedback should be code-level specific: font sizes, colors, positions — not “make it look better.”

Brief templates by slide type

KPI Dashboard

"KPI dashboard: [Metric1] [Value] ([Trend]), [Metric2] [Value] ([Trend]), ...
 Kicker: [SECTION]. Takeaway: [insight]."

Comparison / Feature Table

"Feature comparison table. Columns: [Option A], [Option B], [Option C].
 Rows: [Feature1], [Feature2], [Feature3]. [Option B] is recommended.
 Use checkmarks for supported, X for unsupported."

Timeline

"Horizontal timeline with [N] milestones:
 [Date1]: [Event1], [Date2]: [Event2], [Date3]: [Event3].
 Highlight [Date2] as current."

SWOT

"SWOT analysis for [Company/Product].
 Strengths: [1], [2]. Weaknesses: [1], [2].
 Opportunities: [1], [2]. Threats: [1], [2]."

Data Table

"Data table with [N] rows and [M] columns.
 Headers: [Col1], [Col2], [Col3].
 Row 1: [val], [val], [val]. Row 2: ...
 Highlight row 3 (best performer)."

Common mistakes

  • “Make it look professional” — every slide already uses consulting-grade design. This instruction adds nothing.
  • “Use blue colors” — set a theme instead (theme_id: "consulting_blue"). Themes handle all colors consistently.
  • “Add some icons” — be specific: “Add a chart-bar icon next to Revenue, a users icon next to Clients.”
  • Walls of text as brief — the engine works best with structured data, not paragraphs. Use bullet points, not prose.

Get started

Try these patterns in the Playground, or connect via MCP and ask your agent to generate slides. Browse 50 templates to see what slide types are available.

Try SlideForge free

$3 credit, no card required. Generate your first slide in under a minute.