How the Three Layer Model Splits Responsibility Between Platform, Management and Production Network

A retake decision sits unresolved for nine days. The producer says the shot met the brief. The platform's content lead says it did not meet the standard. Nobody can point to a document that settles it, and nobody is quite sure whose budget absorbs the regeneration if it goes ahead. Meanwhile two other series in the same slate are approaching the same decision point with the same ambiguity built into them.

This is not a quality problem. It is a responsibility allocation problem, and it is what happens when a platform scales commissioning volume faster than it scales the structure around commissioning. AXIS Management is a working strategy position addressing exactly that gap: an external production management layer sitting between a commissioning platform and the production companies that execute. This piece sets out how responsibility divides across those three layers and, more usefully, why each boundary sits where it does.

The Property Management Analogy, Stated Precisely

The clearest way into the model is the relationship between a property owner and a property manager. The owner holds the asset, decides what to buy, decides when to sell, and takes the return. The manager does not own anything. The manager holds the operating burden: selecting and supervising contractors, enforcing standards, handling tenant issues, reporting on performance, and being accountable when a contractor underperforms. The contractors do the actual work, to a specification the manager sets and enforces.

The analogy holds because it correctly locates the three distinct kinds of value. Ownership and strategic direction sit with the owner. Operating capability sits with the manager. Execution capacity sits with the contractor network. Each is a genuinely different competence, and organisations get into trouble when they assume that holding one implies holding the others. A platform that commissions well is not automatically a platform that supervises production well, in the same way that owning a building well is not the same as running one.

It also explains why the manager is worth paying. An owner with one property can supervise contractors personally. An owner with forty cannot, and the point at which self management stops working is a volume threshold rather than a competence judgement. The same threshold exists in commissioning. This is the frame AXIS Management is built on, and the responsibility split follows from it directly.

Layer One: What the Platform Keeps

The platform keeps everything connected to ownership and demand. Commissioning decisions are the platform's, because the platform holds the audience data, the catalogue strategy, the monetisation model and the balance sheet. No management layer should be deciding which titles get made. The decision about what the catalogue needs is inseparable from the decision about what the platform is, and outsourcing it would be outsourcing the business.

The platform keeps intellectual property and rights. Whatever is produced belongs to the platform under whatever terms the commission specifies, and the management layer's presence in the chain does not change that. It also keeps financing. The management layer coordinates spending against an approved budget rather than funding production and recovering from it, which is a meaningful distinction because it determines who carries risk when a series underperforms commercially.

The platform keeps distribution, marketing and audience relationship. It keeps the definition of what good looks like at the strategic level, expressed as tier expectations and genre direction. And it keeps final acceptance authority, meaning the right to say that a delivered series does not meet the standard. The management layer's job is to make that rejection rare, not to remove the platform's ability to make it.

Layer Two: What AXIS Management Would Hold

The management layer holds the operating burden between commissioning and delivery. That begins with translating a platform's commissioning decision into a production brief that a production company can execute without ambiguity. A great deal of what goes wrong in commissioned production originates here, in the gap between what a content lead meant and what a producer read, and closing that gap is the first function of the layer.

It holds production company selection and supervision. That means maintaining a network of production partners with known capability, matching a given commission to the right partner rather than the available one, setting the standard in writing before production starts, and holding partners to it during rather than after. It holds quality review against defined criteria, which is different from taste based review and is the mechanism that would have resolved the nine day retake argument in the opening paragraph.

It holds coordination across concurrent productions, escalation handling, and reporting. Reporting is worth naming separately because it is the function platforms most consistently underestimate. A commissioning team running a growing slate spends a large share of its week assembling status from multiple producers into something a leadership team can read. That burden scales linearly with volume and it produces nothing. Moving it into the management layer is one of the clearest arguments for the structure existing at all.

What the layer does not hold is equally definitional. It does not commission. It does not own IP. It does not finance. It does not distribute or market. And it does not hold creative authorship, which remains with the writers, directors and production teams doing the work.

Layer Three: What the Production Network Executes

The production network is where the work is made. Scripting, generation, editing, sound, grade, and delivery to specification all sit here, executed by production companies and teams contracted for specific commissions. The network is deliberately plural. A single production company is a capacity constraint and a single point of failure, and a model built on one would reproduce the problem it is meant to solve.

Production partners hold craft authority within the brief. This matters and it is easy to get wrong. A management layer that dictates every creative choice has converted specialist production companies into execution staff and lost the reason for using them. The boundary is that the brief and the standard are set upstream, and how they are met is the production partner's to determine, subject to review against the criteria that were agreed before work started.

Production partners also hold their own delivery reliability. Schedule commitments, milestone reporting, and escalation of problems as they emerge rather than at delivery are contractual obligations to the management layer, which is what makes the layer able to give the platform a reliable view. A network partner who conceals slippage is failing the model at the point where it is most load bearing.

Where the Boundaries Sit and Why

Three boundaries do the real work, and each of them is placed to keep an incentive honest rather than to divide labour tidily.

The first is between commissioning and management. It sits where it does because the party choosing what to make should not be the party assessing whether what was made is good enough. Collapsing those two creates an obvious conflict, and it is the reason a management layer that also commissions would be worse than no management layer at all.

The second is between management and production. It sits where it does because supervision and execution have opposed short term incentives. A supervisor who also produces will eventually be reviewing their own work under schedule pressure, and the review will lose. Keeping the management layer out of production capacity is what allows its quality judgement to be trusted by the platform.

