Blog

Gamma blog: AI decks & slide craft

Gamma editorialLong-tail guides

The blog is Gamma's long-tail engine. Canonical topical guides live under /learn hubs. Blog posts go narrower: stage, industry, persona, objection, or migration scenario, the searches that do not deserve their own money page but still need a serious answer with a reusable framework.

Each post should teach a decision, include a worked example with specifics, and link up to its parent hub or spoke plus across to a product page. We do not publish thin keyword pages. If a post cannot change what you put on a slide this week, it should not ship.

Prompt → outline → slides

1. Prompt

Audience, goal, length, proof you already have.

2. Outline

  • • Opening claim
  • • Proof beats
  • • Ask / next step

3. Slides

Long-tails climb into hubs; hubs support money pages, not the other way around.
Diagram of long-tail blog posts feeding learn hubs and money pages
Read a post for the scenario; open the hub when you need the full craft system.

How to use the blog

Arrive with a constraint: “Series A checklist,” “churn in a QBR,” “ChatGPT outline into a real deck.” Skim the answer block, steal the framework, then draft in Gamma with your facts. Do not collect posts the way people collect templates, finish one scenario end-to-end, including a forced edit.

When a post compares tools or migrations, cross-check claims against /method. Undated “best AI” language without a job and a rubric is noise. Prefer posts that name who should pick the other tool.

Which tool for which job

Need native PowerPoint editing every day?

Yes → Plus AI / Copilot · No → continue

Need rigid brand kits across a large team?

Yes → Beautiful.ai / enterprise kits · No → continue

Need outline-first AI drafting + present link?

Yes → Gamma

Pick posts by failure mode: stage mismatch, objection handling, migration, or generic AI output.
Decision map for choosing a Gamma blog post by scenario
Scenario first. Cluster labels help, but the meeting you have this week matters more.

Featured scenarios

Start here if you want high-leverage reads. Each blurb states the decision the post helps you make, then open the full article for the framework and worked details.

Weak slide → strong slide

Before

  • • Overview
  • • Features
  • • Next steps???

After

  • • Cost of status quo
  • • Wedge in one claim
  • • Proof + decision ask
Most posts encode the same habit: rewrite topic lists into claim sequences matched to the room.
Before and after slide rewrite pattern taught across blog posts
If you only take one habit from the blog, take claim titles with proprietary proof.

Clusters you will see

  • Pitch & fundraising — stage checklists, MRR slides, slide counts for short pitches.
  • Sales, SaaS examples, security objections, pricing-to-deck, leave-behind vs live.
  • Product & exec, QBR churn, PM review examples, exec roadmap framing.
  • AI & migrations, prompts, ChatGPT handoffs, Copilot limits, Beautiful.ai/Tome paths.
  • Education & workflows — class talks, thesis outlines, notes/docs to decks.
  • Design fixes, generic AI slides and brand color discipline.

Fundraising narrative arc

ProblemInsightSolutionTractionAsk

Tension early. Proof before the ask. Titles should skim as a story.

Pitch posts still obey narrative arcs, they just zoom into stage-specific failure modes.
Pitch arc visual referenced by fundraising blog posts
Long-tail pitch posts should still skim as a story when you read titles only.

All posts

Full index of live long-tails. Descriptions come from the registry; featured blurbs above add editorial guidance for the highest-leverage scenarios. New posts must clear the same quality gate as spokes: no padding, one framework, one worked example.

What not to expect

This index is not a news feed. It is not affiliate roundups without a method. It is not a second homepage. If you need the product path, open the AI presentation maker. If you need craft systems, open learn hubs. If you need shapes, open examples.

Time-to-usable-deck

Blank PPT path

Outline in docs → design fight → rebuild → 3–8 hours

Outline-first AI path

Prompt → edit outline → generate → polish → minutes to first usable draft

A useful post shortens time-to-usable-deck for one scenario, measure it that way.
Sales journey visual used by sales-cluster blog posts
Sales long-tails should still map to Discovery → Fit → Proof → Next step.

Frameworks, worked rules, and cuts

The blog is Gamma's long-tail engine for scenario-specific decisions that do not deserve their own money page. Canonical craft systems live under learn hubs. Posts go narrower on stage, industry, persona, objection, or migration. If a post cannot change what you put on a slide this week, it should not ship. Prefer posts that name a constraint, a reusable framework, and a worked example you can recreate the same day.

Original framework for reading: Constraint, Framework, Draft. Arrive with a constraint such as Series A checklist, churn in a QBR, or ChatGPT outline into a real deck. Steal the framework. Draft in Gamma with your facts. Do not collect posts the way people collect templates. Finish one scenario end-to-end including a forced edit before you open a second long-tail.

Featured scenarios cover stage-specific pitch checklists, discovery-led SaaS sales shapes, churn presentation in QBRs, ChatGPT-to-Gamma handoffs, meeting notes to client decks, and rewrite passes for generic AI slides. Each featured blurb states the decision the post helps you make before you open the full article so you can skip reads that do not match this week's room.

Clusters you will see include pitch and fundraising, sales, product and exec, AI and migrations, education and workflows, and design fixes. When a post compares tools or migrations, cross-check claims against the public method page. Undated best-AI language without a job and a rubric is noise; dated job-based guidance is the bar.

Worked use: an AE facing a security objection opens the enterprise security objection post, steals the validation-step pattern, pastes buyer language into Gamma, and sends a leave-behind the same day. A founder preparing Series A opens the checklist post, then the seed versus Series A spoke, then drafts with real cohort evidence rather than recycled seed prose.

Failure modes include treating the blog as a news feed, publishing thin keyword pages, affiliate roundups without method, and using long-tails as a second homepage. Money pages remain product entry. Hubs remain craft systems. Examples remain annotated shapes. Climb from post to hub when you need the full system rather than a scenario patch.

Not for you if you need breaking news, if you want undated pricing tables for procurement, or if you refuse to draft after reading. Concrete next step: pick one featured scenario that matches a meeting within seven days, open the post, then generate an outline with your facts before you open a second article.

Quality bar matches spokes: one original framework or checklist, one worked example with specifics, failure modes, honest not-for-you guidance, and a concrete Gamma next step. Related links should climb into the parent hub and across to a product page without keyword soup. Measure a post by whether time-to-usable-deck for that scenario dropped.

Migration and tool-limit posts should name when to stay put. A Copilot or Beautiful.ai critique that never says who should keep the other seat is a sales page in disguise. Prefer posts that date the constraint and point at method when claims get comparative.

Education and workflow long-tails should still end in a draft action: notes cleaned into claims, thesis outline with timing, or Notion export trimmed before generate. If the post only lists tips without a recreate path, treat it as incomplete and open the matching learn hub instead.

Draft the scenario you would write about

Outline-first decks make better case studies, and better meetings.