Executive summary
Live Venues Platform Review
Daniel wants to know whether the venue work you built is something his design department can actually use. You have three working surfaces, real data behind all of them, and one honest limitation that is better said out loud than discovered. The win condition for this meeting is not applause — it is Daniel naming which venues matter and what his team needs to see per venue, so the next build is aimed rather than guessed.
When
Wed 2 Sep · 1:00 PM ET
Length
30 minutes
In the room
Daniel Croci · Natalia Kovaleva · you
Where
Ask of them
Priority venues + what to show per venue
01
One-page meeting brief
What this meeting appears to be about
Straight from the calendar invite, word for word:
“Review the live venues platform Ahmad built, understand how Daniel can use it in his role, and frame it as a tool for the design department.”
So it is a fit review, not a status update. Daniel is not asking whether it works — he is asking whether it belongs in his department's hands. That reframes your job: less demo, more “here is what it does, tell me where it lands in your workflow.”
Needs confirmation
The invite cites a Slack thread from Fri 28 Aug, 9:06 PM ET. That thread predates two of the three
surfaces you built (the globe on 30 Aug, the scene on 31 Aug), so “the live venues platform” in the invite most
likely refers to the 3D LED configurator — the link you had been sending. Do not assume. Open the meeting by
naming all three in one breath and let Daniel point.
Needs confirmation
The calendar lists you as the organiser, which does not match “I accepted this before I understood it.”
Worth a glance before you join — if someone set it up on your behalf, they may have an agenda you have not seen.
Why it matters to ANC
- The design department is the bottleneck that costs deals time. Every proposal that needs a visual waits on a person to build it. Three of your surfaces attack that from different angles.
- The data already exists and nobody can see it. ANC has quoted 1,727,754 sq ft of LED across 310 systems. Until now that lived in spreadsheets and PDFs. It is now visual and to scale.
- It is a retention story, not just a sales story. The globe shows 246 active venues with live event load and open tickets — the operational picture that usually only exists inside the service desk.
- Daniel already runs a tool you built. The Design Hub has 43 active projects and 9 users on it today. This is an extension of a working relationship, not a cold pitch.
Strongest proof points
- 310 real proposal systems render to scale — one world unit is one foot, so every display is the size it was quoted.
- OKC Thunder – New Arena 2026: 149 screens, 87 distinct, 26,370 sq ft, finest pitch 1.25 mm, 8 zones. Real deal, real numbers, drawn live.
- 246 active venues on the ops globe with 409 events in the next seven days and 32 open tickets, each status carrying the reason it fired.
- The configurator is client-safe today — 4 hand-built venues, pick a zone, drop artwork on the LED, and it can be deep-linked straight into a deck.
Open questions and risks
- Generic placement cannot look real. The scene invents geometry from screen names across 310 different proposals. Say this before Daniel says it — it buys you the whole room.
- The venue asset layer is nearly empty. Coordinates on all 181 mapped venues, but market on 27, screen counts on 2, contract expiry on 1.
- Where should these live? Two of the three sit on your own hosting behind an access link, reading ANC data read-only. That is a prototype posture, not a product posture.
- Source data is duplicated. 310 systems carry only 247 distinct client names — 94 of them share a name with another record.
What you need from them
Three decisions. Nothing else is worth 30 minutes.
- 1 — Real shells or generated ones? The recommendation is to map real quoted screens into the configurator's existing hand-built venue shells. Hand-made shell so it looks right, real quoted dimensions and pitch so it is true per venue. 310 systems driving 4 believable venues instead of 310 invented ones. This is proposed, not built, and it needs Daniel's yes.
- 2 — Which venues first? Name the shells that matter to the design department, in order.
- 3 — What does a designer need to see per venue? The asset layer is empty because nobody has said what belongs in it. Daniel and Natalia can answer that in the meeting.
02
What's actually true — live, built, proposed, idea
Read from the running systems at 08:40 UTC on 2 September. Nothing here is projected or rounded up.
Live Working right now, in production
| Surface | What it is | Verified today |
|---|---|---|
| Venue Vision 3D LED configurator |
Four hand-modelled venues — NFL stadium, NBA arena, mall, transit hub. Pick a zone, drop artwork onto the LED. | Answers 200. Openly reachable, no access link needed. Deep-linkable by venue, zone and artwork, so it can be embedded in a deck. |
| Venue Globe operations map |
Every ANC venue on a globe with live status pulled from the service platform, read-only. | 246 active venues · 181 mapped, 65 not yet placed · 191 OK / 39 attention / 16 critical · 32 open tickets · 409 events in the next 7 days. Every status carries the reason that fired it. |
| Venue Scene to-scale LED inventory |
Every LED system ANC has quoted, generated to scale from the real proposal data. | 310 proposal systems · 4,668 screens · 1,727,754 sq ft. Rows with corrupt dimensions are excluded and counted on screen, never silently dropped. |
| Design Hub Daniel's board |
The design project board his team already runs, with automatic intake from the CRM. | 43 active projects · 9 users · 2 currently linked from the CRM. |
Built, needs a decision
- Deck embedding. The configurator can be dropped into a presentation slide by link. The mechanism is built and verified; whether client decks should carry it is not decided.
- Venue photography registry. 18 venues mapped to ANC's own imagery, built to avoid third-party stadium photos. Nothing consumes it yet.
Do not demoBoth of these are half a step behind the others. Mention only if asked.
Proposed, not built
- Real screens in real shells. Map each proposal's quoted screens into the configurator's existing named zone slots. This is the ask of the meeting.
- Joining the globe to the scene. The globe knows the venue; the scene knows the screens. They are not connected — 2 of 181 mapped venues carry a screen count today.
Say it before they find it Three honest limits
- Generic placement cannot look real. The configurator looks right because a person placed the screens in a hand-built room. The scene invents placement from names and dimensions across 310 very different proposals — a 381 ft strip called “Main Display Board” has no correct automatic home. More lighting will not fix that. What the scene genuinely is: a to-scale LED inventory viewer, and it is worth describing that way.
- Red on the globe means the feed we have configured is failing, not that the venue is dark. Feed health is only judged where a feed address is set — 66 of 181. Say that before someone screenshots Fenway Park.
- The source data has duplicates and typos. 310 systems, 247 distinct client names; “Indiana Fever” appears on 19 systems, 14 of them identical in shape; “New Client” on 6; a stadium name is misspelt in the source. This is a real finding for the proposal side, not a rendering fault — and Natalia is in the room for it.
03
The 30 minutes, in order
Three demos, three pauses, one decision. If you are running late, cut the globe — not the pauses.
0:00 — 0:03 · FRAME
Say what this is and what you want out of it
Do not open with a demo. Open with the three surfaces named in one breath and the decision you want, so Daniel knows where the 30 minutes is going. Then ask him to tell you which one the Slack thread was about.
On screen: this page, or nothing. Talk to them, not to a browser.
0:03 — 0:09 · DEMO 1
Venue Vision — the one that is client-ready today
Lead with your strongest, most finished thing. Pick the NBA arena, select the centre-hung zone, drop artwork on it, orbit once. Say it is four hand-built venues and that is exactly why it looks right.
On screen: the configurator, full screen, already loaded before the call.
0:09 — 0:11 · PAUSE
“Daniel — is this the register your team works in?”
Then stop talking. This is the single most useful question in the meeting: it tells you whether the design department wants photoreal, schematic, or something else entirely. Write down his exact words.
0:11 — 0:17 · DEMO 2
Venue Scene — the scale of what ANC has already quoted
Open OKC Thunder. 149 screens, 26,370 sq ft, finest pitch 1.25 mm, generated from the real proposal — nobody modelled it. Then say the limit out loud, unprompted: the placement is generic and cannot look real, and this is honestly an inventory viewer rather than a venue render.
On screen: the scene on OKC, then the 310-system list.
0:17 — 0:19 · PAUSE
“Is a to-scale inventory of every system useful on its own, or only if it looks like the room?”
This is the fork in the road. His answer decides whether the next build is a viewer or a renderer.
0:19 — 0:23 · DEMO 3
Venue Globe — the operational picture
Short. 246 active venues, 409 events in the coming week, 16 critical. Zoom one critical venue and read the reason it fired. Then be straight: the operational layer is real, the asset layer is nearly empty, and that is a question for them, not a bug.
On screen: the globe, then one venue card.
Cut this section first if you are behind.
0:23 — 0:28 · THE ASK
Put the decision on the table and stop selling
Real screens in real shells. Say it in two sentences, say it is not built, and ask for a yes or a no plus the venues that matter most. Then ask the asset-layer question — what does a designer need to see when they open a venue.
0:28 — 0:30 · CLOSE
Read back the decisions and name the next step
Repeat what you heard, name who owns what, and say exactly what you will come back with and when. Do not end on “let me know what you think.”
04
Six slides — and only six
These are holding slides between demos, not the meeting itself. Most of the 30 minutes is a live screen. Every slide below earns its place or it would not be here.
05
Live-demo plan
Critical
All three 3D surfaces need real graphics hardware to render. Drive them from your own machine, on tabs
that are already open and already loaded, before the call starts. Do not open a cold tab on a shared screen and wait
for a scene to build.
Tab order — open all of these before you join
| # | Open this | What it proves | Be ready for |
|---|---|---|---|
| 1 | Venue Vision abc-3d.izcgmb.easypanel.host 200 verified |
ANC can show a client their own artwork on their own LED, in a room that reads as real. This is the finished thing. | “Can we do this for a venue that isn't one of the four?” — the honest answer is no, not today, and that is exactly what slide 5 asks for. |
| 2 | Venue Scene — OKC venuescene.basheer.app 200 with access link |
Scale. 149 screens generated straight from a real proposal, every one at its quoted size. | “Why does it not look like an arena?” — answer it before they ask. Generic placement, and you would rather fix it properly than light it better. |
| 3 | Venue Scene — the list same tab, system list |
310 systems. The library exists; this is not a one-venue demo. | Duplicate names are visible in the list. Get ahead of it: 247 distinct names across 310 systems, and it is a proposal-data question for Natalia. |
| 4 | Venue Globe venues.basheer.app 200 with access link |
246 active venues, 409 events this week, and every red flag carrying its reason. | “Why is Fenway red?” — the feed we have configured is failing. It is a data-freshness flag, not an outage. |
| 5 | Design Hub abc-anc-design-hub… 200 verified |
Only if the conversation turns to workflow. 43 live projects, and design requests already arrive from the CRM automatically. | Keep it closed unless Daniel steers there. It is his tool and he knows it better than the demo does. |
Access links
The globe and the scene each need their access link in the address — bare URLs are refused. Paste the full links into
your tabs before the call, and do not screen-share the address bar while it contains them.
Questions you should have an answer ready for
| If they ask | Answer with |
|---|---|
| “Is this an ANC product or a side project?” | Working prototypes on my own hosting, reading ANC data read-only, behind an access link. Where they should live is a decision I would like from you — that is a real question, not a deflection. |
| “Can I send this to a client?” | The configurator, yes, today. The other two, not yet — they are behind access links and the scene's placement is not client-grade. |
| “How long to do the real version?” | Do not give a number in the room. Say you will scope it against the venues he names and come back with it. A number invented live becomes a commitment. |
| “Where does the data come from?” | The quoted systems come from the proposal platform; the live venue status comes from the service platform. Both read-only — nothing writes back. |
| “Why are there duplicate venues?” | Because every saved version of a proposal is its own system. 310 systems, 247 distinct names. Whether the viewer should show every version or the latest per client is a decision, and Natalia should make it. |
| “What about the venues that aren't on the map?” | 65 of 246 have no coordinates yet. Placing them is straightforward; the reason it is not done is that wrong coordinates are worse than none, so it only accepts a match it can corroborate. |
06
Say this, not that
Your opening — roughly 25 seconds
“Hi Daniel. Quick frame so we use the half hour well. Over the last week I built three things that all answer the
same question — how do we see a venue before it exists. One is a configurator with four hand-built venues where you
drop artwork onto the LED. One generates every system ANC has ever quoted, to scale. One is a map of all 246 active
venues with what is happening at them this week. They are all live and I will show you all three.
What I want out of today is not a reaction to the visuals. I want to know which of these your team would actually use, and what you would need on it. And before I start — the Slack thread this meeting came from was last Friday. Which one were you looking at?”
What I want out of today is not a reaction to the visuals. I want to know which of these your team would actually use, and what you would need on it. And before I start — the Slack thread this meeting came from was last Friday. Which one were you looking at?”
That last question is the whole opening. It resolves the ambiguity without you ever admitting you were unsure, and it hands Daniel the frame.
Explaining what you built and why
Not this
“So I built a 3D visualisation platform with a procedural generation engine that reads from the proposal database…”
This
“ANC has quoted about 1.7 million square feet of LED and none of it was ever visible. Now you can open any of the 310 systems and see it at the size it was sold.”
Not this
“It's still early days, there's a lot I want to improve, it's a bit rough…”
This
“Two of these are finished enough to use. One has a limitation I want to walk you through, because it changes what we build next.”
Not this
“This could eventually replace how the design team does renders.”
This
“I don't know where this fits in your workflow. That's the thing I need from you today.”
Handling what you do not know
Uncertainty only sounds unprepared when it is vague. Named uncertainty sounds like judgement.
Not this
“I'm not sure, I'd have to look into that.”
This
“Two of 181 venues carry a screen count. The reason is that nobody has decided what belongs on a venue record yet — which is one of the three things I want from this call.”
Not this
“It should be able to do that.”
This
“It doesn't do that today. Tell me whether you'd use it and I'll tell you what it takes.”
RuleNever say “should work” about something you have not opened in front of them. If it is not on a tab you already loaded, it does not get claimed.
Asking for feedback and for ownership
Not this
“What do you think? Any feedback? Let me know if you have thoughts.”
This
“Daniel — name the venues that matter to your team, in order. I'll build against that list rather than guessing.”
Not this
“Would it be useful if I added more data to the venue view?”
This
“When one of your designers opens a venue, what do they need on the screen to start work? That list is what I'll build.”
Open questions get vague answers. Questions that ask for a list, an order, or a yes-or-no get decisions — and a decision is the only thing that makes the next build worth starting.
Your close — roughly 30 seconds
“Let me read back what I heard so I don't build the wrong thing. [Repeat his priority venues and what he wants on a
venue view, in his own words.]
Here's what happens next. I'll scope mapping real quoted screens into the hand-built venues, starting with the ones you named, and I'll come back with what that takes. Natalia — the duplicate systems in the list are a proposal-data question, and I'll send you exactly which ones. Daniel, the one thing I need from you is that priority list; everything else I can take from here.”
Here's what happens next. I'll scope mapping real quoted screens into the hand-built venues, starting with the ones you named, and I'll come back with what that takes. Natalia — the duplicate systems in the list are a proposal-data question, and I'll send you exactly which ones. Daniel, the one thing I need from you is that priority list; everything else I can take from here.”
Never close on “let me know what you think.” Close on who owes what.
07
Before you join
Read and confirm
Open the Slack thread from Fri 28 Aug, 9:06 PM ET that the invite cites. It is the only piece of context missing from this package — it will tell you which surface Daniel actually meant.
Check who created the invite. The calendar lists you as organiser, which does not match your read of it. If someone set it up for you, find out why.
Decide the Natalia angle in advance. She is in the room. The duplicate-systems finding is genuinely hers — decide whether you raise it live or send it after, and do not let it hijack Daniel's half hour.
Tabs — load them, do not just open them
Venue Vision on the NBA arena, a zone already selected, artwork already applied. Verified answering today.
Venue Scene on OKC Thunder, scene fully built, camera framed. Access link in the address already.
Venue Scene system list, scrolled to show the range.
Venue Globe, spun to a critical venue with its reason visible.
Design Hub, loaded but not shown unless he steers there.
Backups — because a 3D scene failing live costs you the room
Screenshot every scene from your own machine before the call: the configurator with artwork on the LED, OKC in the scene, the 310-system list, the globe with a critical venue open. These cannot be captured from the server — it has no graphics hardware — so they have to come from your laptop.
Record a 30-second screen capture of the configurator orbiting with artwork applied. If the live scene stalls, you play the clip and keep talking rather than watching a loading state together.
Have the numbers on paper: 310 systems · 4,668 screens · 1,727,754 sq ft · 246 active venues · 409 events this week · OKC 149 screens / 26,370 sq ft / 1.25 mm.
Do not show
- The proposal-to-deck bridge. It is unfinished work that is not in production. Showing it creates an expectation you would then have to manage.
- The venue photography registry. Built, wired to nothing. Mentioning it invites a question you cannot close.
- The address bar of the globe or the scene while the access link is in it.
- Anything on your screen that is not one of the five tabs. Share a single window, not a display.
The one line to have ready if the meeting drifts
“Before we run out of time — the thing I need from you is which venues matter most to your team, in order. Everything
else I can figure out from here.”