An investor deck has to survive more than a good-looking first draft. Its market figures need dates and methods. Its traction claims need company records. The recipient must be able to edit the file you send. This guide takes your approved venture evidence through a claim ledger, a slide narrative, Claude Slides, an editable export and an independent human review. The steps follow Anthropic's current Artifacts instructions, checked on 21 October 2026. BIG CHANGE did not make or export a venture deck for this guide.

This is for a venture owner or authorized deck editor who can approve the claims and the intended audience. You also need someone outside the drafting process to check facts and rights. A coherent deck is the result of those decisions; Claude can help draft copy and arrange slides, but cannot supply your company's missing evidence.

Before you start

Collect the latest approved product description, operating and customer records, team bios, and any proposed financing terms or ask you actually intend to disclose. Identify the owner and revision of each document. Obtain permission to use and upload it. If a source contains restricted customer, financial or employee information, make a disclosure-safe extract or wait for the source owner's decision before adding it to Claude.

For market and competitor claims, go to the original report, filing, product page or other attributable source. Record its publication or access date, geographic and product scope, method, units and any license or quotation limits. Keep a company's estimate distinct from measured company results and from a third party's forecast. Check competitor descriptions against current primary material and give them a fair comparison basis. Where a source cannot be checked or disclosed, leave the claim out.

Choose the recipient's actual editable format, PowerPoint or Google Slides, and the person who will review the final file. Have an approved logo, font and brand guide or an approved Claude design system, including permission to use each asset. Check the account's Slides template and Cloud code execution and file creation setting before uploading sensitive material. Anthropic says Docs, Slides and Design templates are available across plans, but an organization owner can control capabilities. The Artifacts admin guide describes the Team and Enterprise controls. Artifact work counts toward the account's usage limits; enterprise billing and spend controls depend on the organization's plan. Check your own account and any recipient app cost.

1. Build a source pack and claim ledger

Keep a private folder with approved extracts and dated source copies or links. Give each claim a stable ID before asking Claude to write slides. A spreadsheet with these columns works:

Text
claim_id | exact approved wording or number | fact / estimate / forecast | source owner | URL or private document revision and page | source date and as-of date | method, units and denominator | permitted audience | slide IDs | reviewer decision

Enter your real evidence, without sample company figures. For a calculated rate, retain the approved numerator, denominator, period and arithmetic so the reviewer can reproduce it. For a market total, preserve the source's definition and coverage; do not silently relabel a broad market as the venture's addressable market. For a competitor comparison, record the checked product version, price or feature date and the dimension compared. Use [owner evidence needed] as a working placeholder for an unsupported claim. Remove it or omit the slide before handoff.

Mark each record approved, disputed or unresolved with the source owner's decision. Do not treat an AI summary, a search snippet or an older deck as primary proof of a current company metric. The ledger is the point where an attractive but unsupported number should stop.

2. Approve the story before making slides

Write one sentence stating what the company does and what the evidence presently supports. Then make a slide map the owner can change before design begins:

Text
slide_id | role | audience question | one factual takeaway headline | allowed claim IDs | visual and asset permission | footnote/source | owner decision

Map a cover, problem, solution or product, market, competition, traction and team. Add business model, go-to-market, an ask or use of funds only if the owner has substantiated material and the audience needs it. A traction slide can state the evidence's scope and period; if there is no approved traction claim, hold or remove that slide. The same rule applies to market size and the ask. A competitor slide should say what was compared and when, not imply a product won every dimension.

Give each slide one audience question and a headline that makes a supported point. Put the claim IDs and the source citation beside the proposed copy. Sketch charts only from ledger values, with axes, units, denominators and dates. Get the venture owner's approval of the order and disclosure scope. A slide sequence is useful only if the evidence can carry it.

3. Draft copy in Claude Slides

In Claude, choose Output → Slides in the message box or open Artifacts and select a Slides template. Anthropic says Slides can be made from notes, reports or the work already in a conversation, then edited slide by slide. Work inside the account and data boundary the source owner approved. Supply the disclosure-safe source pack, ledger and approved map. You can adapt this prompt:

Text
Create a Slides presentation only from the attached approved source pack,
claim ledger and slide map. Follow the mapped slide order and one factual
takeaway per slide. Draft concise slide copy, and put the supporting claim IDs
and source/date references in the working notes or footnote area for review.
Keep [owner evidence needed] visible where the approved pack is silent.
Do not invent metrics, customers, quotations, logos, market totals, team
credentials, an investment ask or investor endorsement. Distinguish measured
facts, estimates and forecasts. First return the proposed headline and body
copy for every slide in text, with its claim IDs, so the owner can approve or
correct the narrative before you lay it out.

