Kickoff Call Questions for SEs: What Great Kickoff Calls Sound Like

It’s 10:02am on a Tuesday. You’ve just joined the kickoff call two minutes late because the previous one overran - the one with the prospect who wanted to talk about their data lake for forty minutes. You’re muted. You’re scanning the account brief the AE sent at 9:41am, which is three bullet points and a LinkedIn profile. The AE is already talking. Something about “really excited to explore how we can help.” You unmute to say hello. You mute again.

Forty-five minutes later, the call ends. The AE messages you: “Great call! I think they’re really engaged.” You look at your notes. You have the prospect’s name, their job title, and the word “Salesforce” circled twice. You have two weeks to build a demo.

This is not a disaster story. This is a normal Tuesday.

The problem isn’t that SEs don’t know what to ask on kickoff calls. Most of us have been doing this long enough to have a mental list of decent questions. The problem is subtler: we’re optimising for the wrong moment. We’re trying to sound competent on the call itself - asking smart-sounding questions, demonstrating technical fluency, being a Good SE - instead of engineering the conditions that make everything downstream actually work.

I want to walk through what’s really happening inside an SE’s head during a kickoff call. The options weighed, the change directions made, the things deliberately left unsaid. Because the difference between a kickoff that sets up a winning demo and one that sets up a polite waste of everyone’s time isn’t about scripts. It’s about the invisible decisions happening in real time.

Why Most Kickoff Calls Fail to Set Up the Demo

Most kickoff calls fail because the SE treats them as information-gathering sessions. Collect requirements, note the tech stack, confirm the timeline, say something about APIs. Job done. Except it isn’t, because you walk away with a shopping list of features to show and no idea what story the demo needs to tell.

The goal of a kickoff call isn’t to collect information. It’s to build alignment about what this deal is actually about - the real business problem, the internal politics shaping the decision, what winning looks like for the specific human being on the other end of the call. Without that, you’re building a demo on assumptions. And assumptions are what produce the dreaded “this is really impressive, but it’s not quite what we were looking for” email three weeks later.

Research suggests that many buyers describe vendor demos as not relevant to their actual needs. That gap almost always traces back to a kickoff call where nobody asked the right questions.

There’s a structural tension on every kickoff call that nobody talks about openly. The AE wants momentum - they’ve worked to get this meeting, they want it to feel warm and productive, they do not want their SE turning it into a cross-examination. The SE wants signal - enough real information to build something that actually lands. And the prospect, if they’re even on the call, wants to feel heard without being subjected to what feels like a requirements workshop.

These three agendas collide in the first fifteen minutes. Most SEs default to the path of least resistance: stay quiet, let the AE drive, ask a couple of polite questions near the end, take notes that are mostly paraphrases of what the prospect already said.

Here’s the decision tree an SE actually faces in the first five minutes:

I worked with an AE once - Marcus, good bloke, relentless closer - who used to run kickoff calls like they were already the closing call. By the time I got a word in, the prospect had been told about six capabilities they hadn’t asked about and were nodding politely in the way people do when they’ve stopped listening. The demo I built from that call was technically flawless and completely irrelevant. We lost the deal to a competitor whose product was worse but whose demo addressed the one thing the prospect actually cared about, which Marcus had talked over in minute seven.

The dead end worth mentioning: some SEs overcorrect and try to do deep technical discovery on a kickoff call. Full architecture review, integration mapping, the lot. You lose the room. The prospect came expecting a conversation, not an audit. The kickoff call is for orientation, not excavation.

What Questions Should an SE Actually Ask on a Kickoff Call?

The best SE questions on a kickoff call aren’t technical. They’re diagnostic. You’re trying to answer three things: What does failure look like for this person? What have they already tried? And who else has a stake in this decision?

Everything else - the stack questions, the integration questions, the timeline questions - is secondary until you have those three answers. Not unimportant. Secondary.

What Does Failure Look Like?

“What does failure look like” is load-bearing because it surfaces the real risk the buyer is managing, which is almost never the opportunity they’re describing. Someone who says “we want better visibility for our reps” might actually mean “my VP thinks our pipeline numbers are fiction and I need to prove they’re not before Q3 review.” Those are very different demos.

What Have They Already Tried?

“What have they already tried” tells you whether you’re selling against a bad prior experience with a similar tool, internal inertia from people who’ve given up on solving this, or a specific competitor who got close but didn’t land. Each of those requires a completely different approach.

Who Else Has a Stake?

“Who else has a stake” tells you whether the person you’re talking to can actually say yes, or whether they’re a champion who still needs to sell this internally. If it’s the latter, your demo isn’t for them - it’s ammunition for a meeting you won’t be in.

Research suggests that top-performing SEs ask business-context questions earlier in the call than average performers, who tend to lead with technical qualification. The sequence matters as much as the questions themselves.

Now contrast those with what SEs typically ask first: “What version of Salesforce are you on?” “Do you use SSO?” “How many users would be on the platform?” These matter. But asked too early, they telegraph something specific to the prospect: this person is already configuring a demo in their head. They’re not trying to understand my problem. They’re trying to fit my problem into their product.

The Real-Time Decision

Let me show you what this looks like in practice. Not a polished script - the actual messy decision happening in real time.

