📖 Business
Structured Pitching
Kazanjy dismantles the myth that great pitching is an innate talent and reframes it as a structured, learnable skill composed of three distinct competencies: presentations (telling the story), live demos (showing the product), and systematic objection handling (addressing concerns). Each competency has a repeatable structure that can be practiced, refined, and eventually taught to sales hires. The key insight is that every element of a pitch should be designed to advance the prospect through a specific mental journey — from problem recognition to solution understanding to urgency to commitment. Winging it is not a strategy; structure is.
2
Minutes
2
Concepts
+45
XP
1
How It Works
- The Presentation Arc — Kazanjy structures presentations around the sales narrative: open with the problem (establish relevance), present the before/after transformation, show social proof (who else uses this and what happened), and close with a specific ask. Every slide should advance one of these stages. Slides that do not serve the arc get cut.
- Live Demo Best Practices — Demos should show the product solving the prospect's specific problem, not tour every feature. Kazanjy recommends: (a) set up the scenario in the prospect's terms before touching the product, (b) show the "aha moment" within the first 2 minutes, (c) narrate what the product is doing and why it matters rather than describing UI elements, and (d) have a pre-built demo environment that never crashes.
- Objection Mapping — Before any pitch, catalog the 10-15 most common objections and prepare structured responses for each. Kazanjy categorizes objections as: budget ("too expensive"), authority ("I need to check with my boss"), need ("we already have something"), and timing ("not right now"). Each category requires a different response strategy.
- The Feel-Felt-Found Pattern — For handling objections in real time: acknowledge how the prospect feels ("I understand that concern"), reference how others felt the same way ("Other VPs of Engineering initially felt the same"), and share what those others found after engaging ("What they found was that..."). This pattern validates the objection while redirecting.
- The Specific Ask Close — Every pitch must end with a specific, time-bound next step. Not "let me know what you think" but "Can we schedule a 30-minute technical deep-dive with your team lead this Thursday?" Kazanjy emphasizes that the ask should be the smallest reasonable next commitment, not a leap to a signed contract.