Yottio
Yottio was a broadcast video participation platform that brought remote audience video into live TV control-room workflows.
View original storyProduct snapshot
What it was
Yottio enabled mobile video participation for broadcast television, letting producers bring remote viewers into live show segments.
Who it was for
Problem / value
It promised interactive TV formats with moderated, broadcast-quality remote video participation.
Core workflow
Producers screened potential participants, selected them for live segments, moderated conversations, and routed video/audio streams into broadcast equipment.
Core dependency
A sales cycle and demo model cheap enough to survive enterprise broadcast buying timelines.
Product form
Pricing model
Revenue came from a mix of professional services, hardware installation, and licensed software. Exact pricing tiers are not disclosed.
Competitors or alternatives
What happened
Summary
Yottio proved a complex enterprise use case with a real broadcast customer, but the cost and timing of repeat sales outlasted its runway.
Outcome
Yottio shut down despite real revenue, customer validation, and enterprise interest.
Core risk
A complex enterprise product can have demand and still fail if each sale requires too much custom work before cash arrives.
Shutdown reason
The founder points to long sales cycles, expensive control-room demos, hardware-heavy implementation, fundraising failure, and cash constraints.
Demand signal
Yottio had real revenue and a broadcast customer, so the issue was not absence of need. The harder problem was that each next sale required expensive demos, hardware, and buyer-side format timing before revenue was committed.
Distribution issue
The team generated strong leads at NABshow and through broadcast relationships, but prospects needed physical control-room demos and production-company buying cycles were longer than startup runway.
Timeline
- Refactored older desktop video technology into a mobile-first HD beta
- Integrated hardware and software for an initial broadcast customer
- Launched on air with Revolt running Voices of Revolt segments in early 2014
- Generated a bit over $200,000 in two-year revenue
- Produced strong leads and prospects at NABshow
- Received a $20 million acquisition offer that later fell apart
- Effectively shut down after running out of cash
Before you build
Why it matters
One successful implementation can prove technical feasibility but still leave the company without a repeatable market motion.
Primary check
Match runway to the buyer sales cycle and demo cost before selling complex enterprise software that needs custom implementation.
Checklist
- What does one new customer cost before contract signature?
- Can the product be trialed remotely or self-serve?
- Is the buyer waiting on another business event before purchasing?
- Calculate full demo-to-close cash needs
- Identify whether buyers can trial without hardware
- Separate first-customer revenue from repeatable sales evidence
- Keep runway aligned with enterprise procurement timing
Relevant if
- You sell complex B2B software
- Your product needs customer-specific setup or hardware
- Prospects require demos before contracts
Less relevant if
- Customers can self-serve trial the product
- Each sale has low implementation cost and short buying cycles
Pre-build tests
- Sell a paid remote demo before traveling or buying hardware
- Prototype a browser-based control workflow for lower-cost trials
- Require prospects to commit budget before custom control-room work
Transferable lessons
- Price custom work to fund the whole delivery cycle
- Avoid hardware-dependent trials until a repeatable motion exists
- Map buyer timing before choosing the segment
- Do not treat one enterprise customer as proof of repeatability
If you build this today
Start with a SaaS-like trial path or a narrower remote-production workflow before taking on hardware-heavy broadcast integrations and show-format sales cycles.