The third is between management and ownership. The management layer never takes IP or financing positions in the work it supervises, because a manager holding an equity interest in one production partner's output cannot credibly allocate a commission to a different partner. Neutrality inside the network is the asset, and it is the first thing that would be lost if the layer started owning things.

How the Commercial Structure Follows the Responsibility Split

The model contemplates three revenue mechanisms, and each one attaches to a different part of the responsibility split rather than being an arbitrary pricing choice.

A set fee covers the operating layer itself. This is the standing capability: the briefing function, the network relationships, the standards documentation, the reporting infrastructure. It exists whether a given month carries two commissions or six, so it is priced as a fixed cost rather than a variable one. Charging this purely as a percentage would make the layer's income depend on commissioning volume, which is the platform's decision and not something the management layer should be incentivised to influence.

A management percentage covers supervision that scales with the work. More concurrent productions require more coordination, more review capacity and more escalation handling, and the percentage tracks that. It aligns the layer with volume it is actually servicing rather than volume it merely observes.

A production margin applies where production is delivered through the network. This is the ordinary commercial position of any party that contracts production and delivers it onward, and naming it plainly matters more than the number attached to it. A platform evaluating this structure should be able to see all three mechanisms rather than a single blended figure, because a blended figure hides which layer is being paid for what and makes it impossible to judge whether the split is fair.

How Quality and Price Tiers Keep the Split Honest

Responsibility boundaries only function if both sides can point at a shared definition of the standard. The tier framework is that definition. It sets out quality bands against price bands, so that a commission is placed into a tier at the point of briefing rather than argued about at the point of delivery.

The mechanism is straightforward. A tier fixes what the platform is entitled to expect at a given budget, which fixes what the management layer must enforce, which fixes what the production partner is committing to when it accepts the work. All three layers are then looking at the same document. The retake argument in the opening paragraph is resolvable in a tier framework because the question stops being whether the shot is good and becomes whether it meets the standard for the tier the series was commissioned into.

The framework also protects the platform from a failure mode that is specific to a managed model. Without tiers, a management layer has an incentive to place work with whichever network partner is cheapest and present the result as meeting a vague standard. With tiers, price and quality move together explicitly, and a platform buying at a lower tier knows what it is buying rather than discovering it at delivery. Given how much of platform economics now depends on throughput and conversion, as the analysis of short drama app growth pressures from adjoe describes, knowing precisely what a given budget produces is a commercial requirement rather than a nicety.

How the Split Would Be Introduced: Pilot to Portfolio

A three layer structure cannot sensibly be adopted wholesale. The go to market position is pilot first, portfolio second, and the reason is that the boundaries described above are easy to state and harder to operate until a platform has watched them work on real commissions.

A pilot means a small number of commissions run through the full structure, with the responsibility split written down and applied exactly as it would be at volume. The point is not to prove that a few series can be produced. It is to test the interfaces: whether the briefing translation actually removes ambiguity, whether tier based review actually resolves disputes faster than taste based review, whether the reporting a platform receives is genuinely sufficient to replace direct producer contact. Those are the questions a pilot answers and a proposal cannot.

Portfolio follows when the interfaces hold. At that point the argument shifts from whether the structure works to what it is worth, and the value case is a volume case. The management layer becomes more useful as commissioning volume rises, because the coordination burden it absorbs rises with volume while a platform's internal appetite for absorbing it does not. Below a certain slate size a platform is usually better off managing producers directly. The threshold is where the structure earns its place.

Axis AI Studios Perspective

Axis AI Studios is an AI native vertical drama production studio, and AXIS Management is our strategy position on how commissioning at volume should be structured. We are describing a model here rather than a service with an operating history behind it, and we would rather say that plainly than imply otherwise.

The reason we hold this position is that we work at the production layer and can see where the burden actually lands. The failures that cost platforms most are rarely craft failures. They are coordination failures: briefs that meant something different to each reader, standards that were never written down, status that took a week to assemble, and disputes that had no defined route to resolution. Those are structural problems and they respond to structure.

What we are prepared to be held to is what sits inside our control, which is the production layer itself and the discipline of the framework described above: standards fixed before production rather than argued after it, tier expectations stated in writing, problems escalated early, and a commercial split a platform can see the components of.

If you are a platform whose commissioning volume has outgrown the structure around it, and you want to talk through where the boundaries would sit in your case, reach us at business@axisaistudios.com.

FAQ

Does the management layer replace a platform's internal commissioning team? No. The model puts commissioning decisions firmly in the platform layer, because they depend on audience data, catalogue strategy and monetisation judgement that only the platform holds. What the layer takes on is the operating burden that sits after a commissioning decision and before delivery, which is the part that scales badly inside a platform as slate size grows.

Why separate the management layer from production capacity at all? Because supervision and execution have conflicting short term incentives. A party that both produces and reviews will, under schedule pressure, eventually be assessing its own work, and the assessment will bend. Keeping the layer structurally separate from production capacity is what makes its quality judgement worth anything to a platform.

At what slate size does this structure start to make sense? There is a threshold rather than a fixed number, and it sits where the coordination burden of concurrent productions begins to consume commissioning staff time that should be going into strategy. Below it, direct producer management is usually simpler and cheaper. Above it, the burden grows with volume while internal capacity does not, which is the condition the model is designed for.

Further Reading

For the operating detail underneath this responsibility split, the explanation of how AXIS Management works between platform and production network covers the stages a commission moves through and the commercial structure around them.

For a direct comparison of the two approaches, the comparison of commissioning through AXIS Management versus managing producers directly works through seven operational dimensions and where each model fits.

For the limits of the layer, the scope boundaries a platform should understand sets out six things an external production management layer should not do and why each exclusion exists.