The next generation of MediaTech won’t be judged by how much it can do. It will be judged by how much you no longer have to do. In this Part 3 of 3 series on Service-as-Software, Philippe Brodeur looks at the value drivers for software going forward.
Nobody wakes up wanting another enterprise video platform.
Nobody arrives at work thinking: “What we really need is a MAM with 17 more features.”
They have more practical problems.
Find the footage. Get it to the editor. Work out which version is current. Reuse the campaign we spent a fortune shooting three years ago. Get the approved asset where it needs to go.
And please stop making Sarah chase everyone on Teams to make it happen!
That’s what organisations actually buy technology to solve.
Yet somewhere between the problem and procurement, we stop talking about the work and start comparing software. Features. Integrations. Users. APIs. AI capabilities. Another spreadsheet with 200 rows and several reassuring shades of green.
All legitimate. But increasingly, I think we’re asking the wrong first question.
Don’t start with: What should our video software be able to do?
Start with: What should our operation no longer have to do once we’ve bought it?
That’s where Service as Software gets interesting.
The MAM gets a job
Media technology has spent decades answering increasingly sophisticated versions of one question: Where is our content?
We catalogued it, centralised it and added metadata, permissions, versions, rights, workflows and governance.
All essential.
But AI gives us another question: Now that the system knows all this, what can it do about it?
That’s the shift from a system of record towards a system of action.
If a platform understands what’s inside a video, which version is approved, who can use it and what should happen next, returning a search result is only the beginning. It can surface the right material. Trigger the next predictable step. Apply a known rule. Move content forward. And when something genuinely requires judgement, it can send the exception — with context — to the right person.
We’ve spent years making media platforms better informed.
The next phase is making them useful when nobody is clicking.
Buy the result
This is where outcome needs a little discipline.
“AI-powered semantic search” isn’t an outcome. It’s a capability. An editor finding the right shot without waiting for the person who knows the archive is an outcome.
“Workflow automation” isn’t an outcome either. Approved content reaching its next stage without somebody downloading it, uploading it, emailing three people and updating a spreadsheet is.
Capabilities describe what software contains. Outcomes describe what changes because you bought it.
For video operations, those changes are tangible: Less waiting. Fewer handoffs. More reuse. Faster turnaround. More capacity. Lower cost. Less risk.
That’s a much better business case than counting buttons.
Look outside the box
Here’s one of the most useful questions we ask at Overcast: What still happens outside it? You may already have an excellent DAM. A capable MAM. Cloud storage. Production tools. Workflow technology.
Great. Keep them. Now look at everything happening around them.
- Where are files still downloaded and uploaded?
- Where does somebody re-enter information?
- Where does a workflow stop because someone has to remember what happens next?
- Where does a specialist repeatedly perform the same objective check?
- Where does “approved” still mean another team has three hours of work before the asset is actually usable?
That’s where the opportunity lives. The future of MediaTech isn’t necessarily another giant rip-and-replace exercise. It’s making the work between the boxes disappear.
SOK bought reuse
SOK is a good example because the outcome sounds almost boring.
They wanted to reuse old video. Easy, surely?
Except “just reuse it” can mean locating the project, finding the right source material, reconstructing its context and getting everything back into a usable production workflow.
At some point, making something new starts to look easier than reusing something you’ve already paid for.
Overcast changed that equation.
As Juho Kahilainen, Content Team Lead at SOK, puts it: “Overcast is especially useful when accessing older projects to make new edits. The whole process can now be completed by one person without lowering our quality requirements, allowing us to focus on scaling production.”
That’s Service as Software in one sentence. Not “better archive functionality.” One person can now complete work that previously required several.
The outcome is reuse. The economic result is capacity. The technology is simply how you get there.
Two things to buy
This points to a distinction I think will become increasingly important in MediaTech. There are platform outcomes and transactional outcomes.
Platform outcomes are persistent. Your video operation becomes easier to run. Content is understood, findable and reusable. Governance travels with the media. Workflows move more efficiently. More volume doesn’t require proportionately more coordination.
That’s the role of Overcast MAX. You’re buying operational capacity.
Transactional outcomes have clearer edges: Analyse this asset. Perform this check. Prepare this content. Complete this process. Tell me if there’s an exception.
Large video operations will increasingly need both: a persistent operational platform underneath and autonomous pieces of work happening on top. Which is also why, as I argued in the previous article, pricing everything by seats makes progressively less sense.
Different shapes of work need different shapes of software — and different economics.
Spend humans wisely
None of this means every decision belongs to a machine. A technical rule may be objective. A rights or editorial decision may not be. The goal isn’t removing humans. It’s spending humans wisely. Automate the predictable. Escalate the ambiguous. Keep accountable people accountable.
And stop requiring talented people to spend Wednesday afternoon doing something software can reliably finish before lunch.
Start with the outcome
So how should you buy MediaTech differently?
Pick one valuable workflow. Archive reuse. Production handoff. Review and approval. Campaign readiness. Content delivery.
Follow it from beginning to end.
Who touches it? Where does somebody wait? Where is information lost? Where is work repeated? Where does the process leave one system and mysteriously become somebody else’s problem?
Then define the outcome.
Don’t say: “We need AI search.”
Say: “An editor should find and reuse the right footage without waiting for somebody who knows the archive.”
Don’t say: “We need workflow automation.”
Say: “Approved content should move through predictable stages without somebody coordinating every handoff.”
Now you’ve got something worth buying.
One last question
Across these three articles, I’ve argued that AI is changing enterprise software in three connected ways.
- Software is starting to do the work.
- Pricing therefore needs to follow the work.
- And buyers should increasingly define technology by the work they expect it to remove or deliver.
So here’s the question I’d put into every future MediaTech RFP: What will our operation no longer have to do because your software is there?
It’s uncomfortable for vendors because “we have that feature” isn’t an answer. And it’s uncomfortable for buyers because it forces them to define what they’re actually trying to change. Good.
Enterprise technology could use a few more uncomfortable questions. After three articles on Service as Software, that’s where I’d land: Stop buying the software. Start buying what happens because of it.
FAQs
What is a video operations outcome?
A measurable improvement in how video gets used: faster retrieval, greater reuse, fewer handoffs, shorter turnaround, greater capacity or lower cost.
How is buying an outcome different from buying software?
Software procurement starts with capabilities. Outcome-led procurement starts with what needs to change operationally, then identifies the technology required to deliver it.
What’s a system of action?
A system of record knows what exists. A system of action uses that knowledge and operational context to help make the next thing happen.
Does this replace DAM or MAM?
No. DAM and MAM provide important foundations. The interesting opportunity is often the work still happening around and between them.
What’s a platform outcome?
An ongoing operational capability across the video estate: better reuse, faster production, connected governance and greater capacity.
What’s a transactional outcome?
A defined piece of work: analyse an asset, perform a check, prepare content or complete a known process.
Where does AI fit?
AI understands what’s inside video. The value comes from connecting that intelligence to workflows, rules, permissions and context so useful work can follow.
Does more automation mean less human review?
Not where judgement matters. Automate predictable work and send ambiguous or accountable decisions to the appropriate person.
What value can we expect using Overcast?
Faster campaign launches, reduced operational drag, better reuse of content, improved compliance, and data-driven insights. Overcast transforms video from a bottleneck into a strategic asset.
Do we need to replace our existing MediaTech stack?
Not necessarily. Ask “What still happens outside it?” first. Fix the gaps that create meaningful cost, delay, risk or lost capacity.
How should we measure video outcomes?
Measure close to the workflow: retrieval time, reuse, turnaround, manual interventions, capacity, production effort and costs removed.
Still have questions? Contact our team
Take one real video workflow. We’ll identify the work still being performed manually, define the outcome that matters — and map what your technology should be responsible for delivering.