Read that text pass against the ledger. Ask Claude to identify transitions that claim more than the source proves, then make the actual correction yourself with the owner. Check that the problem leads to the product, that the market definition fits the product, that comparisons are fair and that the team claims match approved biographies. Once the copy passes, ask Claude to build the mapped Slides deck. Use its direct slide editing for corrections rather than assuming another generation will preserve every fact.

4. Apply the approved visual identity

Select an existing approved design system if the account offers one. Anthropic says a Claude design system can carry colors, typography, components and layout patterns into decks. Design systems are in beta on Pro, Max, Team and Enterprise; Enterprise owners control enablement. If one is unavailable, provide the permitted brand references and inspect the deck manually. Our guide to building and checking a Claude Design system covers that separate setup task.

Review every slide at presentation size. Check logo use, font substitution, contrast, chart legibility, spacing and clipped text. Use only visuals and customer marks cleared for this audience, with the right license and attribution. An AI-generated illustration cannot stand in for a product screenshot, a customer identity or evidence of a market result. Remove decorative images that obscure sources or figures.

5. Check the deck claim by claim

Work through every slide with the ledger open. For each headline, number, chart label, comparison, customer logo and team credential, record its claim ID or asset permission. Compare wording, period and source revision. Check that estimates and forecasts are labeled on the slide itself. Verify chart axes, units and denominator; a footnote cannot rescue a misleading visual. Inspect source notes and citations where the recipient will see them.

Read the story aloud as a reviewer would: What problem is evidenced? What does the product demonstrably do? Which market has the source measured? What supports traction and team capability? If a leap remains, change or remove the slide. Record the unresolved slide ID instead of silently filling it with Claude's plausible wording.

6. Export and reopen the editable file

Use Export → PowerPoint for a PowerPoint recipient, or Anthropic's direct Google Slides export for a Google Slides recipient. The Artifacts export instructions also offer PDF, which is useful for reference but does not meet this editable handoff. Keep the approved Claude deck and the exported file under distinct revision names.

Open the actual exported copy in the recipient's intended editor. Compare slide count and order with the approved map. Try editing representative titles, body text, a chart or shape that the recipient must change, and notes if the handoff requires them. Check fonts, image placement, line wraps, clipping and source references on every slide. Anthropic describes the export as editable, but that description does not establish that each element in your particular deck survived as a separate editable object. Record exceptions. If a required element is flattened or displaced, rebuild it in the destination editor, then repeat the visual and factual checks on that final file. Our Gamma export guide covers a different starting point: a deck already made in Gamma.

7. Get independent signoff, then control sharing

Give a reviewer who did not draft the claims the final opened file, ledger, source revisions and asset permissions. Ask them to check each material statement, market assumption, competitor description, citation, team bio, visual license and intended audience. Resolve comments in the destination file, then reopen and inspect the revised export again. Record the review date, reviewer, slide IDs checked, remaining exceptions and the exact final file's hash or version identifier. The venture owner decides whether the reviewed deck may be shared and with whom.

An Artifact begins private, and Anthropic's sharing guide describes plan and organization controls for link and invite access. Check the actual Share dialog before exposing a Claude link; a downloaded file has its own distribution path. Test the intended recipient's access with the agreed sharing method. A file's existence, a link or an attractive deck says nothing about investor acceptance or fundraising results.

If a check fails

If Slides or cloud file creation is unavailable, check the account and organization capabilities and use an authorized account only after the data owner approves that boundary. If usage limits stop the work, retain the ledger and approved map for a later session; do not pass restricted evidence to an unapproved service. If sources conflict or permission is uncertain, hold that claim and ask its owner to settle the exact wording and audience. If Claude changes a number or source, restore the ledger wording and recheck that slide. If branding drifts, correct the selected system or slide and inspect again.

If PowerPoint or Google Slides opens with flattened or shifted required elements, repair those elements in that editor and send the repaired revision back through independent review. If artifact sharing is broader than approved, restrict it in the Share dialog and verify the intended recipient's access before delivery. Keep the reviewed file, ledger and decision record together so later updates have a clear starting revision.

The big change

  • A dated claim ledger gives every material slide statement an owner, source, method and permitted audience before design begins.
  • Claude Slides can draft and lay out the approved narrative, while the actual exported PowerPoint or Google Slides file must be reopened and checked for the recipient's required edits.
  • An independent reviewer and venture owner decide whether the exact final file is accurate, licensed and ready for its intended audience.

Sources & further reading