Map verified customer jobs and evaluation criteria to a realistic, evidence-backed demonstration. 제공할 내용: Customer needs and decision, Verified product behavior, Demo session constraints. 예상 결과: A timed demo plan with scenarios, proof, roles, checkpoints, limitations, and fallback.
1
맥락 추가
텍스트는 이 브라우저에 유지됩니다. AILesson Prompts는 이를 모델이나 서버로 보내지 않습니다.
2
프롬프트
채워지지 않은 필드는 플레이스홀더로 표시되므로 프롬프트를 복사하고 편집할 수 있습니다
Create a customer demo plan from verified needs and product behavior. Do not script capabilities that do not exist.
Source-tagged jobs, workflow, problems, outcomes, criteria, stakeholders, authority, timeline, and unknowns:
[needs]
Available features, setup, data, integrations, permissions, proof, limits, roadmap, and approved claims:
[product]
Attendees, duration, environment, privacy, presenter roles, required topics, risks, Q&A, and next step:
[session]
Separate confirmed need, seller interpretation, assumption, and unanswered discovery question. Rank sections by the customer's stated decision criteria, not feature novelty. Map each need to a realistic scenario, exact product behavior, evidence, limitation, and verification question. Do not imply a mockup, manual workaround, beta, roadmap item, integration assumption, sample data, or presenter action is generally available. Use synthetic data unless authorized otherwise.
Design opening contract, current-state recap for confirmation, scenario-based flow, audience checkpoints, limitation/trade-off section, Q&A, and mutual next-step decision. For every segment specify purpose, time, persona/job, starting state, steps, expected visible result, proof, presenter/support role, setup dependency, question, and fallback. Include a must-show/optional/cut list, dry-run checklist, access/privacy plan, failure recovery, unanswered-question parking lot, and post-demo evidence/commitment log.
기본적으로 비공개프롬프트 구성은 브라우저에서 로컬로 이루어집니다. 조직에서 허용하지 않는 한 기밀 정보를 AI 서비스에 입력하지 마세요.
입력에서 결과까지
적용 예시
구체적인 맥락이 이 레시피를 바로 사용할 수 있는 결과로 바꾸는 방법을 확인하세요
실제 입력
Customer needs and decision
Discovery D1: operations lead says 14 branches submit monthly CSVs with inconsistent category labels; analysts spend about two staff-days reconciling. D2: data lead requires definitions, validation failures, and approvals to be auditable. D3: security reviewer asks where files are stored; no data may leave UK region. Decision criteria stated: auditability, CSV workflow fit, permission control, implementation effort. Priya can recommend; procurement and security approve. Unknown: SSO requirement, exact CSV schema, accessibility criteria, budget, and desired go-live date.
Verified product behavior
ClearLedger currently imports CSV, maps fields to a configurable dictionary, runs required-value/allowed-label rules, displays row-level failures, and records approval history with user/time. Role permissions: editor/reviewer/admin. UK-region hosting is available on enterprise plan; security documentation approved for sharing. SSO is available only on enterprise plan but customer need unconfirmed. No automatic correction, Excel add-in, or guaranteed time saving. Demo tenant uses synthetic branch data. API integration is roadmap, not available.
Demo session constraints
Thirty minutes remote: Priya, data lead, security reviewer; seller presenter and solutions engineer. Fifteen minutes demo, five discovery/checkpoints, five security/limitations, five Q&A/next step. Screen-sharing may fail; prerecorded approved clip and screenshots available. Do not collect customer files. Next step could be technical validation only if security and data lead agree; no purchasing commitment.
예시 출력
Opening 0-2 min: contract—“We will show a synthetic CSV from import through definition mapping, validation, and approval history, then cover UK hosting and limitations. We will not estimate savings or assume SSO. Please correct our workflow recap.” Confirm D1-D3 and decision criteria.
Must-show 2-7 min, CSV fit: synthetic branch analyst imports a deliberately inconsistent file, maps exact supplied demo fields, sees row-level required/allowed-label failures. Visible result is an exception list; explicitly state ClearLedger does not auto-correct. Evidence: current demo tenant. Checkpoint to data lead: “Does this resemble where your team needs control, and which schema details differ?” Unknown schema goes to parking lot.
Must-show 7-12 min, auditability: editor corrects synthetic source outside product or updates permitted mapping as applicable, reviewer approves, history shows user/time. Do not imply customer governance is configured. Ask what approval evidence D2 requires. 12-15 min, permissions: editor/reviewer/admin behaviors using preconfigured demo accounts; ask whether these roles map to theirs. SSO is a conditional enterprise capability, not shown unless confirmed.
15-20 min security/limitations: solutions engineer shows approved UK-region/security document, states enterprise-plan condition, synthetic-data boundary, no API/Excel add-in/automatic correction/time guarantee. Security reviewer confirms whether documentation is sufficient for technical validation. 20-25 min Q&A; unknowns logged with owner, no improvised roadmap promise. 25-30 min next step: propose technical validation only if data lead/security agree; procurement/purchase remains separate.
Optional: SSO overview after requirement confirmation. Cut first: role edge cases, extra validation rules; never cut limitations or checkpoints. Dependencies: tenant reset, accounts, synthetic CSV, UK document, clip/screenshots, captions. Screen-share fallback uses approved clip then screenshots and labels it prerecorded. Post-demo log records what was observed, questions, answers needing evidence, and only explicit commitments/owners/dates.
효과가 있는 이유
1
Need-to-proof mapping keeps a demo focused on customer evaluation rather than a tour of available features
2
Visible limitations and fallback states protect trust when an environment, integration, or assumption fails
결과 확인
Is every segment tied to a confirmed need or clearly labeled discovery assumption
Are product behavior, setup, proof, limitations, and availability status accurate
Does the plan include checkpoints, fallback, privacy, unanswered questions, and real next-step authority
안심하고 사용하세요
자주 묻는 질문
이 레시피를 언제 사용해야 하는지, 무엇을 제공해야 하는지, 그리고 어떤 부분에서 사람의 검토가 여전히 중요한지에 대한 실용적인 답변
What should I prepare before using “Draft a demo plan outline from customer needs”?
For “Draft a demo plan outline from customer needs,” prepare Customer needs and decision, Verified product behavior, and Demo session constraints. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.
When is the “Draft a demo plan outline from customer needs” result not ready to use?
The result is not ready if it does not yet deliver the stated outcome—A timed demo plan with scenarios, proof, roles, checkpoints, limitations, and fallback—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.
Which AI tools have recorded tests for “Draft a demo plan outline from customer needs”?
The published test record for “Draft a demo plan outline from customer needs” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.
ChatGPT
