Stadia
Demo
Clock · real
Demo guideHow it fits together

Demo

Demo guide

Everything in the demo is real data in one database. There are no mocked screens. The only fake thing is the card payment (any 16 digits pay; a number ending in 0000 is declined).

  1. The meeting (about 25 minutes, one browser tab, you talking).
  2. The playground for the week: how to be each user, create an event, sell it, invite guests, post as a sponsor, and move an event through its life with the simulator.

Before you start (2 minutes)

Sign in as Admin and open Admin → Events → Nedbank International Polo → Simulator.

  • The status pill should read live and the DEMO strip clock should say real. If not: click Rewind to on sale, then on sale → live, and Clock → Real.
  • Absa Du Champ is currently on sale. Leave it; it is the “real first Equus fixture” story.

Have these tabs ready: the homepage, /wallet (as Guest), /scan (as Gate), and the Polo Live dashboard (as Inanda Club). You will switch users in one tab; the pages re-render for whoever is signed in.

Switching users

Under the main nav there is a thin strip: DEMO · {name} ▾. Click it and pick a persona. It signs you in as that person and lands on their home. No passwords, no emails. It takes a few seconds; wait for the page to land.

PersonaWho they areLands on
AdminStadia staff. Simulator, clock, Outbox, organisations/admin
Inanda ClubOrganizer of Nedbank Polo and Sunset Sixes/organizer
EquusOrganizer of Absa Du Champ/organizer
Nedbank, GlenfiddichSponsors of Polo/sponsor
RMACorporate buyer with an 80-seat Polo block (also a sponsor)/business
Gate, Usher, Experience hostEvent staff on Polo/scan, /scan/lookup
Guest, Lawn, InvitedConsumers with tickets in their wallet/

Every human is a consumer first; roles sit on top. Point that out: RMA’s owner can still buy a ticket for themselves.

Part 1 · The meeting

Talk track in bold, clicks in plain text. Total is about 25 minutes; cut Act 5 if short on time.

Act 1 · 5 min · Persona: Guest

The consumer

“The price you see is the price you pay”

  1. Homepage. Six events, priced all-in. Polo at Inanda, Cartier in the winelands, snow polo in St. Moritz, and Equus’s own Absa Du Champ in February.
  2. /events → click Paarl → Absa Du Champ. A real fixture. Val de Vie, 6 February. Notice “what’s included” under Clubhouse, and that the terms of sale are a link, not fine print.
  3. Open Nedbank Polo → Get tickets → pick one General Lawn → Continue → Details (the organizer’s two extra questions with the champagne incentive) → Pay. Fee is inside the price. Nothing is added at checkout. The terms line names the organizer. Pay with 4242 4242 4242 4242.
  4. Confirmation: 5% back in points, and “Tell a friend” shares the event page, never the ticket.
  5. /wallet → open the new ticket. This is the organizer’s own design. The code refreshes every 15 seconds; a screenshot is useless at the gate. Polo is live right now, so the ring is moving. Scroll: pre-orders from partners, delivered to your pocket, with a service note.
  6. /feed. Posts and offers from the organizers and sponsors of events you hold tickets for. Copy the Glenfiddich code; tick “share my details” and you become a lead. Consent is the only way a sponsor gets a name.

Act 2 · 7 min · Persona: Inanda Club

The organizer

“Your brand, your guests, your data”

  1. Dashboard: events by state, sales today, countdown.
  2. Open Nedbank International Polo. Walk the tabs left to right: Set up, Event day, After. That is the order a producer thinks in.
  3. Tickets: tiers, all-in price with the fee inside, capacity, sold count, “what’s included”. Point at the Waitlist section: a sold-out tier collects emails; an announced event collects “tell me when tickets open”. Yours to export.
  4. Tickets: seating lives under each tier — pockets, tables or none. No seat map; hospitality events sell by pocket and table, not by chair.
  5. Partners: Nedbank headline, Glenfiddich partner, Aston Martin supplier; toggles for event page, ticket, feed.
  6. Team: gate staff and ushers by email, with access until and revoke.
  7. Ticket design: drag a block, paste a brand hex into the accent field, add the Business logo block. Every RMA ticket carries RMA’s mark. Wallet and email render this same design. Do not save unless you want to keep it.
  8. Guests: filter to RMA, not arrived. Show Void and Reissue on a row. Lost phone, forwarded screenshot, wrong name: reissue kills the old code and emails a new one. Export CSV.
  9. Live: arrivals per minute, by business, recent scans. Leave this tab open for Act 3.
  10. Reports: sales for the organizer, engagement per partner, anonymised audience. Buckets under ten people are hidden.

