2.5 · Presenting the price & the proposal

Level 2 · The sales meeting

2.5Presenting the price & the proposal

Goal: Present the price with confidence, justify it through value and structure a clear sales proposal.
Estimated time: 12 min · self-paced reading · If you only have 5 min: read “The essentials in 30s” + the diagram.

The essentials in 30 seconds

  • Value first: recap agreed needs + benefits before the number — price concludes value, it never precedes it.
  • State then go silent: total first, detail next, 2-3 options — first to speak after the price loses.
  • Quotes that sell: needs, priced solution, proof, validity + dated next step — with no follow-up date, it sleeps in the pile.

Threaded mini-case — Younes states €4,800 without apologizing

Final act: Younes, B2B sales rep selling equipment in Algiers, recaps the agreed value — auto follow-ups stopping lost quotes + 7-day support — and gets it agreed: “we agree?”. Then he states: “The investment is €4,800 a year, that’s €13 a day for the team,” and goes silent. The customer thinks, then asks: “and to start?”. Younes books Thursday 10am. His quote will recall the needs, price the options and date the next step.

Final episode of the 2.1-2.4 case — Younes closes without discounting.

1. Price is prepared: recap value first

Restate agreed needs + benefits (« we agree that… ») BEFORE the number: price concludes value, it doesn't precede it. State the price then go silent (first to speak loses): silence lets the customer think, not flee.

2. Present: total, detail, options

Total first (anchoring), detail next (what's inside), 2-3 options (good/better/best: the middle sells). Speak in usage value (« €3/day per rep ») rather than raw total when relevant.

3. The written proposal: the quote that sells

Needs reminder (1 page), priced solution (options), proof (cases, guarantees), validity + dated next steps (« valid 30 days, sign-off Thursday? »). A quote without a follow-up date sleeps in the pile.

Common misinterpretation: “You must drop the price fast, then justify it and concede a discount to show goodwill.” No. Price dropped without value looks naked and high; justifying before objections sounds defensive; discounting to fill silence gives away value. The rule: agreed value → owned price → silence → dated next step, and justify after objections, never before.
Owned price Recapped value, stated price, dated next step. Recap (value) Agreedneeds + benefitsState (silence) Total,detail, optionsDate (next) Validity +booked meeting
Recapped value, stated price, dated next step.
Text version of the diagram (SEO / screen readers / translation): 1) Younes RECAPS the value and gets it agreed before any number. 2) He STATES the total then the detail and options, in usage value, then GOES SILENT. 3) He DATES: a quote with validity and a booked next step. Lesson: value → price → silence → next; never discount to fill silence.

🔎 Concrete example — 🔎 Concrete example — An announcement that doesn't discount

“Let's recap: auto follow-ups (no more lost quotes) + 7-day support…
  Agreed? [yes] → The investment is €4,800/year,
  that's €13/day for the team. [SILENCE]
  → customer: “…and to start?” → “Thursday 10am, 1 h?”

Takeaway: value → price → silence → next.

Lesson: justify after an objection, never before (defensive).

Section vocabulary

Price presentation
The moment the tariff is stated; to do confidently and after establishing value.

Simple example: Younes states €4,800 in a steady voice, then goes silent.

What it is not: dropping the price awkwardly with apologies.

Reflex: state it as something normal, without hesitating.

Value (before price)
The offer’s benefits to argue before stating the price, so it looks justified.

Simple example: Auto follow-ups + support agreed before Younes’s number.

What it is not: stating the raw total before any benefit.

Reflex: always get the recap agreed before the number.

Price relativization
Bringing the price to a speaking unit (per day, per user) or comparing it with the problem’s cost.

Simple example: “€13 a day for the team” instead of the yearly total alone.

What it is not: leaving the raw total with no usage landmark.

Reflex: translate into usage cost whenever relevant.

Sales proposal
A structured, clear offer (included, options, terms) highlighting value and easing decisions.

Simple example: Younes’s quote: needs, options, proof, 30-day validity.

What it is not: an isolated number with no content or next step.

Reflex: needs + solution + proof + validity + dated next step.

Confidence (price)
A confident, unhesitating attitude when stating the price, reassuring customers.

Simple example: Younes neither justifies nor trims after his statement.

What it is not: filling silence with justification then a discount.

Reflex: after the number: silence, listening, next.

