Building a working demo first

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

Understand how the business runs

The first 60–90 minutes: daily tasks, where time goes, and which tasks the team finds repetitive or error-prone.

Identify one workflow

One that is repeated, slow, error-prone, or consuming a senior person's time.

Plan a short demo of that workflow

Built from the client's own process, not a generic example.

Present the demo (~20 min)

Short, because it's based on the workflow already discussed.

Discuss next steps → proposal

A proposal follows because the demo addresses the client's real situation.

Why it works

A demo built from the client's own workflow shows that the work has been understood. This is more effective than a generic product demonstration, and most engagements begin this way.

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"

A working demo before any proposal

Understand how the business runs

Identify one workflow

Plan a short demo of that workflow

Present the demo (~20 min)

Discuss next steps → proposal

Discuss your situation with us