The first call should answer one question: is there a business problem worth solving together?
A practical structure
1. Set the agenda
I’d like to understand what prompted the conversation, how the process works today, where the friction is and what that means commercially. If there is a fit, we can then discuss what a sensible next step looks like.
2. Understand why now
Ask:
- What prompted you to look at this now?
- What has changed?
- Who is pushing for improvement?
3. Understand the current state
- Walk me through what happens today.
- Where does the process slow down or break?
- What work is still manual?
- Where do people rely on workarounds?
4. Quantify consequence
- How often does that happen?
- Who is affected?
- What does the delay or error cause downstream?
- How much time is spent on this?
- If nothing changes over the next 12 months, what happens?
5. Understand previous attempts
- What have you already tried?
- Why has the problem persisted?
- Is the constraint technical, operational, behavioural or organisational?
6. Qualify the decision
- Who owns this problem?
- Who else needs to be involved?
- Is there a deadline or critical event?
- What would a successful next step need to prove?
Pain versus inconvenience
A process can be annoying without being commercially important. Look for consequence: lost capacity, slow revenue, poor service, avoidable cost, risk, rework or inability to scale.
Do not force AI into the conversation. A good outcome may be process redesign, integration, rules-based automation or a decision not to change anything yet.
Close clearly
Summarise what you heard, confirm the problem in the client’s language and agree one concrete next step with an owner and date. 
