Picture this. It is 12:32. Founder three steps onto the stage to a thin, polite round of applause. In row eight, the lead investor of the round nobody had time to confirm is checking her phone. The Wi-Fi drops mid-slot. Two seats down, a partner from the fund your founders most wanted has not shown up at all. By 15:00, the meeting schedule is forty minutes out of alignment. By 18:30 the photographer is packing up while two unanswered press requests sit in the press lead’s inbox.
This is not a horror story. It is an ordinary demo day, planned by a team that built the stage and forgot the operations behind it. Each of those moments is operational, not strategic, and each of them is preventable.
This guide is the playbook that prevents them. Twelve weeks, four KPIs (key performance indicators), one structured budget, one run-sheet, one risk register. It assumes you have read our organiser’s guide to what a demo day is and our six-phase structure for maximum follow-ups. Those two posts cover the why and the strategy. This one covers the project plan.
The short version: A demo day is a twelve-week project, not a one-day event. Start with investor curation at T minus twelve weeks, lock venue and AV (audio-visual) at T minus eight, open pre-scheduled meetings at T minus four, rehearse at T minus one, and run a tight five-window day at T minus zero. Budget realistically for a ten-startup cohort, pick a matchmaking platform you can audit, and measure four KPIs: meetings per founder, investor Net Promoter Score, fourteen-day follow-up rate, and ninety-day funding velocity.
Why demo day planning runs on two tracks
A demo day has a stage track and an operations track. They are equally important and they live on different calendars.
The stage track is what people see on the day: a moderator, a pitch deck, a clicker, a Q&A, a follow-up reception. It is what your founders rehearse, what your AV team builds, what the photographer captures. It is also the part most first-time organisers obsess over. It is necessary, but it is not sufficient.
The operations track is what decides whether the room is full of the right investors, whether your founders meet them in pre-scheduled slots, whether anyone follows up in the first forty-eight hours, and whether the programme can report cohort-over-cohort improvement to its board. It runs on a twelve-week timeline that starts before the founders even rehearse a single slide.
The simplest test is to ask: if your venue and AV team disappeared tomorrow, could you still close the round? If the answer is yes, your operations track is doing the work. If the answer is no, the stage is carrying weight it cannot carry.
The 12-week countdown
Use this countdown as a project plan. Each phase has a primary owner, one or two outputs, and a decision that must be locked before the next phase opens. The labels (T minus twelve, T minus ten and so on) count down to pitch day at T zero.
T-12: Kick-off and cohort brief
Twelve weeks out, you are not yet thinking about catering or the runsheet. You are writing the cohort brief. It is a one-page document for every internal stakeholder: who is in the cohort, what stages they are at, what sectors they cover, what cheque sizes they need to raise, and what success looks like for each of them. The cohort brief becomes the input for the investor thesis at T-10. Without it, curation is just a guess.
T-10: Investor thesis and long-list
Ten weeks out, your investor lead drafts a written thesis. Stages, sectors, geographies, ticket sizes. From the thesis you build the long-list: typically four to six times the number of investors you actually want in the room. If you want one hundred and twenty active investors on pitch day, your long-list opens with five hundred to seven hundred names. Yes, that is a lot. The funnel from long-list to confirmed attendance runs at about twenty to twenty-five per cent for tier-one cohorts and ten to fifteen for the rest.
T-8: Venue, AV and vendor contracts
Eight weeks out, the venue contract is signed, the AV brief is locked, and your photographer, videographer and live-stream partner are confirmed. Venue specifications that get missed at this stage cause Wi-Fi outages on the day. According to FPC Events’ 2026 AV checklist, the load-in path and dedicated bandwidth are the two items most likely to be under-specified. Ask the venue, in writing, how many hardwired Ethernet drops are available for the stage and the matchmaking-platform terminals.
T-6: Investor outreach wave one
Six weeks out, wave one of investor outreach goes out. The Slush model is instructive here: investors confirm meetings that founders propose, not the other way around. That means you need a meeting-matrix platform configured and open to founders by T-6 so they can begin requesting. Industry data from Allied Venture Partners (2026) shows that eighty per cent of successful deals require at least five follow-ups, and the first one lands within forty-eight hours. The discipline begins now, with how you chase confirmations.
T-4: Pre-scheduled meeting architecture
Four weeks out, meetings are being booked. Cap the number per investor (typically eight to twelve over the day) and per founder (typically six to ten). Build in fifteen-minute buffers between slots. Have a named operations owner who can move a meeting at thirty seconds’ notice when an investor’s flight delays.
T-3: Founder pitch trainings and marketing drumbeat
Three weeks out, founders run their first full pitch rehearsal in front of mentors. They will rehearse three times: T-3 with mentors, T-2 with a pitch coach, T-1 in the actual venue. Marketing turns on the social drumbeat: cohort announcements, founder spotlights, embargoed press teasers. Save the headline reveal for pitch day.
T-2: Investor confirmations and day-of tech stack
Two weeks out, you confirm every investor with a personal email from the founder they are scheduled to meet, not a calendar reminder from your platform. Confirmation rates jump significantly when the message comes from the person the investor is about to meet. You also lock the day-of tech stack: badge printing, check-in flow, matchmaking-platform terminals, Q&A microphones, live-stream tier.
T-1: Final rehearsal and run-sheet lock
One week out, you rehearse on the actual stage with the actual AV. The run-sheet is locked: who stands where, who holds the clicker, who runs the Q&A, who manages the matchmaking-platform terminal, who handles a Wi-Fi-drop fallback. Every named owner has a printed copy and a phone number for the person above them in the escalation chain.
T-0: Pitch day
On the day, everything you planned either works or does not. The plan does not change. The owners change posture: from planners to operators. The run-sheet runs. The KPIs are captured live. The follow-up window opens at the final handshake.

