
You are in a regular account call or QBR and want to find out whether there is a real next problem worth solving, without it feeling like a fishing expedition for your next deal
The safest expansion conversations start with something the customer said, not something you decided to pitch. When customers hear their own language reflected back, they feel understood rather than sold to. That shift - from vendor to advisor - is what makes them open to a recommendation at all. Discovery inside an existing account is different from new business discovery: the customer already has opinions, frustrations, and wishes. Your job is to surface them.
If you skip diagnosis and go straight to a recommendation, even a good one, the customer hears a pitch. They get defensive. They say they need to think about it. The conversation stalls and the relationship feels transactional.
You can run a short diagnostic conversation inside an existing account call that surfaces the customer's next real problem in their own words, giving you a natural, low-pressure opening to recommend an expansion if one fits.
Listen for 'I wish' and 'we still' phrases in every call. These are the customer telling you where the friction is. Write them down verbatim.
Ask one forward-looking question after reviewing recent wins: 'What is the next milestone your team is working toward?' Then stop and listen.
Ask one friction question: 'Where is the process still slower or more manual than you would like?' This surfaces bottlenecks without you having to guess.
Summarize what you heard before you say anything about your product: 'So it sounds like X is going well, and the main thing slowing you down now is Y - is that right?' Let them correct you.
Only move to a recommendation once they have confirmed the problem. The transition is: 'Given that, there are a couple of ways we could help - want me to walk through one option?'
After a quick recap of usage numbers, the AM says: 'We also have a reporting add-on that a lot of customers in your space are finding really useful. It gives you dashboards and automated exports. Would that be something worth exploring?'
The customer mentions in passing: 'We are still pulling the data manually every Friday for the leadership report.' The AM notes it and comes back to it: 'You mentioned the Friday report is still manual - how much time is that taking, and who owns it?' The customer explains the pain. The AM summarizes: 'So the core workflow is running well, but the reporting piece is still a bottleneck for your team every week.' The customer agrees. The AM then says: 'That is actually something we can fix - want me to show you how two other teams handled the same thing?'
You can run a short diagnostic conversation inside an existing account call that surfaces the customer's next real problem in their own words, giving you a natu
You have got it when your expansion recommendation uses at least one phrase the customer said earlier in the same conversation, and the customer responds with 'yes, exactly' rather than 'interesting'.
The safest expansion conversations start with something the customer said, not something you decided to pitch. When customers hear their own language reflected back, they feel understood rather than sold to. You can run a short diagnostic conversation inside an existing account call that surfaces the customer's next real problem in their own words, giving you a natural, low-pressure op
If you skip diagnosis and go straight to a recommendation, even a good one, the customer hears a pitch. They get defensive.
£7-10k flat fee. The methodology, delivered.
See Hire with Assessment