Prompt Library

Keep your 10-slide pitch deck current with real numbers every month

Every month, Sai rebuilds your 10-slide pitch deck from the same numbers your team already tracks, updates the traction and runway slides, and flags every claim the data no longer supports — so the deck is ready the day an investor asks for it.

The PROMPTS
Copy prompt
On the [first Monday] of every month, rebuild our investor pitch deck and publish it as a web presentation. Structure: ten slides — Title, Problem, Solution, Why now, Market, Traction, Business model, Competition, Team, The ask. Start from our current deck at [Drive / Docs URL] and keep my wording on every narrative slide. Update these slides from data every run: Traction from [metrics sheet URL / billing export], showing the last [12] months as one chart; Business model from [pricing page URL] and our latest unit economics at [sheet URL]; Team from [team roster / org chart]; The ask using our current cash and net burn from [finance sheet URL], stating how many months the raise buys. Do not rewrite Problem, Solution, Why now, Market, or Competition. Instead, check each against current evidence — [competitor list / market notes / customer interview folder] — and if a claim no longer holds, mark the slide "Needs review" with one line on what changed and the source. At the top of the page, add a change log: which numbers moved since last month, which slides were auto-updated, and which are flagged for review. Every number on a slide must link to its source; if a source is missing, leave the number blank and say which input is missing — never estimate. Style: [brand colors / font], one idea per slide, large type. Make it presentable in a browser and exportable to PDF. Keep each month's version at its own link.
Run this TaskView Demo

Platforms this prompt works across

Most founders do not have a pitch deck problem. They have a stale pitch deck problem. The deck was built for the last round, and in the months since, traction has doubled, pricing has changed, two people have joined, and one competitor has pivoted. None of that reaches the slides until an investor asks for "the latest deck" — and then it becomes a weekend of rebuilding under pressure, which is exactly when numbers get copied wrong.

‍

What this recurring task does

Once a month, Sai rebuilds your deck on a standard 10-slide seed structure. The slides that are pure numbers — traction, business model, team, and the ask — are updated automatically from the sources your team already maintains. The slides that are judgment — problem, solution, why now, market, competition — keep your wording, but are checked against current evidence and flagged when a claim no longer holds. A change log at the top shows what moved since last month.

‍

The 10-slide structure, and what goes stale on each

A template tells you what each slide should contain. The more useful question between rounds is what quietly stops being true.

★ THE 10 SLIDES, AND WHAT GOES STALE ON EACH

SlideWhat it must showWhat goes stale between rounds
1 · TitleCompany, one-line description, contactThe one-liner, after the positioning quietly shifts
2 · ProblemWho hurts, how often, what it costs themCustomer quotes older than the current product
3 · SolutionWhat the product does, shown not describedScreenshots of a UI that no longer exists
4 · Why nowThe change that makes this possible todayA "recent" shift that is now two years old
5 · MarketBottom-up market size with sourcesA sizing that no longer matches who actually buys
6 · TractionRevenue or usage trend, one clear chartEverything — this slide is out of date within weeks
7 · Business modelPricing and unit economicsOld pricing tiers; early CAC figures
8 · CompetitionPositioning against real alternativesCompetitors that pivoted, raised, or shut down
9 · TeamWhy this team winsMissing recent hires; people who have left
10 · The askAmount, runway it buys, milestonesA runway figure computed on last quarter's burn

‍

Why Sai updates numbers but only flags narrative

A deck that rewrites its own story every month would be worse than a stale one. The founder's framing of the problem is the argument, and it should change only when the founder decides it should. So Sai draws a hard line: numbers are refreshed from source, and every figure links back to where it came from; narrative slides are never rewritten, only marked "Needs review" with a one-line reason — a competitor raised, a market assumption no longer matches who is actually buying. The founder decides what to do with the flag.

‍

What happens on the second run

Each monthly deck keeps its own link, and the change log compares it with the previous month. Over time that history becomes useful on its own: you can see how long a slide has been flagged without being fixed, and investors who saw an earlier version can be sent a deck that shows real progress rather than a new coat of paint. If a source is missing, the number is left blank and the missing input is named, rather than carried forward from last month as if it were current.

‍

Where this fits

This deck pulls from the rest of the founder toolkit. Traction comes from the same numbers as the weekly executive briefing deck. The ask slide's runway figure comes from the monthly cash runway calculator, and the business model slide can cite the monthly SaaS metrics dashboard. The competition slide is checked against the monthly market landscape map. For the classic slide order this structure follows, see Y Combinator's guide to seed fundraising.

Stop doing repetitive tasks. Let Sai handle them for you.

Sai is your AI computer use agent — it operates your apps, automates your workflows, and gets work done while you focus on what matters.

Try Sai