Binly demo · council meeting
90 seconds end-to-end · 6 steps · scripted recovery for AR misses
Before the meeting
Bring:
- iPhone with Binly installed (TestFlight) — battery ≥ 50%, screen on full brightness
- A printed sheet of your bin QR stickers (Settings → Integrity & audits → "View & print stickers")
- 3 props: Coke can / water bottle, banana or apple, paper newspaper or cardboard
- iPad or laptop showing the council dashboard (admin.html) for the data-side reveal at the end
- Printed pre-meeting brief, one per attendee
Test the demo 2x in private before walking in. The script below assumes the AR detector locks on each prop within 2 seconds. If it doesn't on prop #1, recover by saying "and barcode mode is always a tap away" and use that instead. Don't fight the demo.
The 6-step demo
1
Open the app, show the Home screen
Trust chip top-right shows 100. Streak chip shows current day. Today's main action: "Scan something to recycle".
~ 5 sec
Here's what a resident sees when they open Binly. Their trust score is here — it's how the council knows this household is reliable. Right now I'm at 100; we'll see it move in a moment.
2
Tap Scan tab → tap "Bin session"
Green CTA card opens the camera in full-screen Bin Session mode. Top bar shows "0 logged · Verify bin · Done".
~ 5 sec
This is the flow we built specifically for the "every item, no friction" problem. One tap opens the camera. Now I just hold each thing up.
3
Hold the Coke can to the camera (~30 cm, centred)
Hint: "Locking on Bottle…" → "Hold steady… 78%" → commit. Voice: "Bottle, Mixed Recycling, plus 12." Bucket chip flies in. Counter: 1 logged.
~ 4 sec
Recovery: If AR doesn't lock within 3 sec, say "Sometimes the AI needs a second angle" and rotate the can. If still no lock, tap Done, switch to Barcode mode, scan the can's barcode.
Notice — no taps. No "which bin?" picker. The app announces it out loud so the resident can keep their eyes on the bin.
4
Hold the banana to the camera
Voice: "Banana, Food Waste, plus 4." Bucket chip. Counter: 2 logged.
~ 3 sec
Different item, different bin, instant. No cool-down between different items. The resident binned two things, took five seconds total.
5
Tap "Verify bin · +trust" — point at the printed Recycling QR
Pill turns blue: "✓ Mixed Recycling verified." Voice: "Mixed Recycling bin verified." Now hold the cardboard up.
Voice: "Bottle, Mixed Recycling, plus 14" (verified +15% bonus).
~ 8 sec
Recovery: If QR scan times out, place the printed sticker flatter / closer. Worst case, manually claim verified mode by saying "we'll show this in the dashboard view instead" and skip to step 6.
Now I'm scanning the bin's QR sticker. This is Layer 2 of the integrity pipeline — every subsequent log is anchored to this physical bin. The points went up by 15% because the council now has provable per-bin attribution.
6
Tap Done → return to Home
Toast: "Bin session done — 3 items logged." Trust chip on Home has gone up (100 → still 100 since already maxed; mention that for previously-flagged households it climbs back to 100).
~ 5 sec
Three items binned, fifteen seconds, zero taps after the first. And this is just one household — at ward scale, the council gets the data view I'll show on this dashboard.
The follow-on (30 seconds, on the iPad/laptop)
Open admin.html in a browser. Show: ward-level recycling rate, contamination trend, top-offending items list. Frame as: "this is what the council never had before — per-ward contamination evidence by item type, available within hours not weeks."
The ask, at the end
Don't pitch the financial ask in the demo. The demo's job is to make the integrity model believable. The financial conversation lives in the pre-meeting brief and the pitch deck.
The end-of-demo line: "What we'd like to leave today with is a sense of whether you're open in principle to issuing a Letter of Intent for a 90-day Lozells pilot. No money. No procurement. Just a signal we can take to Innovate UK and our angels. That unlocks everything else."
What to avoid
- Don't fight a missed detection. Switch to barcode mode and keep the momentum.
- Don't talk over the voice announcements. Let them play — the silence shows the user doesn't need to look at the screen.
- Don't promise behaviour data the pilot hasn't yet produced. Keep targets aspirational, with the source given.
- Don't open the trust-score audits screen in the demo. It's a council-facing surface; if asked, offer to walk through it after.