Sales for Geeks, or How to Frame Suggestions, Questions and Requests
summary
Argues sales is positive persuasion not trickery and that developers should learn psychology and debate techniques instead of chasing a new language. Uses mental models, business analysis and silence as tools, emphasizes features vs benefits when pitching. Gives concrete wins: fixing a form saves an employee ~20% time worth roughly $10–20k annually, converting unused suites into six‑week offices fills rooms and brings revenue, and quiet listening prevents needless discounting.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:57What is Sales
- 3:07Sales is not a zerosum game
- 6:40Sales is about persuasion
- 8:45You have value
- 10:55We love to hack
- 16:40Sales example
- 20:09Cognitive biases
- 21:54Personal beliefs
- 23:51Features vs benefits
- 25:38Joes background
- 26:47Hotel Sales
- 28:11EdgeCase Sales
- 30:40The art of shutting up
- 31:08Perfect example
- 33:20Metaprogramming
- 37:00What helped you turn the corner
- 38:05Marketing vs Sales
- 39:25Shutting Up
- 40:20The Magic Answer
- 41:45The Right Solution
- 43:27How to convince people to go to hourly
related talks
36mThe Developer's Model for Talking to Managers
43mGetting Past No: The Science of Moving Others
50mTalk to Me Nicely - How to Communicate Your Ideas and Speed Up Your Career
34mYou're a problem solver
39mSomone is Wrong
14mThe Art of Persuasion
32mHow to Present Ideas So That Your Client Will Listen
55mImprove your thinking, improve your software