The next step isn’t a nice-to-have at the end of a discovery meeting – it’s the legs of the table, the wheels of the car. Without it, nothing moves. Your job in a discovery meeting isn’t done when the conversation ends. It’s done when you’ve bridged that conversation to the next value-building stage of your buying process – with a specific action, owned by someone, with a date attached. Not “I’ll be in touch to schedule something.” A date. In the diary. Before you leave the room. That’s when things stop slipping through the cracks.
Why this is harder than it looks
- Most engineers go into discovery meetings with their solution already in mind. They’re thinking about what they want to present rather than what they need to learn. So they listen just enough to find an opening, then they start explaining. The customer feels diagnosed without being understood. Trust doesn’t build. And without trust, nobody agrees to anything meaningful at the end.
- Engineers often confuse a good conversation with a productive one. The meeting felt positive. The customer was friendly. There was plenty of nodding. But nobody asked the hard questions – what does this problem actually cost you? What happens if you do nothing? What would need to be true for you to move forward? Without those questions, there’s no buying tension, and without buying tension, there’s no next step.
- Logic makes us think. Emotion makes us act. Engineers default to logic – technical detail, specifications, methodology. But buyers make decisions emotionally and justify them logically afterwards. A discovery meeting that never connects with how the customer feels about their problem – the risk, the frustration, the career implications – will produce a polite “we’ll be in touch” rather than a committed next step.
What good looks like in practice
- Engineers who consistently end meetings with next steps treat discovery as a process, not a conversation. They have a structure they follow – not a script, but a proven sequence of conversational stages that ensures nothing important gets skipped. They know what they need to establish before they can propose anything, and they know what order to establish it in. That structure is learnable and repeatable – but it needs to be designed for your specific team and market, not borrowed from a generic sales model.
- The best discovery meetings are the ones where the customer does most of the talking – and leaves feeling that the engineer genuinely understood them. The questions that make this happen aren’t complicated: what have you tried already? What’s the cost of where you are now? What would success look like in six months? What would that mean for you personally? These aren’t sales tricks. They’re the questions a good engineer asks when they’re diagnosing any problem. Pointed at the commercial situation, they’re extraordinarily effective.
- Firms that get discovery right also get next steps right – because the next step emerges naturally from the conversation rather than being bolted on at the end. When both sides have genuinely explored the problem and the value of solving it, the question of what happens next answers itself. The engineer simply reflects back what they’ve heard and proposes the logical move: “Based on what you’ve described, it seems like the right next step would be X – does that feel right to you?” That’s not closing. That’s good engineering.
Where most engineering firms go wrong
- They go in with one solution and one agenda. The engineer has decided in advance what the customer needs. So the discovery meeting isn’t really discovery – it’s a presentation dressed up as a conversation. Customers feel this immediately. The questions feel leading. The listening feels selective. And when the proposal arrives, it doesn’t quite fit – because the engineer never found out enough to make it fit.
- They skip the value conversation entirely. They explore the problem well enough, then jump straight to options and pricing. But the customer hasn’t been helped to feel the cost of where they are, the value of where they could be, or the risk of doing nothing. Without that, any number you put in front of them feels like a cost rather than an investment. Price resistance almost always traces back to a discovery meeting where value wasn’t properly explored.
- They don’t have a shared conversational process. Different engineers run meetings completely differently. Some are great. Some are painful. And nobody is coaching the gap because nobody has agreed on what good looks like. The firms that improve fastest are the ones that design a conversational framework together – with specialist input – and then coach it consistently, one behaviour at a time.
Where to start
Before your next discovery meeting, write down one sentence: what do you need to learn in this conversation in order to propose the right next step? That single question changes how you listen. Instead of waiting for an opening to present, you go in genuinely curious about the customer’s situation – their problem, what it costs them, what good looks like from where they’re standing. That shift in intent changes the whole dynamic of the meeting.
Know your typical next steps before you walk in. For your business, what does the buying journey usually look like after a first conversation? A proposal? A site visit? A diagnostic? A second meeting with a wider team? Having a mental map of your usual process means you can steer toward a logical next step rather than improvising one under pressure at the end. That said, stay flexible – every customer is different, and the best engineers can read the room and adapt when the situation calls for something different.
And when you agree a next step – get the date in the diary before you leave. Not “I’ll send some dates over.” Not “let’s find a time next week.” A specific date, agreed in the room, with both parties’ calendars open. This is the single most common place where good discovery meetings unravel. The conversation goes well, both sides are aligned, and then three weeks pass because nobody pinned down a date while they were still in the room together.
Then after the meeting, ask yourself two questions. Did the customer do most of the talking? And did the meeting end with a specific next step, owned by someone, with a date? If the answer to either is no, that’s your starting point for improvement. Not a training course – just a conversation with your team about what happened and what you’d do differently. Do that consistently and the quality of your discovery meetings will improve faster than you’d expect.
The thing worth checking in your business
Ask your team to recall their last three customer meetings and answer honestly: in each one, did the customer leave with a specific, dated, owned next step? Not a vague “we’ll speak soon” – a real commitment. If fewer than two out of three have that, your discovery process has a gap. The good news is that gap is almost always a process problem, not a people problem. Your engineers aren’t bad at meetings. They just haven’t been given a framework that helps them steer a conversation to a natural conclusion. That’s fixable – with the right structure and the right coaching approach behind it.
Want to know where your team actually stands?
Use the free commercial diagnostic tools to find out exactly where the gaps are in your team’s sales effectiveness, and what to do about them. Takes 10 minutes. The report is specific and actionable.