How you buy it

You own it. Or we run it.

Two engagements, one system. We build it around your workflow and hand you the system, or we take the operating seat and run it for you. What changes is what you own, and how much you can publish.

Two engagements, one system.

Same pipeline underneath, built the same way. What changes is who owns it, how much you can publish, and whether you pay once or every month.

Build & hand over You own it and run it

We design and build the system around your workflow, run it alongside your team until the output is consistently publishable, then hand over the running system, your credentials and the documentation.

Includes 01–08
  • 01 Discovery and workflow mapping
  • 02 Custom pipeline build, all ten steps of the run
  • 03 No content limit. Publish as much as you want
  • 04 Everything runs and stays on your own machines
  • 05 One system covers every brand you handle
  • 06 One build cost, then only what the vendors charge
  • 07 Team training and a supported handover window
  • 08 Guaranteed bug support and change requests
For
Teams with in-house operators who want the asset on their own books.
Outcome
A production system you own, staffed by the team you already have.
Fully managed We run it for you

We already run this system. We onboard your brand onto it, connect your channels and start publishing, usually inside a week. You approve the plan and finished content appears on your channels.

Includes 01–08
  • 01 Live in under a week, with no build to wait for
  • 02 A monthly plan, far below the cost of a build
  • 03 A content allowance set by your package
  • 04 Day-to-day operation, monitoring and publishing
  • 05 Content plan development with your team
  • 06 Analytics you can check any time, plus a monthly report
  • 07 We carry the responsibility for publishing on schedule
  • 08 Move to your own system whenever you decide to
For
Teams who want the output now, or who want to prove the workflow before committing to a build.
Outcome
Published content on schedule, with no system to run and no new headcount.

The managed route

Not ready to build one? Start on the monthly plan.

We already run this system for other brands. We onboard yours, connect your channels and start publishing, usually inside a week. No build to wait for, no system to run, and you can commission your own whenever you decide to.

Same system. Different deal.

Both run the same pipeline. What changes is who owns it, how much you can publish, and whether you pay once or every month.

How build and hand over compares with a fully managed engagement across eight decision points.
Decision point Build & hand over You own it and run it Fully managed We run it for you
Who owns the system You do. The system, the files and the credentials sit where you choose — your own machines by default. We do. You are buying the output rather than the asset.
How much you can publish The difference most people feel first. No limit. As many long videos, shorts and posts as you want to run. A monthly allowance set by your package. Need more, move up a package.
How you pay One build cost, then only what the AI and platform vendors charge for the runs you make. A monthly plan. Much lower to start, and it continues for as long as you use it.
Time to the first published run Seven to twenty one days, depending on scope. Usually under a week. There is nothing to build.
Where your files and credentials live On your machines by default, or your own cloud if you pick it. Either way the logs, finished files and keys are yours. With us, under the same privacy and security commitments we run everything on.
Running several client brands The deciding factor for most agencies. One system covers all of them, because it is built around how you work. One package per brand.
Who carries it when it matters You operate it. We guarantee the build and fix anything that breaks. We carry it end to end, including getting content out on schedule.
Reporting Analytics sit in your own system, in front of you. Analytics you can check remotely, plus a monthly report.

From first call to a finished system.

Five steps to a system of your own. The managed plan skips almost all of it: we onboard your brand onto the system we already run, usually inside a week. Either way, what the finished thing actually did on one account is published in full.

  1. 01 First call Requirements analysis We go through how your content gets made now and mark what is slow, what breaks, and what is worth fixing first. You leave knowing whether a system is worth building for you.
  2. 02 Workflow design We agree what the system runs on its own, what runs with a person in the loop, and what stays manual, then the same again for review. Every input and every output is named, and the whole path is joined up end to end.
  3. 03 Pipeline build Built to run where you want it: in the cloud, entirely on your own machines, or a mix of both. A dedicated host or a local machine for anything that has to run around the clock, on macOS, Windows or whatever your team already uses.
  4. 04 Test run We run the whole thing as a demo, from the first upload through to the finished output, and tune it until it is right. Nothing is deployed until you have watched a full run and approved it.
  5. 05 Ongoing Deploy and support You get the system and do your work through its front end. The code behind it stays with us, the way a studio keeps its working files, which is how we can stand behind the build and fix anything that breaks. When you want the pipeline changed later, you tell us and we make the change with you.