In practice — Hands-on — Present price and structure proposals

  1. Establish value first (argued benefits) BEFORE stating the price, never the reverse.
  2. Present the price confidently and naturally, without apologising or hesitating (hesitation creates doubt).
  3. Link the price to benefits and relativise it (per day, per user, vs the cost of the current problem).
  4. Structure a clear proposal (included, options, terms) that highlights value and eases the decision.
You present the price confidently, backed by value, and structure a clear proposal: a price that looks justified and moves things towards the close.

Ready-to-say script — state the price without discounting (30 s)

“Let’s recap: auto follow-ups — no more lost quotes — plus 7-day support. Agreed? The investment is €4,800 a year, that’s €13 a day for the team. [SILENCE — let them answer]”

Agreed recap + total + usage value + silence: add nothing before the customer answers.

Copy-paste template — quote that sells

NEEDS REMINDER (1 page): _______________
PRICED SOLUTION (total + detail): _______________
OPTIONS (good / better / best): _______________
PROOF (cases, guarantees): _______________
USAGE VALUE (per day / user): _______________
VALIDITY + DATED NEXT STEP: _______________

Tight customer budget

Relativize in usage value and propose good/better/best: the framed middle reassures without discounting.

SME in Algeria

Younes shows the clear incl.-tax total, options and 30-day validity, with a next step booked in the diary.

Multi-decider B2B

A quote readable by absentees: needs reminder + proof + next step, so everyone gets it without the meeting.

Video + express send

Spoken announcement then quote sent within the hour: fresh value, next step dated within 48 h.

✓ Best practices

  • Value first, price next.
  • Silence after the number.
  • Dated quote + next.

✗ Common pitfalls

  • Price dropped without value.
  • Filling silence (discount).
  • Quote without dated next.

Key takeaways

  • Present the price confidently, as something normal, AFTER establishing value.
  • A price stated before benefits looks “naked” and high; after value, it looks justified.
  • Link the price to benefits and relativise it (per day, per user, vs the cost of the problem).
  • Structure a clear proposal; the salesperson's hesitation creates the customer's doubt.

48h Challenge — apply tomorrow

Prepare your recap + statement line (agreed value, total, usage value) and rehearse the silence after the number. For real: state, then count to 5 adding nothing.

Section exit checklist
  • I can state a price confidently after agreed value.
  • I can hold the silence without justifying or discounting.
  • I sent 1 quote with validity + dated next step.
Self-rating 1-5: do I back prices with agreed value?Self-rating 1-5: do I date each proposal instead of letting it drift?

Frequently asked questions

Should you state the price early or late in the interview?

As a rule, after establishing value — i.e. after discovering and arguing the benefits, not right at the start. The reason is simple: a price only makes sense relative to what it brings. Stated “naked”, before the customer has perceived your offer's value, it inevitably looks high (it has nothing to compare with but zero). Stated after the customer has understood and desired the benefits, the same price looks justified, even reasonable for what they get. That is why experienced salespeople “build value” before talking figures. Be careful, though, not to dodge the price question if the customer asks early: avoiding or stalling breeds mistrust. If asked the price too early, a good technique is answering honestly while steering back to value (“it depends on your needs, which I want to understand properly first so I can offer the most suitable solution — I'll give you a precise price afterwards”). The principle stands: value first, price second, but transparently and without clumsy evasion. And when the moment comes, state the price with confidence and without hesitation.

How do you answer when the customer says “it's expensive”?

This is the price objection, so frequent and important that a whole section is devoted to it (section 3.3) — here are the broad principles. First, don't panic or give in immediately: dropping the price at the first “it's expensive” is a mistake (it devalues your offer and destroys your margin). Next, dig: “it's expensive” is vague — expensive compared to what? A competitor? A budget? A perception of value? Understanding the true nature of the objection lets you answer it accurately. Then, return to value: recall the concrete benefits, link the price to what the offer brings, relativise (cost set against gain, duration, cost of the unsolved problem). Often, “it's expensive” really means “I don't yet perceive enough value” — a signal to argue value better, not necessarily to cut the price. A high price well justified by value defends itself very well. The key is confidence in your offer: a salesperson convinced their price is justified defends it firmly, while a salesperson who doubts collapses at the first “it's expensive”. Section 3.3 details techniques for defending price and margin without giving in too fast.

Check your understanding

Younes states the price then justifies and discounts at once. What is the mistake?

Additional resources (optional, to go further)

Level 2 examFresh, harder questions to test what you've learned