1/13
Looks like no tags are added yet.
Name | Mastery | Learn | Test | Matching | Spaced | Call with Kai | Chat |
|---|
No analytics yet
Send a link to your students to track their progress
OBJECTION 1: “NOT INTERESTED” / “NO NEED” / “DOESN’T APPLY”
“Totally fair.”
(pause)
“Just so I don’t misread that — is it because you don't have any bottlenecks in your company, or because I haven't given enough information for relevance yet?”
If They Say “Things Are Running Smoothly”
“That’s good to hear. Most teams we speak with felt the same way — until growth, volume, modernization, or audits exposed gaps they didn’t see early.”
(pause)
“As things scale, where does complexity usually show up first for you — if anywhere?”
OBJECTION 2: “NO TIME” / “TOO BUSY” / “CALL ME LATER”
“I figured — and I’ll respect that.”
(pause)
“I haven't given you enough information for you to see the true value here yet.”
(pause)
“If it did make sense, what's usually more open for you, mornings or afternoons? I’ll follow up”
If They Say “Maybe Later” (No Specifics)
“No problem — what would need to be in place for this to become a priority?”
OBJECTION 3: “NO BUDGET” / “TOO EXPENSIVE”
“Understood — budget always matters.”
(pause)
“Just so I’m clear, are you assuming this would be expensive, or are you already allocating budget elsewhere?”
Mandatory Reframe after Budget Objection
“Just to clarify — this isn’t a pricing conversation.
The intro is simply to see whether there’s even a problem worth solving.”
(pause)
“If there wasn’t a clear return, it wouldn’t go anywhere anyway.”
OBJECTION 4: “I’M NOT THE RIGHT PERSON”
“Got it — I appreciate you telling me.”
(pause)
“Who typically weighs in on operational or system decisions?”
OBJECTION 5: “SEND ME INFO”
Happy to.”
(pause)
“Just so I don’t send something generic — what should I focus on to showcase the true value we could bring with our guidance and connecting support?”
OBJECTION 6: “WE ALREADY USE [X]” / “WE’RE HAPPY WITH OUR CURRENT SOLUTION”
“That makes sense — most teams already have tools in place.”
(pause)
“What systems are you using right now?”
“We are a connecting an implementation layer for existing tools not a complete overhaul replacement”
Non-Threatening Reframe After We already Use X
“Our goal isn’t replacing tools — we’re connecting what’s already there.”
(pause)
“Do you have clear visibility across student acquisition, scheduling, instructor utilization, and operations in one place today?”
“WE’RE TOO SMALL”
“That’s actually when inefficiencies show up fastest — because there’s less margin for error.”
(pause)
“How many students or aircraft are you managing today?”
“WE’RE GROWING FAST / JUST EXPANDED”
“Seems like perfect timing then, that’s usually when things start to stretch.”
(pause)
“What’s feeling harder now than it was six months ago, and how are you handling modernization in the middle of expansion?”
“WE’VE TRIED CONSULTANTS BEFORE”
“That makes sense — a lot of teams have.”
(pause)
“What didn’t work last time?”
“JUST SHOOT ME A PRICE
“Its really based on what you want to get out of it, and your custom operation”
(pause)
“Im just the guy confirming whether there’s even something worth solving. Believe this, we only working in situations that make sense. Our founder always says he “only works in win-win situations, that’s how people work together long-term””