How we scope and price.

The monthly plans are published in full. A build is priced per engagement, after the call: a single-channel pipeline and a multi-brand system are not the same job, and one rate card would be honest about neither.

What moves the number 01–06
  • 01 Channels Each one is its own render specs, metadata rules and publishing integration, plus the logic deciding which cut goes where.
  • 02 Brands One profile is one voice, one claims policy, one template set. An agency running twelve clients needs twelve, kept apart.
  • 03 Volume per month Ten runs and four hundred are different engineering problems. Queueing, cost control and failure handling all change shape.
  • 04 Approval workflow One reviewer is a gate. Legal at script, brand at render and client sign-off before publish is a workflow with an audit trail.
  • 05 Integration depth Reading your content calendar is straightforward. Writing back into a DAM, a PIM or a client portal is the part that takes weeks.
  • 06 Who operates it after Handover needs runbooks, training and a supported window. Us operating it needs staffing and reporting instead.
Indicative timelines To first live run
Under 7 days
Fully managed. We onboard your brand onto the system already running, connect your channels and start publishing.
Up to 21 days
Your own custom build. Seven days at the short end for one brand and one channel, twenty one at the long end for multi-brand with approval workflows.
What we need from you 01–03
  • 01 A named content owner One person who can approve a plan and settle a brand question without convening a committee.
  • 02 Your own channel accounts YouTube, Meta and the rest, with a role granted to your system. Nothing publishes from a shared pool.
  • 03 A claims policy, or the appetite to write one What your content may and may not assert. The script stage enforces it on every run.
  • Fully managed

    Priced by how much you publish each month, on a monthly plan. Live in under a week.

    View pricing
  • Your own build

    Scoped to what has to be built, from $2,000. Tell us the shape of it and we will quote it.

    Get a quote

Choosing between them

Which one is right for us?

Which of the two should we start with?

If you publish at volume, run several brands, or want the cost to stop climbing, build your own. If you want output this month, or you want to prove the workflow before committing to a build, start on the managed plan. The honest test is whether the content limit in a monthly package would constrain you. If it would, a build pays for itself; if it would not, the plan is the cheaper answer.

Can we start on the managed plan and build our own later?

Yes. You get published content while you decide, and you already know what the output looks like on your own brand before you commit to a build. When you are ready, tell us and we build your system. Your channels are in your name throughout, so nothing has to be untangled.

We run several client brands. Which one works out better?

A build, in almost every case. One system covers every brand you handle, because it is built around your workflow, and each client gets its own profile inside it. On the monthly plan it is one package per brand, so the cost scales with the number of clients rather than staying flat. That is the single biggest difference for an agency.

What does the monthly plan include, and what does it not?

It includes the production, the publishing, the monitoring and the reporting: we runs the system and carries the responsibility for getting content out on schedule. It does not include owning the system. The files and credentials sit on our side, and the amount you can publish is set by your package rather than being open-ended.

How quickly can we actually be publishing?

Under a week on the monthly plan, because there is nothing to build: we onboard your brand onto the system already running and connect your channels. A build takes seven to twenty one days depending on scope, and you watch a full run and approve it before anything is deployed.

Do we need someone in-house to run it?

For a build, yes: one person to monitor it, and someone who can sign off a script or a render. For the monthly plan, no. That is the point of it — we operate it and you approve the plan. Neither model needs you to hire a production team.

What happens to our channels if we stop?

They stay yours. Your social accounts are connected in your own name under both models, not held in a shared pool, so stopping does not cost you the audience you built. With a build, the system and everything on it is already on your machines.

Not sure which one fits you?

Bring your monthly volume and the number of brands you run to the call. We will tell you plainly whether a build pays for itself at your size, or whether the monthly plan is the cheaper answer.

Book a build call