1
Week 1 · day 1
Kickoff meeting
Day one, with Salto’s technical point of contact. We map how post actually runs today — the systems, the handovers, the delivery formats — so we know exactly where EdMon slots into the chain.
We integrate EdMon into how Salto already works — company-wide, not per production. It starts with your technical point of contact and works outward: integration first, then the edit assistants, then the story producers. Three weeks of hands-on work, then we step back.
Everything runs through one technical point of contact at Salto. They learn the system properly, own the integration, and stay our counterpart afterwards — which is why the weekly check-ins are with them and not with a rotating cast.
Day one, with Salto’s technical point of contact. We map how post actually runs today — the systems, the handovers, the delivery formats — so we know exactly where EdMon slots into the chain.
Two weeks alongside the same person. We integrate EdMon into Salto’s existing pipeline — storage, naming, formats, delivery — and hand the setup an owner inside the building.
We onboard the edit assistants who will sit in EdMon across your productions. They are the ones using it daily, so they learn it on the integrated setup — inside the integration fortnight, not after it.
The first real ingest through the integrated setup, followed by a check-in with the technical point of contact and the edit assistant. We confirm everything landed correctly before anything is built on top of it.
A session teaching EdMon’s web interface to the story producers who will be working in it. By now the material reaching them has already come through Salto’s own pipeline.
Three weeks of 15-minute calls with the technical point of contact — short by design. We are only confirming things are on track, not running training.
Integration and training run across weeks 1–3. From week 4 all that is left is a fifteen-minute call a week while Salto runs it.
→ By week six, Salto runs the full workflow in EdMon without us in the room.
An integration done for one production has to be done again for the next. A company integration does not. New productions start in a system that is already part of the pipeline, producers move between them without relearning, and the knowledge stays with your technical point of contact rather than with us.
One named technical point of contact who can give us week 1, the edit assistants for their onboarding in week 2, and a live production to run the first ingest on. The story producers only need the one workshop.
Two weeks to go-live.
Six to running it alone.
Nobody changes editing system and nobody learns a new craft — EdMon sits inside the pipeline you already run. The integration, the training and the support through it are all included.