A build per client
A theme to fork, a player to skin, an app to scope. Every new contract opens a project, and your margin goes to the developer.
Put each client on their own media platform — their colours, their words, their languages, their merchant accounts — and hand over a Studio their team can run without calling you.
A theme to fork, a player to skin, an app to scope. Every new contract opens a project, and your margin goes to the developer.
The homepage wears the client’s colours. The receipt email, the TV app and the error messages still don’t.
One sells season passes, one runs a radio station, one needs nothing but a video library. Each difference turns into custom work.
The client’s team can’t change their own homepage, so every weekend banner comes back to your inbox as a request.
A typical first client, below. The next one might sell merchandise and never broadcast live — same platform, different switches.
A composite launch for a client that runs concerts and a radio station — from brand pack to handover, with no developer involved.
The client’s own Maintenance mode is on, so their new domain shows a branded holding page while the Studio stays open. Dark and light logos, a favicon and two sign-in backgrounds fill the image slots, and the client’s colours repaint live before anyone presses Save.
The client broadcasts in English and Arabic. Switching Arabic on mirrors the entire site right-to-left, player controls included. French stays off, so it never appears anywhere — not on the site, not in the Studio.
This client runs concerts and a station, not a shop or a series. Store and Shows go off, and their pages, menu links, Studio sections and app tabs go with them.
In the phrase editor, “Events” becomes “Concerts” in both languages and an error message gets gentler. Every screen shows the new wording immediately.
A hero slider that only looks a week ahead, a row of upcoming concerts, the radio station and a sponsor carousel. Each block saves itself as it’s dropped.
The client’s Stripe account goes in with test mode on, and the test-credentials button confirms it. Keys are shown back only as their last four characters, and money from the first real sale goes straight to the client.
The account lead builds a Producer role and a Presenter role from the permission matrix and creates a staff account for everyone on the client’s team. Maintenance mode comes off, and the client opens on a platform their own people can run tomorrow.
Walk through a client launch on a call — brand, wording, modules and roles — and see exactly what your team would do on day one.
A 30-minute walkthrough of the live product — no slides.