Act 3 · 3 min · Persona: Gate → /scan

The gate

“Alive means valid”

  1. Camera scanning needs a second device; for the room, use manual entry: type the ticket number from Act 1 (it starts STA-2026-) → Check in. Green card: name, tier, pocket.
  2. Enter it again → Already checked in with the first time. Duplicates and stale screenshots fail; the gate never argues with a guest, the card does.
  3. Switch to Inanda Club → Live dashboard: the arrival is there. (Or as Admin, Simulator → Scan 20 in, and watch the chart move.)
  4. Persona Usher → /scan/lookup → type nkosi. An usher finds the guest’s pocket without scanning anything.

Act 4 · 5 min · Persona: RMA → /business

The business

“Replace the spreadsheet and the WhatsApp group”

  1. Your blocks: 80 Clubhouse seats on Polo, RSVP funnel, arrivals. This is the corporate host’s phone on the morning of the event.
  2. Open the Polo block: guests ranked 1 to 3, states queued / invited / accepted / declined / expired / checked in. Rank 1 is invited up to the block size. A decline or a 72-hour silence invites the next name automatically. Show Resend, Remove, Add guest, the CSV template, and Process now.
  3. Scroll to Your mark on tickets: upload a logo and every RMA ticket shows it.
  4. Persona Admin → Outbox. Every email the platform sends is recorded here: invitations, reminders, tickets, reissues. The demo never depends on an inbox. Open an invitation; the RSVP link inside is live.
  5. Mention invoices: a block can be bought by Invoice / PO; Admin marks it paid under Admin → Orders and the seats appear.

Act 5 · 3 min · Persona: Glenfiddich → /sponsor

The sponsor

“Show sponsors what they paid for”

  1. Dashboard: reach, clicks, redemptions, leads across sponsored events.
  2. Posts: a post with auto-UTM link, an offer with a code, a product (the bottle at R1 450) fulfilled by the organizer. Open one to show scheduling: “3 months after the event, to guests who said they are interested in an Aston Martin” is a real option.
  3. Reports → Nedbank Polo: impressions, CTR, copies, redemptions, bottles sold, audience profile with the data-source note.
  4. Leads: the consented guest from Act 1.

Close · 1 min · Persona: Admin → Simulator

Close

One switch walks an event from draft to announced, on sale, live, wrapped. One clock moves the whole platform forward so a 72-hour RSVP window or a post scheduled for November can be shown in a minute. Everything you saw was the same database, every role a real login.

Part 2 · The playground

Same URL. Use the DEMO ▾ strip to be whoever you need. You cannot break anything that Admin cannot put back, so click freely. Two house rules:

  • Build your own events rather than editing Nedbank Polo; Polo is the shared reference event.
  • The virtual clock is global. If you move it, everyone sees the moved time. Put it back to real when you are done.

