Every customer implementation was different. Though the underlying platform remained the same, each customer came with their own infrastructure, branding requirements and ways of working. This meant defining how the platform would be tailored to each customer — from product offerings to live TV and VoD features, subscription packages, and supported devices. The first step was about understanding the customer's business, technical landscape, and expectations, and translating those into a shared project plan.

From technical dependencies to business priorities, the initial phase focused on discussing timelines, defining scope, aligning stakeholders and uncovering potential risks early. This established the context that would shape the rest of the project.

From 2024 to 2025, I managed the onboarding of customers onto the Zattoo’s white-label TV streaming platform, coordinating SaaS implementation for network operators across Europe. Each implementation involved bringing together different systems, teams, and requirements to transform a platform into a fully customised product.

My role was to keep people, priorities, and dependencies aligned throughout the iterations — coordinating stakeholder communication from initial requirements and technical groundwork through customisation, testing and go-live. The process involved multiple layers of planning, technical coordination, and collaboration that sit between a platform and the final customer experience. This page is a look into the process of planning, building and implementing the streaming service.

The process

By this stage, most of the technical work had been completed. The remaining effort centred on coordinating the activities that would bring the service into production and ensuring a smooth and well-coordinated launch. 

Reaching this stage was exciting because the platform finally felt real. Besides technical delivery, customer readiness, operational handover, and launch communications all had to come together before the service could go live. From user migration and final UAT to launch planning and marketing communications, I coordinated the final stages of each workstreams to keep everything moving towards launch.

And once all pieces came together, it felt satisfying to finally see the platform ready to be operated on multiple devices and experienced by thousands of users.

With the technical groundwork in place, the platform could begin to take shape. This was the stage where a generic product gradually became a service tailored to each customer's brand and audience —from visual identity and feature configuration to content catalogues and regional content rights.

While development teams focused on configuring the platform, I coordinated priorities across customers and internal teams, overseeing technical workflows, sprints initiatives and ongoing cross-functional collaboration, while managing issues, changes and progress across video operations.

Working closely with engineering teams and customer stakeholders, I coordinated testing activities across multiple devices and ensured feedback was incorporated before moving to production deployment.

With the different layers of the service in place, the focus shifted to bringing them together into a cohesive experience and refining the platform through testing and feedback. Changes were incorporated along the way, preparing the service for final UAT across supported devices.

As the implementation progressed towards launch, part of the plan was also to prepare teams who would operate the platform externally. Together with the customer, we held the Operations Workshop to establish the processes and tools needed for a smooth handover. People were trained on how to use ticketing and monitoring tools to ensure that support teams were ready to manage the platform from day one.