The Questions You're Not Asking in District Meetings

Many EdTech founders think discovery is about gathering information. They go into a meeting, ask a few questions about the district's needs, take a few notes, and then move on to the presentation. Discovery done.

But that's not real discovery. That's just going through a checklist.

Real discovery is when your relationship with the district either begins to grow, or it doesn't. This is the moment when the administrator decides if you really care about their situation or if you're just another vendor following a script. That choice happens early and shapes everything that comes next.

Asking questions is not the same as listening

Most founders do ask questions during a discovery meeting, and that's not the issue. The issue is what they do while the administrator is answering.

If you're listening while planning what you're going to say next, or waiting for a pause so you can connect their answer to a feature, you're not really listening. The administrator can feel that. They'll give you shorter, surface-level answers and keep the conversation pleasant but guarded.

Listening means focusing on what someone is really saying, repeating it back to check your understanding, and then asking a follow-up question based on their answer, not just what you planned to ask next. That's how real conversations start.

The administrators I've worked with over the past 40 years all say the same thing. They trust the vendors who listen before presenting. It's simple, but it takes discipline, since it's natural to want to solve the problem before you really understand it.

The questions you ask determine the answers you get

There's a big difference between asking, "Are you happy with your current solution?" and, "What challenges are you running into with your current approach?"

The first is a closed question. It gets a yes or no, and then you have to figure out what to do next. The second is open-ended. It encourages the administrator to talk, and what they share gives you real insight.

Open-ended questions usually start with "how" or "what." Here are some examples:

"What's driving this project for your district?"

"How is this affecting your teachers on a daily basis?"

"What would a successful outcome look like from your perspective?"

These questions aren't complicated. They're clear and simple. But they do something closed questions can't: they give the administrator room to share what's really happening, not just agree or disagree with your assumptions.

Going deeper with anxiety questions

There's a kind of question that most salespeople never learn, but it's one of the most useful tools in discovery. They are known as anxiety questions.

Anxiety questions are designed to surface concerns that administrators usually keep to themselves. These might be worries about internal resistance, past failures with similar products, pressure from the board, or doubts about whether their team can handle something new.

These concerns don't come up with standard questions. You need to make room for them. Here's how you might ask:

"Is there anything about this process that concerns you that we haven't talked about yet?"

"What would need to be true for you to feel confident moving forward?"

"Has the district tried something like this before, and how did that go?"

When an administrator shares something they've been holding back, two things happen. First, you get information that completely changes how you position your solution. Second, the administrator trusts you more because you gave them the chance to say what was really on their mind. That trust is what separates a vendor from a partner.

Discovery is an investment, not an expense

Many founders feel discovery slows them down. They want to get to the presentation because that's where they feel most confident. And there's always pressure to move things along, especially when you're trying to close deals and grow a business.

But the time you spend on discovery is worth it. Each question that uncovers the real problem makes your proposal better. Every concern you address early is one less objection to handle later. And when you listen well enough for the administrator to be heard, you build trust that competitors can't match with just a better presentation.

The founders I work with often say that the deals where they spent the most time on discovery were actually the easiest to close. The sales cycle didn't get longer—it got shorter, because there was less back-and-forth on the proposal. Everything important had already been discussed.

Three words that change the conversation

If you're not sure where to start with discovery, there's a simple phrase that works every time: "Help me understand."

"Help me understand what's behind this project."

"Help me understand how your team is handling this right now."

"Help me understand what a good outcome looks like for you."

It works because it's not a demand—it's an invitation. It shows the administrator you're not there to prove anything, but to learn about their situation. That's the foundation of every district deal that closes well.

The real cost of skipping discovery

When you rush or skip discovery, you end up guessing what the district really needs. Your proposal is based on assumptions, not real conversations. The administrator, who never felt heard, won't have a strong reason to choose you over the next vendor.

Most founders who struggle to close district deals don't have a product problem. They have a discovery problem. And the good news is that it's a skill you can learn.

If you want to get better at this, send me a message. I'm happy to chat.

#EdTech #K12Education #SellOnValue #EdTechSales #DistrictSales