Create and sell an event (as an organizer)

  1. Persona Equus (or Inanda Club) → New event. Give it a title; you land in the wizard.
  2. Basics: dates, venue, city, description, a hero image path (any /events/*.jpg from the existing events works), house rules, terms of sale (text or a link).
  3. Tickets: add tiers. Price is all-in; the fee is the slice inside it. Add “what’s included” lines. Set capacity small (say 3) on one tier if you want to see Sold out and the waitlist later.
  4. Tickets · Seating: open a tier and pick pockets or tables, then type Tables 1–20 or a comma list of company names. Choose None for general admission. Rules and complimentary tickets sit on the same step.
  5. Questions: extra questions and the incentive line. Transferability and the waitlist live under Tickets → Rules.
  6. Partners: attach a sponsor (they must exist; Admin creates them under Admin → Organisations). Choose tier and placements.
  7. Team: invite a gate person by email with an optional access until. The invite lands in Admin → Outbox; open the link to accept as that person.
  8. Ticket design: drag, resize, recolour, add blocks, Save design.
  9. Review & publish: the checklist gates publishing. Announce lists it as “Coming soon” with a “tell me when tickets open” form. Put on sale opens checkout.
  10. Persona Guest → find the event under /events → buy. Then check the organizer’s Guests and Overview.

Be a business

  1. Persona RMA → Buy a block → open an on-sale event → Buying for a company? → tier, quantity, pay by card or Invoice / PO.
  2. Invoice path: persona Admin → Orders → Mark paid. The block and its seats appear under /business.
  3. Open the block → Upload guests (download the template first: name, email, mobile, tier_rank 1–3, location) or Add guest by hand. Rank-1 names are invited at once.
  4. Persona Admin → Outbox: open an invitation, copy the RSVP link, open it, sign in as that guest, answer the questions once, Accept. The ticket appears in their wallet reading “You are invited by RMA · RMA pocket”. Decline instead and watch the next name get invited on the RMA dashboard.
  5. Expiry: set the clock forward (below) and click Process now on the block page. Unanswered invitations expire and cascade.

Be a sponsor

  1. Persona Nedbank or Glenfiddich → Posts → New. Choose Post, Offer (code, expiry, shared or per-guest codes) or Product (price, quantity, fulfilment note). Schedule now, at a time, or relative to the event (“90 days after wrapped”). Target everyone, a tier, or an answer to an organizer question.
  2. Persona Guest → /feed to see it (guests only see orgs tied to their tickets or follows). Copy a code, consent, pre-order a product with a delivery note.
  3. Back as the sponsor: Reports and Leads. As the organizer: Fulfilment shows the pre-order with the note, grouped by pocket.
  4. Assets: upload the brand logo; it appears on tickets where the organizer placed the sponsor strip.
  5. Admin can prefill a post from any public page under Admin → Import from URL.

Run the gate

  1. Persona Admin → Simulator → on sale → live. Wallet codes start rotating; /scan accepts them.
  2. Persona Gate → /scan: camera on a phone (HTTPS, allow camera) or type a ticket number. Try the same ticket twice.
  3. Persona Usher → /scan/lookup: search by name, email or number.
  4. Persona Admin → Simulator → Scan 1 / 5 / 20 in writes real check-ins so the organizer’s Live dashboard moves without a phone.
  5. Staff with an access until in the past lose /scan; Revoke on the Team tab does it immediately.

The simulator and the clock (as Admin)

Admin → Events → (event) → Simulator. Two independent controls:

Lifecycle buttons move the event’s state. Organizers may go draft → announced → on sale (and back); only Admin can go on sale → live → wrapped → archived, and Rewind to on sale replays a finished event.

StatePublicBuyableWallet codeGate
drafthiddennonono
announced“Coming soon”, email capturenonono
on salelisted with pricesyes“Opens on matchday”no
live“Today”organizer’s choicerotatingyes
wrapped“Past”nonono
cancelledlisted as cancellednonono

Virtual clock moves “now” for the whole platform (badges, RSVP expiry, reminder emails, scheduled posts, “access until”). It does not change an event’s state; use the buttons for that. The clock is global: set it from the DEMO strip ( Clock · … ▾) on any page, or from the event’s Simulator. Jumps on a Simulator are dated from that fixture (AMEX uses October, Polo uses August).

JumpVirtual nowUse it to see
Realtodaynormal browsing; always end here
Two weeks beforeevent start − 14 daysinvitations pending
RSVP windows expiredevent start − 10 daysclick Process now on a block
Matchdaythe event’s startwallet codes rotating, gate open
Three days afterevent start + 3 dayspost-event reports
90-day follow-upevent start + 93 daysrelative sponsor posts: click Publish due

For an event you created, the buttons are usually all you need: announce it, put it on sale, buy a ticket as Guest, set it live, scan, then wrapped for reports.

Useful places

WhatWhere
Every email ever sent, with live linksAdmin → Outbox
Create organizers, sponsors, businesses; add ownersAdmin → Organisations
Mark an invoice paidAdmin → Orders
Give a company free tickets (organizer approves); run the RSVP cascade for every eventAdmin → Allocations and RSVP
Storefront of an organizer/o/inanda-club, /o/equus
How the pieces fit together“How it fits together” in the DEMO strip (/map)

Things to know

  • @stadia.demo addresses cannot receive email. Always use the DEMO strip for the seeded personas, and Admin → Outbox for any link a flow “emailed”.
  • Signing in with your own email works (magic link or 6-digit code) and creates a consumer account with 20 points. If the mail is slow, the link is in Admin → Outbox too.
  • Payments are pretend. Any 16 digits pay; end the number in 0000 to see a decline.
  • Business accounts never see or earn points; invited guests do.
  • Resale only appears on events where the organizer switched transferability on (Cartier, AMEX, Sixes, St. Moritz). Equus events default to off.
  • Camera scanning needs HTTPS and a real phone; in a laptop browser use the ticket-number field.
  • If something looks stuck after a persona switch, reload the page.

Putting things back

As Admin: DEMO strip → Clock → Real. If you moved Polo, Rewind to on sale then on sale → live. Events you created can be cancelled from their Overview or left as drafts; they only show publicly once announced.