Prompt library
Answer the pricing question without dodging
Buyers ask early to self-qualify, and a number with anchors respects that while keeping sizing control. The three-reaction follow-ups turn the scariest moment of early conversations into a planned fork, including the underpricing tell most reps miss.
Last reviewed July 17, 2026
The prompt
Draft responses to a pricing question that arrived before we wanted it.
The question as asked: {{question}}
Our pricing reality: {{pricing}}
Where we are in the deal: {{stage}}
Produce:
1. The principle: why dodging ("it depends") burns trust, and what the buyer is actually asking (am I wasting my time? am I the budget owner for this size?).
2. Three response drafts:
- The range with anchors: the real range plus what places a customer at each end, then a question that sizes them.
- The example customer: "a company your size typically lands around X because Y", then the sizing question.
- The qualify-first, used ONLY when we genuinely cannot range it: give the floor ("engagements start at X"), explain the one variable that moves it most, commit to a number by a date.
3. For each: when it is the right draft, and the follow-up if they react with silence, sticker shock, or "that is cheaper than expected" (underpricing signals matter too).
4. The line we never say: pretending price is not decided when it is.
Every draft gives a real number or a real floor. No draft postpones the answer past this conversation.Run in idaptOpens a new chat with the prompt prefilled. Nothing sends until you press send.
Fill in the variables
| Variable | What it is | Example |
|---|---|---|
| {{question}} | How they asked | before we go further, what does this roughly cost |
| {{pricing}} | Your actual pricing structure | 9k to 40k per year, driven by seat count and data sources |
| {{stage}} | Where the deal is | first call, problem confirmed, no scoping yet |