aldi
MVP demo · 31 October 2026

The Demo Script

Two cuts: a 90-second trailer recorded in advance, and a three-minute live demo on stage. Both run on the same scenario engine, with mock data and a fast-forward clock.

Open the stageShipper windowBuyer windowConsole window

1 · Trailer, 90 seconds

screen capture + voice-over
  1. 0:00–0:06
    Logo motion
    Orange dot blinks on navy → the ring expands → orange fills the frame, cut (variant A from the branding sheet).
    On screen: 320 / 4,000
    Every day, an area of 4,000 orders sees about 320 deliveries fail on the first try.
  2. 0:06–0:18
    Landing · The problem
    Slow scroll across the four hero numbers; hold on 40,000 VND and 0 windows.
    On screen: 40,000 VND · 8–12% · 0 windows
    Sellers pay up to forty thousand dong to ship each one back. And the delivery time — the thing that decides whether a buyer accepts — is negotiated outside the system.
  3. 0:18–0:26
    /demo/shipper
    10:02, the shipper calls, no answer. Close-up of the thumb tapping “A · No answer”.
    With Alodi, the shipper taps one button.
  4. 0:26–0:36
    /demo/buyer
    The message lands in chat with quick replies. The clock fast-forwards 10:02 → 11:02.
    On screen: 10:02 → 11:02
    The agent messages at once, while the buyer is watching their phone. Sixty silent minutes later, it calls.
  5. 0:36–0:56
    /demo/buyer · call
    Incoming call under a verified name. Answer, let the call audio run with live captions.
    (Call audio) “Tomorrow after five, please. Leave it with security in Tower B — or call my wife.”
  6. 0:56–1:08
    /demo/console
    Fields appear one by one with confidence bars; the JSON bumps a version and the changed block lights up.
    On screen: 0.94 · 0.88 · 0.91
    The answer becomes structured data, each field with its own confidence. Confident enough, it applies itself. Ambiguous, it goes to a person.
  7. 1:08–1:20
    /demo/shipper
    The context card slides in. Cut to the next day, 17:22, tap Delivered.
    On screen: Time-to-context: 4 seconds
    Seconds later the context card is in the shipper’s app. The next day, the parcel reaches the right person, at the right time.
  8. 1:20–1:30
    Landing · Team → logo
    Glide past Team Develarper, end on the logo and tagline.
    Alodi. Make the second drop land.

2 · Live demo, 3 minutes

four speakers, one segment each
  1. 0:00
    Nomura Yoshio

    An area handling 4,000 orders a day sees about 320 fail on the first attempt. Each return costs the seller up to forty thousand dong. And Shopee still doesn’t let buyers choose a delivery time.

    Problem slide (or landing · The problem).
  2. 0:30
    Nomura Yoshio

    Three screens: the shipper app, the buyer’s phone, and the customer-service console. The demo clock fast-forwards: sixty minutes become six seconds.

    Open /demo, scenario “A · No answer”, turn Auto-tap off, press Play.
  3. 0:45
    Long Quan Ton

    The shipper arrives, calls, no answer. Instead of typing a note, he taps one button.

    Tap A in the shipper app.
  4. 1:00
    Long Quan Ton

    The agent messages right away. The buyer stays silent, so exactly sixty minutes later it calls — after the policy guard checks the time.

    Point at the “Call hours 08:00–20:30 · inside” chip.
  5. 1:15
    Khanh Tuong Huynh

    The buyer answers like people really do: time, drop-off and a stand-in receiver in one breath. The extractor splits it into fields, each with a confidence score.

    Tap Answer on the buyer’s phone and let the call run.
  6. 1:50
    Thanh Loi Tran

    Everything is above 0.85, so the agent applies it. The Order Context Object gets a new version, and the audit log shows who changed what.

    Point at the highlighted JSON block and the audit log.
  7. 2:05
    Long Quan Ton

    Four seconds after hang-up, the context card is in the shipper’s app. The next day, delivered.

    Let it run to Delivered (or press →).
  8. 2:20
    Khanh Tuong Huynh

    And when a buyer refuses at the door, the agent doesn’t call. It only suggests a label; a person decides.

    Pick “Refused”, speed 2x, press Play.
  9. 2:40
    Nomura Yoshio

    Two numbers are measured: accuracy and safe autonomy. Savings are always projected. Alodi — make the second drop land.

    Open /metrics.

Five scenarios in the engine

  • AA · No answerChat → AI call → context card → delivered
  • BB · RescheduledShipper’s 10-second voice memo → context card
  • —RefusedNo buyer contact, CS cuts losses
  • AA · Low confidenceVague answer → human review
  • AA · Two missed calls2 missed calls → hand to CS

Voicing the call

  • Assistant (AI)
    Warm female voice via TTS. The greeting and recording consent are pre-recorded.
  • Mr. Minh (buyer)
    A real person voicing it, natural and a little rushed.

Checklist before demo day

  1. 01Test the browser’s English TTS voice on the recording machine.
  2. 02Open /demo/shipper, /demo/buyer and /demo/console in three 1080p windows; they stay in sync. Press H to hide the controls.
  3. 03Turn Auto-tap on for the trailer, off for the live demo so the presenter taps.
  4. 04Silence OS notifications, set speed to 1x, press R before every take.
  5. 05Record a backup video of the full main flow in case the venue machine fails.
  6. 06Know the answers to the five questions in the landing FAQ by heart.

Keyboard shortcuts while recording

SpacePlay / pause
→Next step (skip waits)
RReset
HHide controls (single windows)