What a Management Percentage Buys Across a Commissioning Slate

The Line Item That Gets Circled

Three numbers on the commissioning agreement. A set fee, a management percentage, and a production margin. The first reads as a retainer and the third reads as the cost of making the thing, and both are familiar shapes to a finance team that has approved production spend before. The middle number is the one that gets circled in the review meeting. It is expressed as a proportion of slate spend rather than a fixed amount, which means it grows as commissioning volume grows, and a number that grows without an obvious unit attached to it invites a fair question about what it is buying.

The honest answer starts with what the percentage is not. It is not a finder fee for introducing a platform to a production company. It is not a markup buried in the middle of the stack and relabelled. It is not payment for a weekly call and a status document, although both of those exist and both are visible. A fee attached to spend is a claim that the work being performed scales with the spend. If that claim is false, the mechanism is wrong no matter how modestly the number is set. So the useful conversation is not about the size of the percentage. It is about which categories of work genuinely grow with slate volume, and whether the percentage is attached to those categories rather than to activity that would happen anyway.

That distinction matters more in vertical drama than it does in most content categories, because the unit of commissioning is small and the unit of operation is large. A platform does not commission one series and stop. It commissions a slate, refreshes it on a cycle, and lives with the consequences of every supplier decision for as long as those series stay in the catalogue. The management layer either absorbs that operating load or it does not. Everything below is an attempt to name the load precisely enough that a platform can price it.

Why the Fee Is Proportional Rather Than Fixed

Proportional fees are conventional wherever the work performed tracks the size of the thing being managed rather than the count of transactions inside it. Investment management is the clearest example, where fees are set as a share of assets under management because oversight burden follows the portfolio rather than the number of decisions taken in a given quarter. The manager is not being paid per trade. The manager is being paid to hold responsibility for a body of value that requires continuous attention whether or not anything is actively changing.

Real estate is the closer analogy, and it is the one the Axis AI Studios model is built on. A managing agent on a residential portfolio charges a percentage of collected rent rather than a fee per repair, because the operating load of property management moves with the size and activity of the portfolio. Vendor relationships have to be maintained between jobs. Standards have to be enforced across units that were never inspected in the same week. Compliance and record keeping accumulate. The owner is not buying a series of discrete interventions. The owner is buying the absence of a category of work.

Production management for a commissioning slate has the same shape. The load is not concentrated in the weeks when a series is in generation. It sits in the space between commissions, in the supplier bench that has to stay warm, in the standards that have to survive a change of production partner, and in the record of what was made and how. Attaching the fee to a fixed amount per series would price the visible part and ignore the rest. Attaching it to spend prices the whole operating relationship, which is what is actually being purchased.

There is a second reason, and it is about incentive alignment rather than accounting. A fixed per series fee rewards volume of commissions regardless of their size or quality. A percentage of spend rises when the platform commissions more ambitious work and falls when it does not, which means the management layer is exposed to the same tier decisions the platform is making. That is a healthier position than being paid the same amount to manage a low tier series as a premium one.

The Bench: Supplier Capacity Held Open Between Commissions

The single largest thing a management percentage buys is capacity that exists before it is needed. A platform that manages production partners directly discovers its supplier bench at the moment it needs one, which is the worst possible moment. Sourcing a production partner properly means finding candidates, running paid tests, reviewing output against a written standard, checking references, negotiating terms, and building enough working history to know what the partner is good at. That process takes real time and real money, and it has to be repeated for every capability gap the slate exposes.

Held between commissions, that same work becomes a bench. Partners who have already been tested. Terms that have already been negotiated. A record of which partner handles interior dialogue coverage well and which one is stronger on stylised action, built from actual delivered work rather than from a pitch deck. When a commission comes in, the sourcing question is a selection question rather than a search question. That difference is invisible on any single series and enormous across a slate.

Bench maintenance is genuinely continuous work. Partners change staffing. Tooling moves. A partner who was strong six months ago may have lost the operator who made them strong. Keeping the bench honest means periodic retesting, tracking delivery performance across every commission that touches a partner, and quietly removing partners who have drifted. None of this produces a deliverable a platform can look at. All of it is the reason a commission can be placed with confidence in a week rather than a quarter.

