Customer pitch decks generated from a Google Slides template

One template, every prospect different

The pitch deck a sales team sends to a prospect is almost never the master template. The story changes for a CTO and a CFO. The framing changes for a fifty-person startup and a five-thousand person enterprise. The angles that land for a fintech don’t land for a manufacturer. So the deck gets copy-pasted, edited, re-edited, and the version that goes out is whatever survived the last twenty minutes of polish.

That work is the same work every time: read up on the company, figure out what they care about, retell the deck in their language. None of it is creative — it’s research plus tailoring. This example moves both into the workspace.

The form, the table, the deck

The Customer Presentations page has two things on it: a short form for kicking off a new deck, and a table of every deck that’s been generated. The form takes three fields — the prospect company name, the contact person, and their role — which is exactly what the tailoring pass needs. Submit the form and a Generated Presentation record lands in the table in the generating state so everyone on the team can see a deck is on the way.

As the background task progresses, the record transitions through generating → reviewing → completed (or failed if something blocks it). When the deck is ready the row carries a direct Google Slides link, the Slides file ID, and a one-line review note about what the polish step tidied. The whole record — who asked for it, what was filled in, where the finished deck lives — sits in the table for next time, so the team doesn’t lose track of which prospect already got a deck and which didn’t.

From a name and a role to a finished deck

1. You fill in the form. Company name, contact name, contact role. A new Generated Presentation row lands in the table in the “generating” state.
2. The workspace researches the company. A background task does a web-search pass on the prospect — what they do, their size, their industry, the kind of challenges someone in the contact’s role would care about. This is the part a human would otherwise do in a browser before opening Slides.
3. Your Slides template gets copied and filled in. The workspace duplicates your master pitch template via Google Slides’ copy_presentation, reads every slide with get_presentation, swaps any {{placeholder}} tokens via replace_all_text, and rewrites each descriptive section from the seller’s perspective — tailoring the angle to the contact’s role.
4. The deck moves to your Drive folder. The new file is filed into a “Customer Presentations” folder in Google Drive — the folder gets created the first time round, then reused for every future deck.
5. A polishing pass cleans up loose ends. A second task — Review Customer Presentation — silently reads the finished deck, fills any empty sections, rewrites generic filler, removes leftover placeholder tokens, and flips the row to completed with a short review note describing what was tidied.

What the workspace actually stores

Each Generated Presentation row captures everything you might want to look back at later: the company_name, contact_name, and contact_role from the form; the task_id and review_task_id the platform uses to poll progress; the live status through generating → reviewing → completed / failed; the presentation_url and google_slides_id of the finished deck; the review_notes from the polish pass; an error_message if anything failed; and created_at + created_by so the team can tell who kicked it off and when.

Template, folder, and tailoring depth

• The Slides template — the master deck the workspace copies on every run. Swap it for an updated template whenever marketing refreshes the pitch and every future generation picks up the new structure automatically. Slide titles are left untouched; only the body content of descriptive sections gets rewritten.
• The Drive folder name — defaults to “Customer Presentations”. Rename it for a region, a quarter, or a campaign and the workspace will create-or-reuse the folder you point at.
• Who can generate a deck — restrict the form to specific roles so prospects aren’t accidentally generated by people outside that workflow.
• The tailoring depth — how aggressively each section gets rewritten for the prospect. Light-touch for familiar categories, heavier rewrite for prospects in industries the master template doesn’t cover well.
• The polishing pass — which kinds of leftover placeholders, generic filler, empty sections, and wrong-topic content get auto-fixed before the row flips to completed.

The pitch you would have written, written for you

The pieces that change per prospect — the company facts, the role-specific angle, the section rewrites — are exactly the pieces a human would have redone manually. The pieces that stay the same — which template, which Drive folder, the polishing rules — are declared once and reused for every deck after.

When the master deck changes, you update the template. When the team moves to a new shared folder, you change the folder name. When the polish pass needs to catch a new kind of stale copy, you adjust the rules. The deck a prospect sees is always the current pitch, tailored to them, without anyone on the team having to rewrite it.