Product

Your brand, our pipeline

· By · 5 min read · Product

The moment a client sees another vendor's branding on the deliverable page, your markup stops looking like a service and starts looking like a middleman fee. White-labelling is not vanity — it is the difference between selling video production and forwarding someone else's. Here is what it actually covers, and what it does not.

The moment your markup starts looking like a fee

Agencies have resold production forever. You scope the work, you take responsibility for it, you charge for judgement — and the client never meets your edit suite, your freelancers, or your stock library. That is not concealment; it is what buying a service means.

Software broke that convention by putting vendor branding on the deliverable. The client clicks the link you sent, sees somebody else's logo above the video, and does the arithmetic out loud: so what exactly are we paying you for? The work did not change. The framing did.

White-label is two different things

It helps to separate them, because they solve different problems and they are not the same feature.

What it coversWho sees it
The agency workspaceMembers, permissions, and allocating productions to the people doing the work.Your team, internally.
Portal brandingYour logo and colours on the client-facing review page.Your client, externally.

The first is throughput. The second is positioning. Most agencies want both, but they are worth understanding separately because only one of them is visible to the people paying you.

One queue instead of five inboxes

The constraint on an agency's client list has never been talent. It is throughput — every client wants regular video, every video is a scramble of scripts, voices and edits, and so the client list gets capped at whatever the edit bay survives.

The workspace changes the shape of that. An agency admin manages the seat list, sets what each member can do, and allocates productions to them. Every client's work flows through a single queue rather than five freelancers' inboxes, and the same pipeline handles all of it.

What that buys, concretely, is that your senior people review plans instead of assembling timelines. Since each production asks for exactly one approval — the Phase 1 storyboard — one experienced reviewer can shepherd a volume of work that previously needed a room. That is the actual mechanism behind taking on the eleventh client without hiring the sixth editor.

Brand presets belong to the agency rather than to individuals, which is the other half of it: each client gets a saved identity, and producing for that client becomes selecting them from a dropdown rather than remembering their hex codes.

Your brand on the page the client actually opens

The client-facing artefact in StudioCut is the Review Portal — a read-only, no-login page carrying the finished video, generated from a link you share off a completed render. It is the only StudioCut surface your client ever touches.

On agency and white-label plans, that page wears your brand: your logo, your colours. On other plans it carries StudioCut's. That single difference is what "white-label" means here in practice — not a separate product, but whose name is above the video when the client presses play.

You configure it once at the workspace level, and from then on every deliverable page for every client carries it.

Plan-gated, and worth stating plainly: portal branding is an agency / white-label plan capability. It is not a default on every tier, and no amount of configuration turns it on below that.

What it does not cover

Three limits, stated up front so nobody discovers them mid-pitch.

First, the portal is genuinely read-only — no approve button, no comments, no expiry picker. Branding it yours does not add those; it changes whose logo sits above a page that still only plays a video.

Second, white-labelling the deliverable page is not the same as running the whole application under your own domain. If your pitch depends on the client never seeing any other name anywhere, scope that conversation with us rather than assuming.

Third, everything else in the pipeline is unchanged. White-label affects presentation, not production — the same five phases, the same single review gate, the same credit arithmetic.

Why the margin holds up

The reason agency work resells well here is that the cost side is predictable in a way human production never was. A production's credit cost is a flat base plus a per-30-second rate set by the quality tier — visible in the wizard before you commit — so you can quote a client a number that is derived rather than hoped for.

And because fixing a plan at the storyboard gate costs nothing, the revision rounds that historically ate agency margin are free until you approve. Round three costs what round zero cost: nothing. The render happens once, afterwards, at the price you already saw.

That combination — a fixed input cost, free revisions before generation, and your brand on the deliverable — is what makes reselling this feel like selling a service rather than forwarding a vendor.

A note on this page's screenshots: we have not included interface shots of the agency workspace or the branded portal here. The captures we had did not actually show those screens, and we would rather ship a post without an image than caption a screenshot as something it is not. If you want to see the real thing, ask us for a walkthrough.

The one-sentence version: the agency workspace gives one admin the members, permissions and allocation controls to run many clients through a single queue — and on white-label plans, the client-facing review page carries your brand instead of ours.

Further reading

Put your name on the door

Run every client through one workspace, allocate work to your team, and hand over a review page that carries your brand instead of ours. Talk to us about agency plans.

Get Started Free