Blog/Craft

A product demo developers watch to the end

Build it around one outcome, show the real product, keep one honest limit, and plan it in beats so the proof arrives early.

Kevin Blanco··6 min read·Evaluation

The short answer

A product demo developers watch to the end is built around one outcome. It shows the real product with a real cursor, one honest limit and one next step, in two to four minutes, with the proof inside the first two. Plan it as beats with a time for each, and cut whatever delays the proof.

01

One outcome

Pick the result a developer evaluating you wants to see, and let every minute serve it. A list of features is a tour, and viewers leave tours early.

"This is how to get webhooks failing in staging to behave like production" is a demo. "Here's our dashboard, and here's our settings page" is a tour. Developers can tell within seconds which one they're watching.

FigureA two-minute demo in five beats. The proof starts early. Durations are an example.

02

Plan it in beats

Name each part and give it a time before you record. The sheet adds them up and tells you when the proof arrives.

The beat sheet

Does the demo fit?

Change the names and the seconds. The bar shows the whole video.

  1. 0:00s
  2. 0:10s
  3. 0:35s
  4. 1:30s
  5. 1:50s

2:00 of 4:00

The proof starts at 0:35

It fits. Check that every beat earns its seconds.

03

The first ten seconds

The usual opening

"Hi, I'm Sam from Acme. In this video I'll show you our platform and some of its features."

The opening that keeps them

"This is a webhook that fails in staging and works in production. Here's how to make them behave the same."

Introductions can wait until the viewer has a reason to care who you are.

04

What to leave in and out

Do

  • One outcome, shown start to finish.
  • The real product, with data that looks real.
  • One honest limit, said plainly.
  • One next step, with the link under the video.

Don't

  • A tour of every menu.
  • Narration that reads out what's on screen.
  • A long intro before anything runs.
  • A call to action that asks for a purchase.

05

Check before you ship

The test

Would a developer finish it?

Tick every question you can answer yes to.

Not yet

0 / 5

Pick the one outcome first, then plan the beats around it.

FAQ

Questions people ask

How long should a product demo video be?

Two to four minutes is the range we aim for, with the proof inside the first two. Longer demos lose viewers who only wanted to see one thing work.

What should a developer product demo show?

One outcome, start to finish, in the real product: the setup that's needed, the run, one honest limit, and one next step they can take.

Should a demo show the product's limits?

One, yes. It makes the rest of the demo more believable to a developer who is comparing you with alternatives.

How do I start a product demo?

With the outcome, in the first ten seconds, ideally with the product already on screen. Save introductions until the viewer has a reason to care.

What call to action should a demo have?

A step the viewer can take now: the sandbox, the quickstart or a repo. Asking for a sales call at this stage asks for too much.

DevReel

How we do it at DevReel

We plan every demo as beats with a time on each, before anyone records. The proof comes early, the limit stays in, and the next step is a link under the video.

Cloudinary's videos usually average around 400 views. Ours passed 9,000 in the first week. For ngrok, watch hours tripled and subscribers went from about 450 to over 800 in the first week.

Cloudinary views

9,000+

in the first week, against a usual ~400

ngrok watch hours

3×

subscribers from ~450 to 800+ in the first week

Now the hard part

Tell us what a developer should see in your demo and we'll plan the beats.

Kevin Blanco founded DevReel. He has made 500+ developer-tool videos and spoken at 80+ developer conferences.

Keep reading