When this fits
- First or second meeting with a prospective client
- The client has sat through generic AI demos before and is skeptical
- The business has specific operational texture — not just "we want to use AI"
- There is time to listen for at least 60 minutes before showing anything
How it works
- Spend the first 60–90 minutes asking about the work itself — not about AI, not about pain points. What does an ordinary Tuesday look like? Where do hours go? What does the team complain about?
- Identify one workflow that has a specific shape — repeated, slow, prone to error, or quietly draining a senior person's time.
- In real time, sketch what a 20-minute AI demo of that specific workflow would look like. Not generic AI — the actual workflow, with the actual quirks.
- Show it. The demo runs short — twenty minutes — because the listening already did the work.
- Close on the conversation, not the tech. The retainer proposal writes itself because the client recognised themselves in the demo.
Why it works
Clients do not buy AI capabilities — they buy the feeling of being understood.
A generic demo is a product showcase. A specific demo, built from what the client
just told you, is proof the consultant listened. Conversion happens on the listening,
not the technology.
Worked example
A founder-led Thai garden retail SME ran a three-hour discovery meeting.
The first ninety minutes were about the business — supplier WhatsApp threads,
customer order ambiguity, inventory reconciliation done by hand on weekends.
The AI demo at the end was twenty minutes, focused entirely on the WhatsApp-to-order
workflow. The retainer proposal was drafted the same day.
Anti-patterns
- Showing a polished demo deck that wasn't built from this client's actual workflow
- Leading with capability statements ("Claude can analyse documents, generate text, search the web…")
- Treating the demo as the centrepiece — it is the closing artifact, not the opening move
- Skipping the listening because the AI tools "are already impressive enough"