This is also where the three layer structure does its work. The platform sits at the top with the commissioning decision and the catalogue strategy. The management layer sits in the middle holding the bench, the standards and the record. The production network sits underneath, doing the making. Each layer is doing work the other two are not equipped to do, and the percentage is the price of the middle layer existing at all.

Standards That Persist Between Series

A quality standard written for one series is a brief. A quality standard that survives across a slate is infrastructure. The difference is that the second one has to be legible to production partners who were not in the room when it was written, applicable to genres it was not drafted for, and stable enough that a platform can compare a series delivered in March against one delivered in October and know the comparison is fair.

Building that takes more than a document. It takes a tier framework that connects budget to expectation, so that a lower tier delivery is judged against what that tier promised rather than against the best series on the slate. It takes worked examples of acceptable and unacceptable output for each category of shot, because written adjectives do not travel between reviewers. It takes a review protocol that produces the same verdict regardless of who runs it. And it takes revision, because standards that are never updated stop describing what the tooling can actually do.

Across a slate, the value compounds in a way it never does on a single series. The second series inherits the standard rather than negotiating one. The fifth series inherits a standard that has already been tested against four sets of real delivery problems. The twentieth arrives into a framework where the disagreements have mostly been had already. A platform managing partners directly rebuilds some portion of that standard on every commission, usually informally, usually in the head of whoever is handling that particular series.

The percentage buys the persistence. Not the document, which any competent producer can write. The persistence, which requires someone whose job continues after the series delivers.

The Cost of Coordination at Slate Level

Coordination cost does not rise in a straight line with the number of series in production. It rises faster, because every additional series adds relationships rather than just tasks. Three series in production at once means three delivery schedules, three sets of review cycles, three partners with their own capacity constraints, and a set of interactions between them: the partner working on two of the three, the reviewer whose availability is contested, the tooling change that affects all three at different stages.

A platform team absorbing this directly ends up doing a specific kind of work that nobody was hired to do. Chasing status. Reconciling delivery formats that arrived slightly differently from two partners. Translating between a creative note and a production instruction. Working out whether a slipped milestone on one series is a local problem or the first sign of a partner running out of capacity across everything they hold. This work is real, it is time consuming, and it is almost never captured in a headcount plan, which is why platforms consistently underestimate what direct management costs them.

The management layer exists to hold that load in one place, where the patterns are visible. A partner running late on one commission is a schedule problem. The same partner running late on three is a capacity problem that should change what gets placed with them next. Only the layer that sees the whole slate can tell those apart. A platform team seeing one series at a time cannot, which is how supplier problems get discovered late and expensively.

The Data Layer and What It Is Worth Twelve Months Later

Every commissioned series generates a record. What was specified, what was delivered, what was rejected and why, how long each stage took, which partner did the work, which tooling produced which shots, and what the review verdict was against the standard. Collected consistently, that record becomes the basis for every commissioning decision that follows. Collected inconsistently, or not at all, it becomes nothing.

The value of this record is almost entirely deferred, which is why it rarely gets built by a team under delivery pressure. Nobody needs the retake data from series one while series one is in production. The person who needs it is the person deciding, fourteen months later, whether to place a similar commission with the same partner, or whether to commission a sequel, or whether the tier that felt right at the time actually produced work that performed. That person is far better served by structured records than by memory.

Slate level data also answers questions a single series never can. Which genres consistently come in over their retake budget. Which partners hold their quality as their volume with the platform rises. Whether the tier framework is calibrated correctly or whether the middle tier is quietly delivering close to the top tier and being priced as if it is not. These are portfolio questions and they require portfolio data, gathered the same way across every commission, over a period long enough to be meaningful.

The percentage buys the discipline of collecting it during production, when it is cheap, rather than reconstructing it afterwards, when it is impossible.

What the Percentage Does Not Cover

Naming the boundaries is part of making the mechanism credible. The management percentage does not cover the cost of production itself. Generation, editing, sound, localisation and delivery are production work, and they are paid for through the production margin, which is a separate mechanism attached to the work actually performed. A platform that expects the percentage to absorb production cost has misread the structure.

It does not cover creative authorship. The management layer does not originate concepts, write scripts or make the taste calls that determine what a series is. Those decisions belong to the platform, or to a creative partner the platform engages. The management layer translates those decisions into executable specification and holds delivery against them, which is a different job and a smaller one.

