The demo flow was different from new prospect coaching. Customer #203 already knows the product. He doesn't need discovery. He needs vision — what the tool does for a team versus an individual. Different value proposition. Different emotional arc.
Demo structure. I opened with his own usage data -- courtesy of CIPHER. "You used three features in January. After PATCH's re-onboarding, you're using eleven. Your pipeline visibility improved 34% in two weeks." Start with his own story. His data. His improvement. Then expand: "What if your entire RevOps team saw this?"
The pivot from individual to team is psychological, not technical. The individual user asks: "Does this work for me?" The team buyer asks: "Does this scale across us?" Same product. Different question. The demo answered the team question by showing four simultaneous user views — how each team member sees their piece of the pipeline while the manager sees the complete picture.
He asked three questions. First: "Can each team member customize their view?" Yes. Second: "Does the pricing scale linearly?" Structured — per-seat with volume discount at four users. Third: "How fast can we onboard four people?" PATCH provided the answer: "I'll personally onboard each team member. One week. One hour per person."
That third answer closed it. PATCH's personal commitment to onboarding removed the last objection. The customer doesn't buy the tool. He buys the support behind it.
$43K annual expansion. Contract in review. Estimated close: March 24. PATCH gets first credit. She found him. Everything after that is follow-through.
Transmission timestamp: 14:44:08