The prospect says: “We’re looking for something that integrates with Salesforce and gives our reps better visibility into their accounts.”

The SE’s internal monologue, in about two seconds: Do I ask about the Salesforce setup now? That’s comfortable territory. I know Salesforce. I can sound smart about Salesforce. But if I go there, we’ll spend ten minutes on API versions and object models and I still won’t know why visibility is the problem.

So instead: “When you say visibility - what’s happening today that makes that hard? Like, what does a rep actually do on a Monday morning when they don’t have it?”

That question delays the technical rabbit hole. It surfaces the workflow pain. And critically, it gives you something to anchor the demo to - a specific moment in a specific person’s week that your product can visibly improve. “Let me show you what Monday morning looks like with this” is a demo opening that lands. “Let me show you our Salesforce integration” is not.

The rejected alternative - “What version of Salesforce are you on?” - isn’t wrong. It’s just premature. Save it for the follow-up, or the pre-demo technical call, or even an email. It’ll keep.

Handling the Tension Between Sales and Technical Discovery

The SE’s job on a kickoff call isn’t to run discovery. It’s to protect the quality of the demo by ensuring at least one or two business-critical questions get answered. That’s it. One or two. Not twelve.

This means negotiating scope with the AE beforehand. And I realise “negotiating” makes it sound formal. It’s not. It’s a two-minute Slack message or a quick huddle before the call. But it has to happen, because when it doesn’t, you get the default: the AE runs the call based on their instincts, the SE gets one question in at minute thirty-seven, and the demo gets built on CRM notes that were written for the AE’s manager, not for you.

AE/SE misalignment on call ownership is frequently cited as a factor in lost deals - not because either person did something wrong, but because nobody agreed beforehand who was responsible for what.

I’ve seen CRM notes that said “prospect interested in analytics and reporting.” That could mean literally anything. That’s not a brief. That’s a horoscope.

The pre-call conversation doesn’t need to be complicated. What doesn’t work: “Can you send me the discovery notes?” That’s passive. You’ll get whatever the AE already has, which is whatever the prospect said on the first call, filtered through the AE’s interpretation, compressed into three lines of text.

What works better: “Before we jump on - I need to understand two things to make the demo actually land. Can I take five minutes on the call to ask about their current process and what success looks like for them specifically? I’ll keep it tight.”

That framing matters. You’re not asking for control. You’re asking for five minutes, with a clear reason, and a promise to be efficient. Most AEs will say yes to that. Some will say “let’s just see how it goes,” which is AE for “no.” In that case, you have options:

  1. Plant the questions through the AE (“you might want to ask them what they’ve tried before”)
  2. Push for a separate follow-up call before you build anything

The harder case - and I don’t have a clean answer for this one - is the AE who does no discovery at all and expects the SE to just figure it out from the demo request. “They want to see the platform, just show them the standard flow.” These deals have a success rate that I’d describe as aspirational. Your best move is to ask for a separate technical discovery call before you build anything, framed as “I want to make sure we don’t waste their time showing them things that aren’t relevant.” Sometimes you get it. Sometimes you don’t, and you build the best demo you can from three bullet points and a LinkedIn profile, and you hope.

What to Listen for That Most People Miss

The most valuable signal on a kickoff call isn’t what the prospect says they want. It’s the hesitation. The qualifier. The offhand comment that everyone, including the SE, treats as background noise.

“We tried something like this a couple of years ago.” “My team is… a bit sceptical about new tools.” “Our VP is really driving this.” Each of those sentences contains more useful information than twenty minutes of requirements discussion. And each of them typically gets noted as a single word - “prior experience,” “change management,” “exec sponsor” - and promptly forgot.

The cognitive load problem is real. On a kickoff call, the SE is simultaneously:

In that state, soft signals get filtered out. The brain prioritises concrete nouns - Salesforce, API, dashboard - over emotional texture.

But the emotional texture is where the deal lives. “We tried something like this before” might mean they got burned by a competitor’s implementation. It might mean there’s scar tissue in the organisation around this category of tool. It might mean the person talking to you championed the last attempt and is now putting their credibility on the line again. You don’t know which one until you pull the thread.

And pulling the thread is simple. You just say: “Oh, interesting - what happened?”

That’s it. Three words. Not a clever reframe, not a diagnostic question from a methodology playbook. Just genuine curiosity about what they just said. Most people - including most SEs - are so busy preparing their next question that they miss the answer to the current one.

I still get this wrong sometimes. I was on a call last month where the prospect said “we’ve had some internal pushback on this kind of initiative” and I wrote down “stakeholder alignment - follow up” and moved on to asking about their data sources. It wasn’t until I was building the demo three days later that I realised I had no idea what the pushback was about, who was pushing back, or why. I had to ask for another call. The AE was not thrilled.

The unsexy truth about kickoff calls is that they’re not about performing competence. They’re about creating the conditions for a demo that actually matters to the people watching it. And that work is mostly invisible - it happens in the two-minute Slack message before the call, in the decision to ask “what happened?” instead of “what version?”, in the willingness to sit with three unanswered questions rather than filling the silence with product talk.

Nobody will ever compliment you on a great kickoff call. They’ll compliment you on the demo that came after it.