Make the Leave-Behind Match the Meeting Deck
The Departure
The account brief is in one file, your leave-behind is half-written, and the deck still says last quarter's price as you head toward a client meeting. The danger isn't an ugly slide; it's handing over two polished things that disagree.
Give an agent one approved source packet to draft from between stops, then make agreement between the outputs your acceptance test.
The Co-Pilot
Tool: Claude Cowork with Claude Docs and Slides (beta, where available)
The Use Case: Draft an editable client one-pager and a four-slide meeting deck from the same approved facts, then reconcile every claim before export.
The Build: Anthropic's September 16 announcement brings Docs and Slides into the same Claude conversation as longer-running work. Its Docs guide describes turning a document into a presentation. That is a useful drafting path, not a guarantee that two generated files will agree. The formats are beta and access is rolling out; check that the output controls appear in your account.
Build a small packet before you leave: meeting objective, three or four approved account facts with their source lines, the current offer and price caveats, and the exact next-step ask. Strip out unnecessary personal data. Use only material your organization permits in this tool. If a number is unapproved, label it NEEDS REVIEW rather than asking the agent to smooth it into a claim.
The Prompt:
"You are preparing two draft client-facing artifacts for [CLIENT] on [MEETING DATE]. Use only the approved account packet pasted below. First create a shared facts table that lists the approved claims, source section, caveats, and intended next step. Then create (1) an editable one-page client summary in Claude Docs and (2) a matching four-slide presentation in Claude Slides. Slides: situation, proposal, price and exclusions, next step. Both outputs must preserve the same numbers, caveats, and next step. Never turn an unverified note into a client claim; list it separately as NEEDS REVIEW. Do not invent case studies, results, testimonials, ROI, dates, or customer commitments. If native Docs or Slides are unavailable, say exactly which format is unavailable and produce a clearly labeled fallback draft only. Do not send, share, publish, edit CRM, or use connected apps. Stop when both draft artifacts and the cross-artifact consistency check are ready. APPROVED ACCOUNT PACKET: [PASTE YOUR APPROVED PACKET HERE]."
That final comparison is the job. Check the source table yourself, then scan the one-pager and deck side by side. Did a six-week pilot become a six-month rollout? Did a price that excludes travel become an all-in quote? If either file drifts, fix it before exporting. A pretty output with one wrong number fails.
In a synthetic test for this issue, Claude produced both native formats and kept the core facts aligned. But its own consistency report missed an extra creation date in the Doc header. Check visible metadata, speaker notes, and any internal review notes too; an agent's green check is not your sign-off.
For external clients, don't assume a Claude sharing link works. The Docs guide says Team and Enterprise Docs cannot currently be shared outside the organization, and Pro/Max link recipients need a Claude account. Export a reviewed file through your approved process. Mobile can request or view a Doc, but editing and sharing settings require web or desktop.
The Upgrade
Topic: Run the one-packet, two-output check
Approve the packet. Put only current, client-safe facts, source lines, proposal scope, exclusions, and one next-step ask in a single file. Mark uncertain claims for review.
Draft both outputs. Paste the approved packet after the prompt in the same Cowork task. If Docs or Slides is not visible in your account, don't pretend the native-format step happened; use an approved alternative and keep the same checks.
Reconcile before sharing. Match every number, caveat, and ask across source, Doc, and deck. Resolve the exceptions yourself, then export and send only through your normal approval path.
The Landing
Try this with a fictional account first. Give it three approved facts, one price exclusion, and one tempting but unverified metric. The test passes only when the Doc and deck agree with the source, the unverified metric stays out, and you can point to the human decision that clears each exception.
Safe travels,
Marcellus