top of page
Search

Specific Problem Detail Closes; Generic Pitch Doesn't

Aug 15
2 min read

We've been running calls on exterior remodeling for the past few weeks, and we're seeing a clear pattern: when we lead with specific problems, we book. When we pitch generic services, we don't.


Here's what our data shows. Calls where reps mentioned quantified issues—a 20% discount tied to siding scope, the exact square footage of windows, deck repair needs for a specific property address—converted to meetings. One rep brought up a previous quote context and a referral structure. Another specified AI gateway controls and governance challenges. Another called about a deck repair for a Maryland property. All booked.


The calls that stalled? They led with what we do, not what the prospect needs. We see "follow-up required" or cancellations when the pitch stays abstract. One prospect agreed to a 10 AM appointment for a "proximity program" quote, but when the rep mentioned a 45-minute duration during confirmation, the prospect cancelled. The detail that killed it wasn't the scope—it was that we packaged it generically. He had an objection, but we hadn't shown him why those 45 minutes mattered to his deck repair.


We're averaging 650-second calls on the booked ones. That's roughly 11 minutes of actual conversation. In that time, the winning reps are doing one thing: they're showing they've done homework. They reference the last inquiry. They mention the location. They talk about the specific problem, not the service category. Jackie Chisley heard "20% off and here's a referral fee structure." Ramsey El-Fakir heard "AI governance controls for your team and clients." Dallas Marshall heard "deck repairs for your Maryland property." None of them heard "we offer services."


Why does this work? Because specificity is proof. It proves we've looked at their situation. It proves we're not blasting the same pitch to everyone. When we show we know something about them—their problem, their location, their constraints—they believe we can solve it. Generic pitches sound like we called them by accident.


The practical shift for us: we've stopped leading with company value. We lead with prospect context. Before calling, the rep pulls the previous inquiry, the property address, any notes on what broke or needs fixing. On the call, that goes first. The discount, the program, the timeline—all of that comes after we've positioned it against their specific problem.


This isn't about being slick. It's about being honest. We're not offering them a service. We're offering them a solution to something we know they care about. The ones who book are the ones who feel that difference.


We're seeing this shift our close rate. Our team isn't doing anything different except leading with specifics instead of generics. Same script framework, same discount strategy, same follow-up process. The only variable is whether we mention what they actually need before we mention what we sell.


The takeaway: prospects don't book generic. They book when you show you understand their problem. Do the homework. Name the problem. Then make the offer.

Related reading

 
 
 

Recent Posts

See All
Fintech CTOs Evaluate Multiple Gateway Vendors

We're seeing a pattern in recent calls that changes how we should position our AI gateway solution. CTOs at fintech companies aren't asking us to prove we're the answer. They're asking us to participa

 
 
 
Compliance Budgets Don't Block Demo Bookings

We closed four demos this week from compliance and engineering leaders. Three of them explicitly told us they had zero budget authority for the next two years. That should sound like rejection. Instea

 
 
 
Qualify Build-vs-Buy Before Pitching AI Gateways

We tracked a pattern across calls this week that's shifting how we qualify prospects for AI gateway solutions. Multiple reps connected with engineering teams at scaling companies. Some booked meetings

 
 
 

Comments


bottom of page