2.4The pitch: CAB & SONCAS
The essentials in 30 seconds
- SONCASed CAB: each feature translated into an advantage then into a benefit for THIS specific customer.
- Mandatory proof: numbers, peer testimonials, demos, guarantees — without proof, an argument is an opinion.
- 3 max spoken: 3 CABs aligned on the dominant SONCAS, the rest in appendix — 15 arguments dilute, 3 hit.
Threaded mini-case — Younes no longer unloads 15 features
Armed with his discovery (dominant Security + Money: no more lost quotes, no downtime), Younes, B2B sales rep selling equipment in Algiers, prepares 3 targeted CABs instead of 15 loose features: encryption → intact files → 0 customer leaks, 7-day support → 10-minute answers → no downtime, free migration → 0 downtime days. Each argument carries its proof, including a same-industry peer. He concludes: “which speaks to you most?”
Continues the 2.1-2.3 case — Younes turns discovery into 3 concrete arguments.
1. FAB: calibrated ammunition
Feature → Advantage → Benefit (SONCASed!) : « real-time sync (F) → your files everywhere (A) → never a lost version before a customer (B-Security) ». Pitching means translating each feature into this customer's SONCAS benefit.
2. Proof: the concrete of argument
Numbers (customers, ROI), testimonials (the prospect's peers: same industry), demos (make them touch, not hear), guarantees (trial, take-back). An argument without proof is an opinion; with proof, a fact. 3 concrete arguments beat 10 features.
3. Target: 3 arguments, not 15
The customer's dominant SONCAS → 3 aligned FABs, the rest in appendix. Fifteen arguments dilute; three hit. Ask « which speaks to you most? »: the customer ranks, you adjust.
🔎 Concrete example — 🔎 Concrete example — 3 FABs that sign
Security + Money customer (discovery):
1. Encryption (F) → files intact even if stolen (A) → 0 customer leaks (B)
Proof: “firm X: 0 incidents in 2 years”
2. 7-day FR support → 10-min answer → no downtime (B)
3. Free migration → 0 downtime days (B)
→ “which speaks to you most?” → #1 → dig inTakeaway: each FAB targets SONCAS.
Lesson: the rest in appendix, never spoken.
Section vocabulary
- Pitch
- Presenting the offer linked to the discovered need, focused on benefits for the customer.
Simple example: Younes links each CAB to the lost quotes discovered in 2.3.
What it is not: reeling off the same generic pitch for everyone.
Reflex: no argument without a discovered need behind it.
- CAB
- Characteristic → Advantage → Benefit method: turning an objective fact into a concrete benefit for this customer.
Simple example: Real-time sync → files everywhere → never a lost version again.
What it is not: stating the technology assuming customers will connect it themselves.
Reflex: “so what does it change for THEM?”.
- Benefit
- What the offer concretely brings the customer given their need (what convinces, more than characteristics).
Simple example: “0 downtime days during migration” speaks to the customer.
What it is not: “our product has this tech” meaning nothing to them.
Reflex: end each argument with the customer gain.
- SONCAS
- The buying-motives grid: Security, Pride, Novelty, Comfort, Money, Sympathy.
Simple example: Younes targets Security (0 leaks) + Money (0 downtime, ROI).
What it is not: serving the same pitch to Security and Money alike.
Reflex: spot 1-2 dominants in discovery, align CABs to them.
- Buying motive
- The psychological driver pushing a customer to buy, to identify to adapt the pitch.
Simple example: The customer wants reassurance (Security) and returns (Money).
What it is not: believing everyone buys for the same stated reason.
Reflex: ask “which speaks to you most?”.
In practice — Hands-on — Pitch with FAB and SONCAS
- Turn each characteristic into a benefit with CAB: Characteristic → Advantage → Benefit for THIS customer.
- Always link the benefit to the real discovered need (not a generic pitch).
- Identify the customer's buying motives with SONCAS (Security, pride, Novelty, Comfort, money, Sympathy).
- Adapt your pitch to the dominant drivers (e.g. reliability/guarantees for a “Security”, ROI for a “Money”).
Ready-to-say script — 3 CABs with proof (1 min)
“For your lost quotes: first encryption, so your files stay intact even if stolen — result, 0 customer leaks, like firm X: 0 incidents in 2 years. Then 7-day support, answers in 10 minutes — no downtime. And free migration — 0 downtime days. Which speaks to you most?”
One CAB = one proof; get the customer to rank before digging into the favourite.
Copy-paste template — SONCASed CAB card
DOMINANT SONCAS: _______________
CAB 1: C _______________ → A _______________ → B _______________
PROOF 1: _______________
CAB 2: C _______________ → A _______________ → B _______________
PROOF 2: _______________
CAB 3: C _______________ → A _______________ → B _______________
PROOF 3: _______________
REST IN APPENDIX: _______________Security customer
Stress reliability, guarantees, peer references: reassure before seducing with novelty.
Money customer
Translate each CAB into ROI: problem cost vs gain, per day or per user.
SME in Algeria
Younes picks local proof (same-industry peers) that speaks louder than distant numbers.
Technical product
No characteristic without translation: each technology ends as a concrete benefit for THIS customer.
✓ Best practices
- SONCASed FAB always.
- Proof per argument.
- 3 max spoken.
✗ Common pitfalls
- Bulk features.
- No proof (opinions).
- 15 arguments (dilution).
Key takeaways
- Customers buy benefits, not characteristics: that is the point of the CAB method.
- CAB: Characteristic → Advantage → concrete Benefit for THIS customer, linked to their discovered need.
- SONCAS lists six buying motives: Security, pride, Novelty, Comfort, money, Sympathy.
- Adapting the pitch to the customer's dominant motives (identified in discovery) makes it punchy.
48h Challenge — apply tomorrow
Take your real offer: write 3 SONCASed CABs + 1 proof each with the template above. Test them on a customer and note which speaks most.
- I can turn any characteristic into a SONCASed CAB.
- I can prove each argument (no opinion without fact).
- I have 3 CABs ready + 1 noted customer ranking.
Frequently asked questions
What is the difference between a characteristic, an advantage and a benefit?
This is the distinction at the heart of the CAB method, and mastering it radically changes how effective a pitch is. The characteristic is an objective fact about the product (“this engine has 150 horsepower”, “this software syncs automatically”) — neutral, it doesn't “sell” by itself. The advantage is what that characteristic makes possible in general (“so more power”, “so no double entry”) — better, but still generic. The benefit is what it concretely brings THIS specific customer, given their discovered need (“in your case, it would let your overstretched team gain two hours a week”) — that is what convinces, because the customer pictures themselves and sees the point for them. The beginner's mistake is stopping at the characteristic (“our product has this tech”) assuming the customer will connect it to their interest themselves — which they don't. The golden rule: never state a characteristic without translating it into a concrete benefit for this customer. A good salesperson constantly thinks “so what, what does it change for them?”. That translation is what separates a technical unloading (which bores) from a pitch that sells (which speaks to the customer). And a benefit only truly hits home if linked to the real need — hence the importance of discovery.
Isn't SONCAS a bit reductive for sizing up a customer?
It is a grid, so inevitably simplifying — but very useful as a practical tool, provided you don't apply it mechanically. SONCAS (Security, pride, Novelty, Comfort, money, Sympathy) offers a repertoire of the main buying motives that helps you avoid pitching “at random” and adapt your message. Its strength: reminding you that different customers buy for different reasons, and that the same product must be presented differently per person (reassure a security-minded customer; talk profitability to a price-sensitive one; etc.). Its limits: a real customer is more complex than a single letter — they often combine several motives (e.g. Security and money), with shifting dominants. SONCAS is therefore not a box to lock people into, but a guide for spotting the dominant drivers (through discovery) and adapting your pitch to them. Other grids exist (SONCASE with Ecology, etc.), and the key remains listening: it is by truly understanding the customer (section 2.3) that you identify their real motives, with SONCAS structuring that reading. Use it as a compass, not a cage. Handled well, it makes a pitch far more personalised and effective than one single speech served to all.
Younes lists 15 features spoken with no proof. What is the effect?