Adding delivery capacity without disrupting a live streaming service
MAXstream is Telkomsel’s video streaming service, available across Android, iOS, desktop, and Android TV. As the platform continued to evolve, Accedo Broadband—Telkomsel’s appointed technology partner—needed additional development capacity to maintain and improve the product on a daily basis.
The challenge was not to create a new application from the ground up. MAXstream was already a live, multi-device service with ongoing enhancement, adjustment, and maintenance needs. Accedo needed additional developers who could join its existing team, work under its project management structure, and contribute without creating a separate delivery process.
Suitmedia provided dedicated developer resources through a managed service model. The arrangement gave Accedo additional capacity while preserving its existing ownership, priorities, and ways of working. It also created a practical first step toward supporting Telkomsel’s transition from international to local development partners.
A growing product needed more capacity, not more complexity
1. MAXstream had to improve while remaining operational
Streaming platforms are continuously evolving. Users expect improvements in performance, features, compatibility, and content access, while the service must remain available across several types of devices.
This creates a constant flow of development work. Some tasks involve new capabilities, while others involve adjustments to existing functions, fixes, refinements, or changes required by the wider product environment.
For Accedo, the issue was not a lack of direction. The team already managed the MAXstream program and understood its priorities. The constraint was delivery capacity: the amount of work required had grown beyond what the existing team could comfortably absorb.
2. Multi-device support increased the work surface
MAXstream served users across Android, iOS, desktop, and Android TV. Each platform has different technical conditions, interface expectations, and testing requirements.
A change that appears simple on one platform may require additional work elsewhere. A feature must be implemented consistently, but it may not be implemented identically.
This increased the need for developers who could work within an established product environment and understand how changes affected the wider application ecosystem.
3. The additional team had to integrate quickly
Adding external developers can create as much coordination work as it removes if the team does not integrate well.
New developers need to understand the codebase, development standards, release process, communication patterns, and current priorities. If they work through a separate structure, Accedo’s existing team may spend too much time transferring context and reviewing disconnected work.
The resource model therefore needed to focus on integration. Suitmedia’s developers had to become part of Accedo’s working rhythm rather than operate as a parallel vendor team.
4. Accedo needed delivery support without losing control
Accedo remained responsible for managing the MAXstream project. The additional developers would work directly under Accedo’s Project Manager.
This arrangement was important because it preserved a single line of prioritization and accountability. Accedo could decide what needed to be done, how work should be sequenced, and how delivery should be evaluated.
Suitmedia’s role was to provide capable development capacity within that structure. The model avoided creating competing management layers or forcing Accedo to redesign its operating model.
5. The transition to local partners required a staged approach
Telkomsel had directed a gradual move from international to local vendors. This created a longer-term organizational goal, but the immediate need remained practical: MAXstream required support now.
A staged partnership reduced transition risk. Accedo could begin with a defined number of resources, assess how the collaboration worked, and expand responsibility over time if the model proved effective.
This approach created room to build trust through delivery rather than making a large commitment before the teams had worked together.
6. The service needed reliable continuity
MAXstream was an active product, not a one-time project. Development support had to contribute to continuity across daily work, enhancements, and adjustments.
If additional resources changed too frequently or lacked sufficient context, Accedo could face repeated onboarding costs and inconsistent delivery.
The managed service therefore had to provide stable, dedicated capacity. Consistency would allow the developers to build product knowledge and become more productive over time.
7. Workload pressure could affect delivery quality
When a product team carries too many tasks at once, several problems can follow. Priorities may compete, testing may be compressed, technical debt may grow, and small improvements may be delayed because urgent work consumes the available capacity.
Additional developers could help distribute that workload. But capacity only creates value when it is integrated into a clear process and directed toward meaningful work.
Suitmedia’s solution needed to give Accedo more hands without creating more coordination burden.
8. Technical support had to fit an existing quality standard
MAXstream users expected a consistent experience across devices. New developers therefore needed to work within established technical and product standards.
They had to contribute without weakening code quality, release discipline, or platform consistency. This required more than general mobile development experience; it required the ability to adapt to another team’s environment.
The project depended on practical compatibility between people, processes, and technology.
Embedding dedicated developers inside Accedo’s delivery model
1. Start with the client’s operating model
Suitmedia first understood Accedo’s need for additional mobile application development support and the way the MAXstream project was managed.
The central requirement was clear: the developers would work directly under Accedo’s Project Manager and follow the existing project structure.
This meant the solution was not a separate outsourced project with its own scope and management. It was a capacity extension designed to operate inside Accedo’s established team.
2. Provide dedicated developer resources
Suitmedia deployed developers to support the MAXstream program.
Dedicated resources were important because they allowed the team to build familiarity with the product and its development environment. They were not shared across unrelated projects in a way that would constantly interrupt their focus.
The structure also gave Accedo a practical starting scale. It was large enough to add meaningful capacity but controlled enough to onboard and manage effectively.
3. Align roles with Accedo’s priorities
The developers worked under Accedo’s Project Manager, who remained responsible for assigning work and managing delivery.
This preserved clarity. Accedo did not need to coordinate priorities with multiple independent leads, and Suitmedia’s developers had a clear source of direction.
The model allowed the developers to focus on execution while Accedo retained control of the product roadmap and delivery decisions.
4. Integrate with the existing team rather than create a parallel team
The developers were expected to work as part of Accedo’s team.
This required practical integration into meetings, communication channels, development workflows, review processes, and release routines. The objective was to reduce the distance between the existing team and the new resources.
When external specialists operate as team members, knowledge flows more naturally. They can ask questions earlier, understand context faster, and contribute to decisions rather than receiving tasks without explanation.
5. Build knowledge of the MAXstream codebase
Effective support required the developers to understand how MAXstream was structured and how its components interacted across supported platforms.
This included learning the relevant development practices, dependencies, feature patterns, and quality expectations used by Accedo.
The onboarding phase was therefore an investment in future velocity. Time spent building context reduced repeated clarification later and helped the developers contribute more independently.
6. Support daily maintenance and enhancement work
The managed service model covered ongoing work associated with enhancing and adjusting the MAXstream application.
This could include implementing changes, supporting refinements, addressing development tasks, and helping the broader team maintain progress across the program.
The value came from flexibility. Accedo could allocate the additional capacity to the work that mattered most at a given time instead of engaging a separate team for every individual requirement.
7. Provide capacity across mobile development needs
MAXstream was available on both Android and iOS, making mobile development a central part of the support requirement.
Suitmedia’s resources contributed to the work needed to maintain and improve the application across its mobile environments, while remaining aligned with the wider multi-device product.
This helped Accedo manage mobile work as part of one coordinated program rather than treating each enhancement as an isolated task.
8. Preserve a single delivery process
The managed service arrangement allowed Accedo to retain its own planning, prioritization, review, and delivery processes.
This was a deliberate choice. Introducing additional resources should increase output without forcing the client to create a new governance model.
A single delivery process also made progress easier to monitor. Accedo could assess the contribution of the extended team within the same framework used for its existing developers.
9. Keep communication close to the work
Direct collaboration under Accedo’s Project Manager helped keep questions, decisions, and feedback close to the development activity.
This reduced the chance of misunderstandings surviving across multiple layers of communication. Developers could clarify requirements while the context was still fresh, and Accedo could respond quickly when priorities changed.
Close communication was especially important for a live product with ongoing adjustments. Small misunderstandings can otherwise create rework or delay.
10. Use the initial phase to build confidence
The first stage of the partnership was intentionally limited to developers.
This gave Accedo a way to evaluate the working relationship, the quality of contributions, the speed of onboarding, and the fit with its existing processes.
A staged approach made the transition more manageable. It provided evidence for future decisions about whether Suitmedia could assume a larger role in supporting MAXstream.
11. Align with the local-vendor transition
The engagement supported Telkomsel’s broader direction to increase the role of local vendors.
Suitmedia’s involvement gave Accedo a way to begin that transition without immediately transferring full responsibility for the MAXstream program.
The model allowed local capability to develop within an established international delivery structure. This helped protect continuity while creating a path toward greater local ownership.
12. Create a model that could expand over time
The managed service was designed as a starting point rather than a fixed endpoint.
As the teams developed trust and product knowledge, Suitmedia could potentially take on more responsibility or provide additional resources according to MAXstream’s needs.
This created flexibility for the client. Capacity could grow with the product instead of requiring a full redesign of the partnership each time demand increased.
13. Support delivery without compromising product ownership
Accedo remained the product and project owner. Suitmedia provided the development capacity required to help execute the work.
This separation clarified responsibility. Accedo retained decision-making authority, while Suitmedia focused on contributing skilled resources within the agreed framework.
The result was a partnership that added capability without blurring ownership.
More capacity helped Accedo manage MAXstream more efficiently
1. Accedo gained dedicated development support
The deployment of dedicated developers gave Accedo additional capacity for the daily development and maintenance of MAXstream.
This reduced pressure on the existing team and allowed more tasks to be addressed within the project’s operating rhythm.
The support was practical and immediate. Accedo did not need to pause the program while building a new internal team from scratch.
2. Workload became easier to distribute
The additional resources helped Accedo distribute tasks associated with application enhancements and adjustments.
This reduced the risk that a small core team would become a bottleneck for every change. Work could be assigned more deliberately according to priority, complexity, and platform requirements.
Better workload distribution also created room for more consistent review and quality practices.
3. The team could respond more effectively to ongoing needs
MAXstream required continuous support rather than occasional development bursts.
The managed service model gave Accedo access to a stable capacity base that could respond to daily requirements and changing priorities.
This improved operational velocity. The team could address work as it emerged rather than allowing a growing queue of requests to accumulate.
4. The developers integrated into Accedo’s management structure
Because the developers worked directly under Accedo’s Project Manager, the client retained clear control over priorities and delivery.
This reduced coordination friction. Tasks could be assigned, reviewed, and adjusted through the same management process used for the rest of the MAXstream team.
The arrangement also supported accountability. Accedo knew where to direct questions and how to evaluate progress.
5. The project reduced the burden on the existing team
The additional developers helped relieve the workload associated with improving the MAXstream application.
This allowed Accedo’s existing team to focus more effectively on planning, architecture, prioritization, review, and other responsibilities that required broader product context.
The benefit was not simply more output. It was a better allocation of the team’s attention.
6. MAXstream gained a more sustainable support model
A managed service model provided a repeatable way to add capacity as the product’s needs changed.
Accedo could use dedicated resources without taking on the full burden of recruitment, onboarding, and long-term capacity planning internally.
This created greater flexibility for a product operating across multiple platforms and serving a large user base.
7. The partnership supported the local-vendor transition
The engagement gave Accedo experience working with a local technology partner within the MAXstream program.
This created a foundation for a staged transition from international to local vendors. The process could be evaluated through real delivery rather than based only on plans or assumptions.
The result was greater confidence in the feasibility of expanding local involvement over time.
8. Product knowledge could accumulate within the team
Dedicated developers who remained involved in the project could build a stronger understanding of MAXstream’s systems and ways of working.
This reduced repeated onboarding and helped improve productivity over time. The team’s value increased as its knowledge of the product deepened.
Accumulated knowledge also supported continuity. The project became less dependent on rediscovering context for every new task.
9. The model created a foundation for broader responsibility
The initial resource deployment allowed Suitmedia to demonstrate its ability to contribute within Accedo’s delivery environment.
This created a potential path for Suitmedia to take on more of the MAXstream program gradually, aligned with Accedo’s needs and Telkomsel’s vendor transition.
The approach balanced ambition with control. Responsibility could expand as the partnership proved itself.
10. Daily application improvements became more manageable
The additional capacity supported the ongoing enhancement and adjustment of MAXstream.
This helped Accedo maintain momentum across a product that needed to evolve continuously. The team could respond to changes without allowing every request to compete for the same limited development capacity.
The broader outcome was a more manageable operating model for a live, multi-device streaming service.
11. The solution preserved delivery continuity
A new resource model can create disruption if it requires the client to stop and redesign its workflow.
Suitmedia’s managed service approach worked within Accedo’s existing project management structure. This helped the client add capacity without changing the basic way MAXstream was managed.
Continuity reduced adoption risk and allowed the team to focus on delivery.
12. The partnership improved overall process efficiency
The case study reports that Accedo experienced substantial assistance in resolving tasks and managing the workload associated with MAXstream enhancements.
This indicates that the solution addressed the underlying capacity problem rather than only adding people to a staffing list.
The resources became part of a more efficient process, helping the client move from request to implementation with less strain.
The deeper lesson: capacity is valuable when it integrates cleanly
1. Additional people do not automatically create additional speed
A larger team can increase coordination if roles, management, and communication are unclear.
The value of a managed service comes from integrating resources into a working delivery model. Clear ownership and direct management are as important as technical skill.
2. Dedicated resources build more value than fragmented availability
Developers who move between too many projects may struggle to build product context.
Dedicated resources can develop deeper knowledge, respond more quickly, and contribute with less repeated onboarding. Stability supports productivity.
3. Capacity models should preserve client control
Clients need to retain authority over priorities, standards, and product direction.
A successful managed service adds execution capacity without creating confusion about who makes decisions. The client should gain flexibility without losing ownership.
4. Staged transitions reduce organizational risk
Moving from an international vendor model to greater local participation can be strategically important, but a sudden transition may create delivery risk.
Starting with a defined team allows the organization to learn, evaluate, and expand gradually. Trust is built through evidence.
5. A service model should fit the product’s operating rhythm
A live streaming platform needs ongoing development, maintenance, and adjustment. A project-based model may not be sufficient when demand is continuous.
Managed service is valuable when it matches the way the product evolves. It provides a stable capacity layer that can respond to changing priorities.
6. Team integration protects knowledge continuity
When resources work directly with the client team, knowledge flows in both directions.
Developers understand the product more deeply, while the client gains a clearer view of progress and technical considerations. This reduces the risk of knowledge being trapped between organizations.
7. Delivery partnerships should be designed for scale
The first phase should solve the immediate capacity problem while creating a path for future expansion.
A clear structure, stable communication, and accumulated product knowledge allow responsibility to grow without forcing a new operating model each time.
8. The real outcome is improved organizational velocity
The purpose of added development resources is not to increase headcount. It is to help the organization resolve work faster, manage change more effectively, and sustain product quality.
Capacity becomes strategic when it improves the speed and reliability of the whole delivery system.
Strategic Insights for the C-Suite
- Buy capacity as an operating capability, not as a staffing transaction. External resources create value when they integrate into priorities, communication, standards, and decision-making. People alone do not solve a delivery bottleneck.
- Preserve client ownership while adding execution strength. The client should retain control of product direction and quality. A clear management structure allows an external team to increase output without creating accountability gaps.
- Use staged vendor transitions to protect continuity. Begin with a controlled team, evaluate performance in the real operating environment, and expand responsibility based on evidence. Gradual migration reduces risk.
- Favor dedicated resources for products that evolve continuously. Live platforms need stable product knowledge and ongoing support. Dedicated teams reduce repeated onboarding and help maintain delivery momentum.
- Measure managed services by organizational velocity. The key question is not how many people were added, but whether the organization resolves work faster, manages workload better, and sustains improvements with less pressure on the core team.
