VergeIO
Run of Show · August 20, 2026
Presenter Run of Show
Working document for the three presenters. Enter your credentials to continue.
Same credentials as the session presentation. Contact George Crump if you need access.
Presenter Run of Show · Internal
The Software-Defined Answer to Hardware Inflation
Sixty minutes, three presenters, two live demonstrations. Research first, then a standard, then a running system. This document carries the clock, the handoffs, the question routing, and what to do when something goes wrong.
Simon Robinson
Chief Analyst, Storage and Data Infrastructure, Omdia
Owns the research. 19 minutes.
George Crump
CMO, VergeIO
Host. Owns the clock and the criteria. 17 minutes.
Dave Vincent
Technical Solutions Strategist, VergeIO
Owns both demonstrations. 12 minutes.
The clock
Minute by minute
George owns the clock and calls every transition. Times below are Eastern with Central underneath. Anything that slips comes out of the criteria segment, never out of Simon’s research and never out of questions.
12:40 PM11:40 AM CT
20 min
All three
Presenters in the room
Audio and video check for each person. Dave shares his screen once and confirms the demo environment is live. Confirm who is muted during whose segment.
1:00 PM12:00 PM CT
3 min
George
Open and frame the hour
Housekeeping in two sentences, recording and report go to everyone afterward, questions welcome throughout. State the shape of the hour so the audience knows the vendor material comes later. Introduce Simon and hand over.
1:03 PM12:03 PM CT
19 min
Simon
Act one, the market and the research
What repriced and why it holds, then what four hundred organizations said they plan to do about it. Simon presents his own material. No VergeIO content appears on screen during this block. George and Dave stay off camera and off mute duty.
1:22 PM12:22 PM CT
1 min
George
Bridge out of the research
One question back to Simon to close his block cleanly, then the turn into the second act. Do not summarize his findings back at him.
1:23 PM12:23 PM CT
12 min
George
Act two, three questions to ask any platform
Capacity reduction, media flexibility, and protection inside the same footprint. Four minutes each. This is the compressible block. If the clock is tight, criterion two loses its detail and keeps its headline.
1:35 PM12:35 PM CT
2 min
George
The reframe and the handoff
The category argument, delivered once, immediately before the demonstration tests it. Full wording in the handoff section below. Land the last line and stop talking.
1:37 PM12:37 PM CT
12 min
Dave
Act three, two live demonstrations
Six minutes each. High availability through a node failure, then a running workload moving across media types. Name what the audience should watch before starting each one, and say what it proves when it finishes.
1:49 PM12:49 PM CT
10 min
All three
Questions
George reads and routes. Nobody answers a question addressed to someone else. Routing table below. Hold three seeded questions in reserve.
1:59 PM12:59 PM CT
1 min
George
Close
The three-part close, the report and recording promise, and the demonstration offer. Thank Simon by name and by firm.
Transitions
The four handoffs
Every transition is a place the session can sag. Each one below has a spoken cue so the next person knows exactly when to unmute and start.
George to Simon · 1:03
“We commissioned this research and we get the same twenty minutes of it that everyone else will read. Simon conducted it, so he goes first and I stay out of the way. Simon, over to you.”
The point of the line is to tell the audience the analyst is not being used as a prop. Say it and hand over.
Simon to George · 1:22
“Simon, one last thing before I move on. Of everything in that data, what surprised you most?”
Simon’s cue to wrap. His answer runs thirty to sixty seconds. Then George takes the screen. If Simon has already run past 1:22, skip the question entirely and go straight into the second act.
George into the criteria · 1:23
“Choosing software-defined storage is the easy half of that decision. The hard half is knowing what to demand of it, and the market is filling with products that claim the label and deliver a fraction of it. Here are three questions that sort them.”
This is the sentence that earns the rest of the hour for the teams already on the path. It targets the audience the research just described.
George to Dave · 1:37
“Hyperconverged infrastructure was software-defined storage with the hypervisor attached, and the idea was right. What buyers rejected was the packaging. An appliance, a hardware compatibility list, and a controller virtual machine reserving memory on every node. Those are procurement constraints rather than architecture, and every one of them makes an inflation worse. Strip them away and what remains is the thing four hundred buyers just ranked first. Dave, show them what that looks like running.”
Deliver this once, here, and nowhere else in the hour. The claim gets made and then immediately tested on a live system, which is the only sequence that earns it. Said in the opening five minutes it reads as a vendor defending a category the market moved past.
Questions
Who takes what
George reads every question aloud and names who answers before they answer. Nobody volunteers into someone else’s lane. A question that spans two lanes gets split out loud rather than answered twice.
Simon
Market, method, forecast
- When does supply relief actually arrive
- How the study was fielded and who qualified
- What other vendors and buyers are doing
- Anything challenging the research itself
George
Economics, evaluation, procurement
- How to run the allocated against written audit
- What to demand of a vendor and how to ask
- Used and refurbished equipment
- Licensing, renewals, and the budget conversation
Dave
Architecture and operations
- Failure domains, rebuild behavior, tolerated failures
- Memory and metadata overhead
- Hardware requirements and mixed media
- Migration mechanics and data protection
“What deduplication ratio do you get?”
George
Do not quote a number. Describe global inline deduplication across the whole pool rather than per volume or per backup job, then offer to size it against their own data. Reduction moves with the workload, and a headline multiple invites a test against their least compressible dataset.
“How much memory does the platform consume?”
Dave
Use the documented figure. 16GB base plus 1GB of RAM per terabyte of storage for metadata. Let a technical audience do their own arithmetic, and point them at their current vendor’s sizing guide rather than quoting a competitor’s number back at them.
“Can we run this on consumer drives?”
Dave
No. The hardware requirements documentation does not support consumer-grade disks or off-brand network cards. Quality used enterprise equipment across mixed generations is the honest answer, validated before anything reaches a quote.
“Isn’t this just hyperconverged infrastructure?”
George
Run the reframe. Most software-defined shortlists get built from array-replacement products that decouple storage and leave compute and networking alone. VergeOS decouples all three from one code base. Make the argument, do not lead with the label.
“How many simultaneous failures can it survive?”
Dave
Tolerated failure counts and performance during a failure depend on the configuration. Give the architectural answer, then offer a sizing session against their node count and media rather than a number from memory.
“Why should we trust a vendor-commissioned study?”
Simon
This one belongs to Simon and it is a gift when it arrives. He conducted the research and controls the methodology. George should route it to him immediately and add nothing afterward.
“Your chart puts hyperconverged just above tape.”
George
Positions five through eight sit inside sampling error of one another. The ordinal order is real and the distance between those four is not, which is why the chart shows rank rather than percentages. Say it plainly and move on.
When something breaks
Contingencies
Every one of these has a decision already made, so nobody has to improvise on a live line. George makes the call out loud and the other two follow it without debate.
If the demo environment fails
Say so, then narrate it
Dave names the problem in one sentence and does not troubleshoot on camera. He walks through what the audience would have seen and what it proves, then George moves to questions early. Never fake a demonstration and never show a recording as though it were live. An audience forgives a broken lab. It does not forgive being handled.
If Simon runs past 1:22
Take it out of the criteria
Skip the wrap question and go straight into the second act. Criterion two loses its detail and keeps its headline, which buys four minutes. The demonstration and the question block are protected. They are the two things the audience registered for.
If screen sharing fails
Keep talking off the deck
The slides carry the full thought on purpose, so anyone can present from what is written without the visual. George keeps narrating until the share recovers. If it does not recover inside ninety seconds, the session continues audio only and the deck goes out in the follow-up.
If nobody asks a question
Seed three, addressed by name
Hold three in reserve and put them to a specific person rather than the group. What surprised you most in the data, for Simon. What does the audit look like on Monday morning, for George. What breaks first when a customer runs hot, for Dave.
If a question hits an unsettled number
Take it offline in public
Say the number is not settled, say why the honest version matters more than a fast one, and commit to sending it in the follow-up. An unsourced claim on a live line costs more than the answer was worth, and there is an analyst on the call who will hear it.
If a competitor comes up by name
Credit first, then differentiate
Everyone in this market is having the component conversation and several have handled it well in public. Give the credit, then move to the architectural difference. A vendor who cannot say anything good about a competitor loses the room’s trust for everything else said afterward.
Language
Say it this way
Eight phrases that will get corrected on a live line, and the version that holds. Worth two minutes at the dry run.
Avoid, and use instead
Every item here has been ruled on by Omdia, by engineering, or by the public record.
“Not one of the 400 reported zero impact.”
Every organization in this study is absorbing an impact. Respondents reporting none were screened out, so the zero describes the screen rather than the market.
“Omdia, formerly Enterprise Strategy Group.”
Omdia. Nothing further. Their analyst group existed well before the integration and they have asked us to drop the reference.
“Buyers chose software-defined storage because it decouples software from hardware.”
Buyers ranked it first for planned investment. The hardware-independence reading is ours, offered as our interpretation rather than as their finding.
“Everyone is leaving VMware.”
Nearly everyone is trimming, almost nobody has finished, and the component squeeze now decides whether they can afford to.
“Relief comes in 2029 or 2030.”
2028. That is what the analysts publish and what we can source on a live call.
“The shortage is driving a boom in refurbished hardware.”
Used enterprise equipment is a logical response to confirmed supply facts. No analyst has published data calling it a market trend.
“The industry runs at about 30 percent utilization.”
Ask what percentage of the array is allocated, then what percentage has been written to in ninety days. The gap is worth more than the statistic.
“VergeIO makes flash cheaper.”
Nobody makes flash cheaper. VergeOS changes how much you have to buy and which media you are allowed to buy.
Before Thursday
Pre-flight
Five items still open. Each one has a date and an owner, and the first two decide how the demonstration lands.
Mon 8/17
Dry run with all three presenters, early morning.
Full clock, both demonstrations, and the four handoffs spoken aloud. Two minutes at the end on the language guardrails. Adjust the timing here rather than on Thursday.
Mon 8/17
Settle the demo media question. Dave.
The storage migration should run between two genuinely different media types. Moving a workload between matched drives proves less than moving it from flash to disk, and the published copy promises the second version.
Tue 8/18
Embargo lifts at 9:00 AM ET.
The press release publishes and both Omdia quotes become usable. Nothing quotable goes out before that moment, on any channel.
Tue 8/18
Omdia feedback on the presentation due back.
Revisions land Wednesday, which leaves Thursday morning clear.
Wed 8/19
Zoom session configured. George.
Polling questions loaded, links and PDFs attached to the session, panelist invitations confirmed for all three, and the recording setting verified.
Session presentation: verge.io/storage-squeeze/presentation · same credentials as this page.
Internal working document. Both Omdia quotes carried in the presentation are embargoed until Tuesday, August 18, 2026 at 9:00 AM ET.
Internal working document. Both Omdia quotes carried in the presentation are embargoed until Tuesday, August 18, 2026 at 9:00 AM ET.