Professional services
The software is half of it. The other half is us.
Products do not change how an organisation works — projects do. Our services team is not a separate business unit selling days: it is the same people who design and write the platform, which is why the design decisions survive contact with your plant.
What we do
Four kinds of work, one team
Consulting and workflow design
Coaching and consulting for media companies: workflow analysis, systems design and change management. This is where most engagements start and where the money is actually saved — before anything is bought. We are equally willing to tell you that a workflow needs re-drawing rather than re-platforming.
Typical trigger: a transition between technological platforms, a merger of two operations, or a channel count that has outgrown the way it is run.
Custom software and integration
Software plug-ins and integration tools, either stand-alone or built into systems you already run. Our architecture assumes this: every product is microservices with a full-stack API, so a bespoke connector is a normal piece of work rather than a fork of the product.
Typical trigger: an orchestrator, a traffic system or a third-party MAM that has to talk to the chain and does not have an off-the-shelf bridge.
Project management, installation and training
Delivery on our own products and on selected solutions from other brands: planning, installation, commissioning, operator training and handover. One project manager, one escalation path, and engineers who can answer a question about the code rather than raising a ticket with someone who can.
Typical trigger: a go-live with a fixed date — a channel launch, a season start, a venue opening.
Digitisation and archiving as a service
Digitisation and archiving of broadcasters' and media companies' archival content, carried out by us where you would rather not staff it. The output is not a folder of files: it is an indexed, searchable, rights-aware catalogue in Synaxis or MediaHive.
Typical trigger: a tape library with a decay deadline, or a rights window that makes the back catalogue suddenly worth something.
See the archive workflowHow we run projects
Short lines, senior people
There is no account-management layer between you and the people who build the system. A requirement does not survive three handovers before it reaches a developer, because there are not three handovers — and the architect in the first meeting is the architect at commissioning.
- Map — we document the workflow you have, not the one the brochure assumes.
- Design — an architecture with the trade-offs written down, including what we recommend against.
- Build — configuration, integration and any bespoke plug-ins, in short cycles you can see.
- Commission — installation, parallel running where the risk warrants it, operator training.
- Support — handover to a Gold or Silver plan, with the same engineers behind it.
Start with the workflow, not the quote
Tell us what has to change. The first conversation is an architecture discussion, and it costs nothing.