It does not cover platform side commercial work. Distribution, marketing, monetisation design and audience strategy sit above the management layer and stay with the platform. And it does not cover the set fee work, which exists precisely because some of the operating load is genuinely fixed rather than proportional. Onboarding, framework setup and the standing infrastructure of the relationship do not get cheaper as the slate grows, so they are priced separately rather than folded into a percentage that would overcharge small slates and undercharge large ones.

Two mechanisms for two different shapes of cost, plus a third for the making itself. The structure is only defensible if each one is doing work the others are not.

How to Judge Whether the Percentage Is Earning Its Place

The test is not whether the management layer is busy. It is whether the platform team is doing less of a specific kind of work than it was before. That is measurable, and it is worth measuring deliberately rather than by feel.

Start with sourcing time. How long does it take from commissioning decision to signed production agreement, and how much of that time falls on platform staff. If the answer has not moved, the bench is not real. Then look at review load. How many hours does the platform team spend per delivered series on quality review and rework negotiation, and is that number falling as the slate grows or holding flat. A management layer that is working produces a declining per series review burden, because standards and partners are both improving.

Then look at variance. Across the last six delivered series, how far apart were the best and worst outcomes against the same tier expectation. Wide variance under management means the standard is not being enforced, which is the core of the job. Narrowing variance is the clearest evidence that the layer is functioning, and it is the outcome that matters most to a platform building a catalogue rather than a single hit.

Finally, look at what happens when something goes wrong. A missed delivery window, a partner capacity failure, a tooling change mid production. The question is who notices first, how quickly a recovery plan appears, and whether the platform team had to build it. If the answer is that the platform team built it, the percentage is buying a report rather than a function.

Axis AI Studios Perspective

Axis AI Studios is an AI native vertical drama production studio based in the Netherlands. AXIS Management is the working strategy position for the operating layer described here: an external production management function sitting between a commissioning platform and a network of production partners, structured on the property management model rather than the agency model.

The three revenue mechanisms are deliberate and separable. A set fee for the standing infrastructure that does not scale with volume. A management percentage for the operating load that does. A production margin on the work actually made. Each one is attached to a distinct category of cost, which is what allows a platform to interrogate any of the three without unpicking the others. The quality and price tier framework sits underneath all three, connecting budget to expectation so that delivery can be judged against something written down rather than against mood.

The go to market is pilot to portfolio. A platform runs a single commission through the structure, sees what the layer actually absorbs, and decides on that evidence whether to move a slate into it. That sequence exists because the argument above is only worth as much as a platform can verify on real work of its own.

For platforms weighing what a management layer would absorb from their own team, or considering a first commission through the structure, write to business@axisaistudios.com.

FAQ

Is a management percentage the same as a production markup?

No. A markup is added to the cost of work performed and rises with that work regardless of what is being managed. A management percentage is attached to slate spend and pays for the operating layer that exists between commissions: the supplier bench, the standards framework, the coordination function and the production record. In the Axis AI Studios structure the margin on production work is a separate mechanism, disclosed separately, so a platform can see which number is paying for what.

Does the percentage make sense for a platform commissioning only one or two series a year?

Less so, and that is the honest answer. A proportional fee is designed for the operating load that grows with slate volume, and at very low volume most of the real cost is the fixed infrastructure rather than the scaling part. That is what the set fee exists for. A platform at that volume is usually better served by running a single pilot commission through the structure and deciding on the evidence, rather than committing to a slate arrangement before there is a slate.

What happens to the percentage if commissioning volume falls?

It falls with it, which is the intended behaviour. A fee attached to spend moves in both directions, so a platform that pauses or reduces its slate is not carrying the full cost of a management layer sized for volume it is no longer commissioning. The fixed portion of the relationship stays with the set fee, which is deliberately the smaller and more predictable of the two.

Further Reading

For a fuller picture of how the layers divide responsibility between a commissioning platform and the partners doing the work, the operating model between platform and production network covers the structure the percentage is attached to and what sits in each layer.

For the framework that connects a commissioning budget to what a platform should expect back, the quality and price tier framework covers how tiers are defined and how delivery is judged against the tier that was bought.

For how the operating load changes as commissioning volume rises rather than staying flat, the scaling picture from three series to a hundred covers what changes at each volume band and what has to be built before it is needed.