How to budget a demo day
Budgets vary by region and ambition, but a ten-startup cohort with one hundred to one hundred and fifty investors in the room runs in a fairly predictable range. The figures below assume a single-day urban venue in Europe or North America with mid-tier production values. Add twenty to thirty per cent for a tier-one city, subtract twenty for a regional venue.
Use these as planning anchors, not quotes. Get three written quotes for venue, AV and catering before locking budget.
| Line item | Low range | High range | Notes |
|---|---|---|---|
| Venue (single day, 200 cap) | EUR 8,000 / USD 9,000 | EUR 25,000 / USD 28,000 | City and exclusivity drive most of the variance. |
| AV and production | EUR 10,000 / USD 11,000 | EUR 35,000 / USD 38,000 | Live-stream tier and stage build are the two biggest levers. |
| Catering (200 attendees, coffee plus reception) | EUR 6,000 / USD 6,500 | EUR 18,000 / USD 20,000 | Reception bar costs scale fast. |
| Matchmaking platform | EUR 3,000 / USD 3,300 | EUR 12,000 / USD 13,000 | Per-event pricing for a B2B-grade tool. |
| Marketing and PR | EUR 4,000 / USD 4,400 | EUR 20,000 / USD 22,000 | Includes paid social, founder photography, press list. |
| Capture (photo, video, recordings) | EUR 3,000 / USD 3,300 | EUR 10,000 / USD 11,000 | Two photographers and a two-camera video team. |
| Contingency (10 per cent) | EUR 3,400 / USD 3,800 | EUR 12,000 / USD 13,000 | Never run a demo day without it. |
| Total | EUR 37,400 / USD 41,300 | EUR 132,000 / USD 145,000 | Ten-startup cohort, one-day urban venue. |

