A login per job
A streaming account for the signal, a ticketing tool for the money, a shop for the shirts and an email tool for the newsletter — and each one keeps its own copy of your audience.
07/ 08SEE IT END TO END
ON AIRREPLACE MULTIPLE VENDORS
Stream the event, sell the ticket and the shirt, publish the story and pull the report from one Studio — with one audience account, one paywall and one ledger instead of a login, a checkout and a customer list per vendor.
- 9 revenue mechanics, one ledger
- One account on web, phone and TV
- Your own Stripe, PayPal or Square
- 54 audited record types
02/ 08YOUR WORLD TODAY
Month end is a spreadsheet
Three payment exports with three different ideas of who a customer is, and a total that matches none of them.
The glue is a person
Somebody checks the ticket list against the viewers who can’t get in, and somebody stays late to download the recording and upload it again.
Your brand stops at each vendor’s edge
The website is yours. The checkout, the receipt email and the TV app each wear somebody else’s look — four logos, four colour pickers, four sets of settings.
03/ 08WHAT CHANGES
- 01A streaming account, a ticketing tool and a manual re-upload.One event page: the signal from OBS or vMix, four ways to charge, simulcast to six destination types and a replay that publishes itself.
- 02Separate app logins and entitlements per vendor.One audience account and one access engine on the website, the phone and the TV — a pass bought in the browser opens the stream on the sofa.
- 03A second store with its own checkout and customer list.A store on the same site for the same audience, with guest checkout through the same merchant accounts and merchandise reported as its own revenue line.
- 04Month-end totals rebuilt from three exports.One Payments console with subscription payments, shop orders and ticket sales on their own tabs, each with its own running counters and a spreadsheet export over any date range.
- 05Four audit logs, if there are any.One activity log across 54 record types — who made the change, their role at the time, and the before and after.
04/ 08WHAT YOU SWITCH ON
Map every tool you pay for to a module. Where a module is a feature switch, switching it off takes its public page, navigation link and app tab away together — and an add-on switches off without losing its data.
Live EventsReplaces the streaming account and the ticket link: a countdown page, an encoder push or an unattended camera, and free, subscription, ticket or hybrid access.
SimulcastKeeps the platforms your audience already follows — Facebook, YouTube, Twitch, X, NFHS Network or a custom destination — each on its own switch, from one signal.
On-demandReplaces the archive on a video-sharing channel: posters, multi-part titles, resume and My List, behind your own paywall.
Subscriptions & plansReplaces the membership tool: rolling plans, season passes and free plans. Renewals run on Stripe and Square, and PayPal takes one-time purchases.
StoreReplaces the second shop: sizes and colours, optional stock tracking that flips a product to Out of stock at zero, and guest checkout on the same site.
PublishingReplaces the blog tool: articles behind the same plans as the video, a comments queue, and contact forms that land in a Studio inbox.
AnnouncementsReplaces the email tool: one message to everyone, viewers, a staff role or newsletter subscribers, by inbox, email and phone push — with the count on screen before Send.
AnalyticsReplaces the outside analytics account: page views, content views, connected TVs counted as TVs, and a PDF report in your own colours.
Roles & activity logReplaces the shared passwords: roles built from 43 permissions in 15 groups, and changes across 54 record types on record.
Forms add-onReplaces the form tool: 24 field types, file uploads, a drawn signature, a fee and a review queue that emails the applicant at each step.
Ticketing add-onLeave offOnly if you sell admission at a venue as well as the stream — barcoded tickets in your colours, scanned from a phone.
RadioLeave offOnly if you run a live audio station. Recorded podcasts live in on-demand.
05/ 08THE CHANGEOVER
An illustrative changeover for an organisation running a streaming account, a ticketing tool, a shop, an email tool and a member spreadsheet. Nothing below needs a developer.
- Week 1 · Monday
Every contract, mapped to a switch
The operations lead lists what each tool does and finds the module that does it. Nobody runs a radio station, so Radio is switched off — no page, no menu link, no Studio section, no app tab.
- Week 1 · Wednesday
The same merchant accounts
The Stripe and PayPal accounts the organisation already sells through go into Payments on Sandbox. Test credentials confirms each one, the keys come back showing only their last four characters, and both flip to Live. The money keeps landing in the same accounts.
- Week 1 · Friday
The member list, in one file
The member spreadsheet goes in through Import on the Users screen: name and email, plus each member’s plan — matched by name to the plans already built — and expiry date. New addresses become accounts, and every skipped row comes back with its line number and the reason.
- Week 2 · Tuesday
A role for every old login
Everyone who held a vendor password gets a role ticked from the permission matrix instead. Each sidebar shows only the sections that job needs, and the activity log records who changed what, with the before and after.
- Week 2 · Saturday
The first event on one page
Saturday’s event is hybrid: members watch free, everyone else buys a ticket. The crew pushes once from OBS, simulcast carries the free pre-show to YouTube and Facebook, and both are switched off when the paid part starts. The shirts sell from the store on the same site.
- Week 2 · Sunday
Nobody re-uploads anything
The replay published itself when the event ended, with its artwork inherited and open to members, and the simulcast destinations were torn down. One announcement goes to every viewer by inbox, email and phone push, with the recipient count on screen before Send.
- Week 3 · Monday
The report from one console
Transactions, Shop orders and Event PPE sit on their own tabs of one Payments console, each with its own counters, and all three export over the same date range. The analytics report goes to the sponsor as a PDF in the organisation’s name and colours.
06/ 08THE NUMBERS THAT MATTER
0revenue mechanics running at once, in one ledger
0publishable content types in one catalogue
0payment providers — your own merchant accounts
0record types in one activity log
THE TALLY LIGHT IS RED
We’ll map every tool you pay for to the module that replaces it, then run an event, a sale and the report on the live product.
A 30-minute walkthrough of the live product — no slides.