Turn prospect context into a tailored interactive demo
Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.
The problem
Generic product demos fail to reflect the prospective customer's actual data and operational questions.
Agent job
Use authorized prospect recordings, messages and spreadsheets to tailor an interactive HTML demonstration.
Expected output
A customer-specific interactive demo.
Where this framing comes from
Core problem: Editorial purpose framing
Agent job: Editorial purpose framing
Expected output: Editorial purpose framing
Relevant job roles: Editorial purpose framing
Benefit type: Editorial purpose framing
Editorial framing and outcome limits
Describes the task’s purpose and intended output; measured benefit, safe unsupervised operation and successful delivery are not established by this framing.
Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.
Case-specific decision guidance · untested
Case-specific decision guidance and first checks are original proposals. The linked source supports the attributed task; this added guidance has not been executed.
A sales team may want a demo to reflect a prospect’s actual fleet and workflow, but discovery material can mix confirmed facts, estimates and sensitive operational details. A convincing screen can imply that a simulated function already exists in the product.
A tailored-demo specification could show which inputs are approved, which data are synthetic and which interactions are demonstrative. The presenter could review the narrative before exposing prospect information or making product commitments.
Why an agent / simpler alternative
Useful judgment
Translate prospect context into relevant demo scenarios while identifying unsupported capabilities and sensitive fields.
Simpler alternative
Use a standard demo with a few renamed examples when deep customization adds little value.
Unsuitable when
The task requires unapproved prospect-data disclosure or representing prototypes as production features.
Proposed inputs
Name
Authorized prospect context
Owner
Account owner
Minimum scope
Relevant call excerpts, messages and spreadsheet fields
Quality check
Confirm permitted use and separate facts from estimates.
Name
Demo capability and audience brief
Owner
Product owner
Minimum scope
Supported product behavior, approved mock interactions and intended viewers
Quality check
Identify where synthetic data must replace real records.
Access and setup — proposed or unknown
Proposed minimum
Read-only minimized source copies and an isolated private demo plan.
Compatibility unknowns
Unknown: exact runtime, HTML build tools, data formats and hosting access.
External actions requiring approval
Uploading prospect data, publishing the demo or sharing it beyond the approved audience.
Expected deliverable and review checks
Proposed artifact
Scenario map and interactive-demo draft specification with data/prototype labels.
Critical checks
Every prospect-specific detail has approved provenance.
Simulated interactions do not imply live integrations or guaranteed product capabilities.
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
Signal
A prospect estimate becomes a precise operational metric.
Why it matters
The demo could misstate the prospect’s business.
Proposed response
Label it as an estimate or replace it with clearly synthetic data.
Signal
A mock action appears to update a live system.
Why it matters
The presenter could create a false product expectation.
Proposed response
Mark the interaction demonstrative and review capability wording with the product owner.
Effort and cost — unknown
Setup work
Select a bounded scenario and minimize prospect data.
Ongoing review
Verify narrative, capability claims and audience before presenting.
Unknowns
Unknown: build effort, integration feasibility and commercial impact.
First check — proposed, unexecuted
Status
proposed_unexecuted
Synthetic fixture
An invented fleet spreadsheet contains an estimated vehicle count and a mock dispatch action with no live integration.
Acceptance checks
Both are labelled accurately.
No real prospect data or deployment is needed.
Stop conditions
Data-sharing permission or product-claim approval is missing.
Limits
Editorial demo-planning aid; no customer-specific deployment or sales effectiveness is established.
Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.
CodexIndependent testing: No
Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.