Use this prompt recipe for pricing explanation after a demo. It gives the AI a clear job, visible source inputs and a review step so the result can be edited instead of blindly copied.
| Best for | sales teams, founders, account managers and partnerships teams |
|---|---|
| Search intent | Readers usually need prompts for sales messages and planning that are specific, respectful and grounded in real account context. |
| Expected output | Account context summary, Message or call plan, Likely objections, Follow-up checklist |
When this recipe is useful
Use this recipe when the task is specific enough to benefit from AI structure but still needs human judgment. In the situation "after a demo", the prompt should make the audience, source material and quality bar explicit before asking for a finished answer.
The goal is not to make a generic pricing explanation. The goal is to create a draft that reflects the real context, avoids unsupported claims and gives the reviewer a clear path for improving the result.
Source inputs to prepare
| Buyer context | Add the real detail for pricing explanation after a demo. If this detail is unknown, ask the AI to return a missing-information question. |
|---|---|
| Known pain point | Add the real detail for pricing explanation after a demo. If this detail is unknown, ask the AI to return a missing-information question. |
| Offer or solution | Add the real detail for pricing explanation after a demo. If this detail is unknown, ask the AI to return a missing-information question. |
| Proof available | Add the real detail for pricing explanation after a demo. If this detail is unknown, ask the AI to return a missing-information question. |
| Next sales step | Add the real detail for pricing explanation after a demo. If this detail is unknown, ask the AI to return a missing-information question. |
Copy-ready prompt
Recommended output structure
- Account context summary: Make this section specific to pricing explanation after a demo and easy for a human reviewer to check.
- Message or call plan: Make this section specific to pricing explanation after a demo and easy for a human reviewer to check.
- Likely objections: Make this section specific to pricing explanation after a demo and easy for a human reviewer to check.
- Follow-up checklist: Make this section specific to pricing explanation after a demo and easy for a human reviewer to check.
Review checklist
- The output uses specific account context instead of generic persuasion.
- The value claim is supported by proof or marked for review.
- The next step is small and realistic.
- The tone respects the buyer relationship.
Common mistakes
- Using flattery without research.
- Overstating ROI or results.
- Making the ask too large for the relationship.
- Ignoring objections the buyer already raised.
How to adapt it
If the first output feels too broad, add one concrete example of the audience, one example of the tone you want, and one example of a claim the AI must avoid. This usually improves the next answer more than adding more adjectives.
If the output is too long, ask the AI to keep the structure but shorten each section around the decision the reader needs to make. If the output is too shallow, add source notes and ask for missing questions before another draft.
FAQ
When should I use this prompt?
Use it when you need pricing explanation after a demo and want the AI output to stay tied to your real source inputs, audience and review rules.
What should I prepare first?
Prepare the practical inputs: Buyer context, Known pain point, Offer or solution, Proof available. If one of those is missing, keep it marked as unknown instead of asking the AI to guess.
Can I publish the output directly?
Treat the output as a draft. Check facts, claims, names, dates, policies and promises before using it in public or customer-facing work.