Update a customer deck from discovery-call context

Why use this

1. A sales presenter may learn new customer priorities during discovery while the prepared deck still emphasizes earlier assumptions. Updating slides from partial conversation can also turn an exploratory comment into a promised product capability.

2. A change preview could connect each proposed slide revision to the customer’s actual words and the approved master. The presenter could decide which changes are accurate and timely before showing or distributing the revised deck.

Why an agent / simpler alternative

Useful judgment

Select relevant customer context and distinguish confirmed needs from questions or tentative remarks.

Simpler alternative

Use speaker notes or a manual slide edit when only one point needs adapting.

Unsuitable when

Transcript accuracy, customer permission or product-claim authority is unresolved.

Proposed inputs

1. Name

   Approved branded master

   Owner

   Designer

   Minimum scope

   Relevant slide/component references and editable areas

   Quality check

   Confirm protected brand elements and source version.

2. Name

   Authorized discovery context

   Owner

   Account owner

   Minimum scope

   Recent transcript excerpts and verified customer priorities

   Quality check

   Check speaker identity and mark incomplete or uncertain transcription.

Access and setup — proposed or unknown

Proposed minimum

1. Read-only master and transcript copies; separate slide-change preview.

Compatibility unknowns

1. Unknown: exact runtime, Figma/slide access and live-transcript availability.

External actions requiring approval

1. Editing shared decks, presenting unreviewed changes or sending customer-specific material.

Expected deliverable and review checks

Proposed artifact

Customer-deck revision proposal with transcript references and preserved master properties.

Critical checks

1. Every customer claim has reliable context.

2. Slide wording does not convert a requested feature into an available capability.

Missing output evidence

No new workflow run or output inspection is performed for this editorial layer. The linked implementation evidence retains the original source-specific outcome and artifact limits.

Failure signals and proposed responses

1. Signal

   A customer asks whether a feature exists and the slide states that it does.

   Why it matters

   The deck could misrepresent the product.

   Proposed response

   Rewrite as a discovery question or obtain product-owner confirmation.

2. Signal

   Rapid content insertion breaks the master layout.

   Why it matters

   A personalized deck may become unreadable or inconsistent.

   Proposed response

   Keep the revision as a preview and have the designer review overflow.

Effort and cost — unknown

Setup work

1. Identify approved editable slides and trustworthy call context.

Ongoing review

1. Check factual wording and visual integrity before presentation.

Unknowns

1. Unknown: transcript latency, editing support and review-time requirements.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

An invented transcript contains one confirmed priority and one unanswered product question; the master has limited text space.

Acceptance checks

1. The priority informs a proposed change.

2. The product question and overflow remain review flags.

Stop conditions

1. A capability promise or unapproved customer disclosure is required.

Limits

1. Editorial presentation aid; no live tailoring speed or successful customer outcome is established.