The day itself: a runsheet template
A workable demo day has five operating windows: build, doors, pitch block, one-to-ones, and break-down. The exact times shift, but the windows do not.
| Window | Time | What happens |
|---|---|---|
| Build | 06:00 to 10:30 | Vendor load-in, AV setup, registration desks, matchmaking terminals, Wi-Fi sanity check, two full audio rehearsals. |
| Doors and check-in | 10:30 to 12:30 | Investors arrive, lanyards out, founder coffees, press briefing window. |
| Pitch block | 12:30 to 15:00 | Ten founders, five to ten minutes each plus Q&A, hard clock. Moderator manages overruns. |
| One-to-one meetings | 15:15 to 18:30 | Pre-scheduled fifteen-minute slots, fifteen-minute buffers, named room manager, hot-list table for unscheduled hot threads. |
| Reception and break-down | 18:30 to 22:00 | Drinks, informal introductions, photographer captures group shots, vendor load-out from 20:00. |
Two ideas baked into this run-sheet matter more than they look. The fifteen-minute buffer between meetings is not slack. It is where investors finish notes and decide whether to extend a hot conversation by ten minutes. The hot-list table is a designated physical surface in the meeting hall where founders can drop a name and a one-line note when an investor flags interest outside of the scheduled slots. The operations lead clears the hot list every thirty minutes and routes follow-ups before the meeting is forgotten.
Tech stack choices
The day-of tech stack has five components: a matchmaking platform, a CRM (customer relationship management) anchor, a calendar-sync layer, a capture system, and a live-stream tier.
The matchmaking platform is the load-bearing piece. It powers the meeting matrix, the check-in flow, the schedule each founder and investor sees on their phone, and the data feed for the post-event report. Pick one you can audit: every meeting request, accept, decline and reschedule should be visible in a log. Rule-based matching with a meeting-matrix backbone is the default for a B2B context because it gives organisers a transparent reason for every match. Algorithmic or AI-assisted layers can sit on top, but only when they explain themselves. For an unbranded comparison of how matchmaking platforms differ in this regard, our overview of the best event networking apps for 2026 sets out the evaluation criteria that matter.
The CRM anchor is where investor profiles and notes live before, during and after the event. The calendar-sync layer pushes confirmed meetings to investor and founder calendars without manual chasing. The capture system records every pitch and produces clips your founders can send in follow-up emails within twenty-four hours. The live-stream tier serves remote investors who could not travel: typically a two-camera mix with cut-aways and a Q&A microphone feed.
Risk register: five failure modes that decide the day
The same five risks come up at almost every demo day. Plan for them and they become operational hiccups. Ignore them and they become the story of the day.
Investor no-shows: the most common failure mode. Mitigation: a T-2 personal confirmation email from the founder, a T-1 reconfirmation from the operations lead, and a stand-by list of named replacements who can be activated by SMS on the morning. A no-show rate above fifteen per cent suggests confirmation discipline is missing.
Wi-Fi outage during the pitch block: almost always due to bandwidth contention. Mitigation: dedicated hardwired Ethernet for stage and matchmaking terminals, plus an audited bandwidth quote from the venue. A spare 4G or 5G hot-spot lives in the AV cart.
Speaker drop or technical failure on stage: Mitigation: every founder records a screen-only Loom of their demo as a fallback. The moderator can introduce the next founder while the AV team resolves.
Pitch slot overruns: a single seventy-second overrun multiplied across ten founders breaks the meeting schedule. Mitigation: a hard clock visible to the founder, a colour-coded countdown at fifteen seconds, and a moderator authorised to cut. Founders should rehearse with the actual clock at T-1.
Embargoed news leaking in the morning press briefing: Mitigation: a written embargo agreement signed before any cohort detail is shared, and a single named press contact who fields every question. If the founders themselves are embargoed, brief them on what they can and cannot say.
How you’ll know it worked: operational and strategic KPIs
Two KPI layers run in parallel. Operational KPIs tell you whether the day itself was well-run. Strategic KPIs tell you whether the programme produced funding outcomes.
Track these four operational KPIs in real time during the day: check-in throughput (target above sixty investors per hour at peak), pitch-slot adherence (target above ninety per cent on-time starts), meeting-slot adherence (target above eighty-five per cent kept meetings), and Wi-Fi uptime (target one hundred per cent through the pitch block).
Track these four strategic KPIs cohort over cohort: meetings per founder (target above eight), investor Net Promoter Score (target above fifty), fourteen-day follow-up rate (target above sixty per cent), and ninety-day funding velocity (target above forty per cent for cohorts pitching for Series A). The four strategic KPIs are the same ones we recommended in our six-phase follow-up playbook, and they remain the four numbers your board will ask about.
Solution: build the engine behind the stage
The pattern across every successful demo day we have supported is consistent. Organisers who treat the matchmaking platform as the load-bearing operations layer (not as an add-on next to the run-sheet) produce more meetings, higher investor satisfaction and faster follow-up cycles than those who buy the stage first and the platform last. Converve’s meeting-matrix engine powers the scheduled meetings, the check-in flow, the on-site display and the post-event reporting in a single audited system. Every meeting request is logged, every match has a transparent reason, and every founder leaves with a clean follow-up list. If that sounds like the engine you want behind your next demo day, get in touch for a demo.
Conclusion
The demo days that produce term sheets are project-managed twelve weeks out, not stage-managed twelve hours out. Build a cohort brief at T-12, lock the investor thesis at T-10, sign vendor contracts at T-8, open meeting requests at T-6, rehearse at T-1, and run a tight five-window day at T-0. Budget realistically, pick an auditable matchmaking platform, prepare for the five common failure modes, and measure four operational and four strategic KPIs. Do that, and the stage stops carrying weight it was never meant to carry.
Frequently asked questions
How long does it take to plan a demo day?
A first-time demo day takes twelve weeks of structured project planning. Established accelerator programmes that run multiple batches per year can compress the cycle to eight weeks because the cohort brief, vendor contracts and tech stack are reusable. The investor curation timeline does not compress: six weeks of outreach is the floor.
How many investors should I invite?
Aim for one hundred to one hundred and fifty active investors in the room for a ten-startup cohort. To get there, your long-list opens with four to six times that number. Tier-one cohorts confirm at twenty to twenty-five per cent, regional and emerging-market cohorts at ten to fifteen.
How much does a demo day cost?
A ten-startup, one-day urban demo day in Europe or North America runs between EUR 37,000 and EUR 132,000 (USD 41,000 to USD 145,000) including a ten per cent contingency. Venue, AV and catering account for the bulk of the variance.
What is the right pitch length on stage?
Five to ten minutes per founder plus three to five minutes of Q&A is the most common format. Some VC-firm demo days run as short as three minutes per startup to fit more pitches into a single afternoon. Y Combinator now runs one-minute pitches at its main Demo Day, which means every word is rehearsed. Match the length to the depth of cohort traction.
What KPIs should an organiser actually track?
Four operational KPIs in real time during the day (check-in throughput, pitch-slot adherence, meeting-slot adherence, Wi-Fi uptime) and four strategic KPIs cohort over cohort (meetings per founder, investor Net Promoter Score, fourteen-day follow-up rate, ninety-day funding velocity). Track all eight and compare against your last cohort, not the industry average.
Do I need an AI matchmaking layer?
Not by default. A rule-based meeting-matrix platform with an auditable match log delivers more transparent outcomes for a B2B demo day audience. Algorithmic layers can help with cold-start matching at very large events, but every investor and every founder should be able to see the reason for every match. Black-box matching is a trust hazard in a room full of investors.



