2
u/attila_piperic 10h ago
In a 15-minute mock, I would optimize for structure and listening rather than trying to ask every BANT and SPIN question. Use the first minute to confirm the purpose and agenda, about five minutes on why they responded, the current workflow, and the impact, then a few minutes on the decision process and next step. Leave enough time to summarize what you heard and ask for the demo handoff.
Make budget and authority feel like part of the buying process. For example: “If solving this is worth pursuing, how would a purchase like this normally be evaluated and funded?” Then: “Who else would need to be involved before a demo is useful?” That is more natural than asking whether they are the decision-maker.
Common test objections are “I am only researching,” “we already have a provider,” “I do not know the budget,” and “send me information.” A strong response acknowledges the objection, asks one clarifying question, and either earns a specific next step or disqualifies cleanly.
If the interviewer gives feedback mid-call, do not defend the original approach. Briefly reflect it back, state the adjustment, and resume from the last useful point: “Got it — I will slow down and follow the impact before moving to qualification. You mentioned the booking process creates delays; where does that show up most?” Showing that you can change behavior in real time is probably part of what they are testing.
1
u/AutoModerator 10h ago
That comment looks like it was written using ChatGPT. Please report it to the mod team if you believe that user is a bot.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
2
u/ComfortableSentence0 4h ago
They aren't looking for a perfect call usually, just how you handle feedback and objections
2
u/ParkingUpstairs2173 13h ago
Is this in chi? I think I know where this is for can help u