Investors
The operational layer underneath live events.
Live events still run on PDFs, spreadsheets and email threads. Startion is building the operational layer underneath them — one shared production system with connected workflow apps for artists, venues, festivals and production teams.
The problem
A high-coordination industry on document-era tools.
Live events are operationally complex and time-critical. The work — advancing a show, exchanging riders, building a patch list, running a production day — happens across artists, venues, festivals, technical crews and management, often for the first time together.
The tools they share are PDFs, spreadsheets and email. Every production reinvents the same coordination from scratch. The cost is paid in errors, reprints, double-bookings and show-day surprises.
Market opportunity
Operational software is the open middle of the live events stack.
Existing software in the industry covers the edges — ticketing, booking, accounting, marketing. The operational middle (advance, rider, patch, runsheet, crew) is largely undigitised at the workflow level.
The buyers are global and structurally similar: tens of thousands of venues, festivals, production companies, artist management firms and touring crews — each running the same coordination problem with the same legacy toolset.
Product suite
Connected operator-grade workflow apps. One shared event.
ArtistRider — riders, hospitality and tour advance for artists and management.
StageRider — patch, stage plot, input list and technical advance for production crews and venues.
Eventiner — event operations, runsheets and schedules for festivals, venues and production companies.
Each workflow app is a standalone product with its own buyer and pricing — and a wedge into a different side of the same production.
Shared data advantage
Startion workflow apps share one live event — not a sync layer.
Every Startion workflow app reads and writes against the same real-time event model. Adopting one workflow app pulls the next into the same account, because the data already lines up.
This produces three compounding effects: faster expansion inside an account, increasing switching cost as more of an event lives on Startion, and a steadily improving data graph across the industry.
Strategic expansion
A shared event model extends into adjacent operational modules.
The same architecture extends naturally into the operational neighbours of advance and runsheet — guest management, travel and logistics, settlement, asset tracking — each addressable as a new module against existing accounts.
Broader industry-graph products (including Bandland) are a longer-horizon optional layer, not core roadmap.
Long-term vision
Become the operational standard for how live events are coordinated.
The goal is a default — the layer that artists, venues and production teams reach for, the way design teams defaulted to Figma and engineering teams defaulted to Linear. Once the rider, the patch and the runsheet live on Startion, the rest of the operation follows.
Team & industry insight
Built by operators with show-day experience.
Startion is built by people with direct production and touring background. Every product decision is reviewed against real show-day use — not abstract personas, not consulting frameworks.
This shows up as faster product cycles, sharper feature scoping and a credibility advantage with the operators we sell to.
Investment opportunity
Recurring SaaS, three buyer segments, one compounding graph.
— Recurring SaaS across three distinct buyer segments inside the same production.
— Multi-product land-and-expand inside the account, enabled by a shared data model.
— Compounding data and switching-cost advantage as adoption deepens.
— Category-defining position in an underserved operational market with universal demand.
Talk to the founders.
For investor conversations, deeper material and product walkthroughs.
Get in touch