Insights

10

5

min read

In-house vs. Third-party Digital Mobile Operator Development

What CEOs Need to Know

Outline

Picture this:

As a telco CEO, your task is transforming your company into a tech-centric, customer-first company. Your telco has many markets worldwide, and you don’t have enough time to bring new digital experiences to your customers. 

One way of quickly introducing new digital products and digital telco experiences is through Digital Mobile Operator (DMO) brands. 

DMOs have the added benefit of letting telcos experiment with different target audiences and experiences before sharing the learnings with the rest of the company. With telcos under pressure to move beyond traditional services and into digital-first business models, this decision has long-term financial and operational implications.

Now the question becomes: to Build or to Partner?

The main challenges of producing DMO capabilities are time and expertise. Depending on your telco’s current set of challenges, there are times when it makes sense to build and times when it makes sense to collaborate with a partner.

Challenges and Considerations When Building a Digital Mobile Operator (DMO) Brand

Telcos of different sizes, locations, and technological maturity have their own challenges. When it comes to considering building in-house capabilities or partnering, these are the most common challenges:

Technical Debt of Existing Software
Some traditional telcos have strong network capabilities but may lack the software infrastructure to offer flexible mobile plans and add-ons.
One approach to upgrading existing software involves layering and integrating new software on top existing legacy software, which can become messy and expensive to maintain. Another approach is to build new software from scratch, but that could mean investing in build and technical training that will take time to bear fruit while continuing to pay for existing solutions.
Talent and Organisation
Launching a new DMO brand using new software, a new paradigm, and new teams could require an organisational shake up. Expertise may be tied up in other parts of the business or need to be trained from scratch.
Time
The time needed to launch the venture depends more on your telco’s existing infrastructure and expertise. Building internal capabilities might not be the right choice when developing a new DMO.
Control: Branding and Experience
Targeting a new niche market requires a new brand. Bringing in experienced third parties more familiar with this niche could go a long way in building a brand that resonates with them.
Financial Management
Managing DMO brand costs isn’t straightforward. Building your own capabilities requires upfront capital expenditure but pays off with long-term operational cost savings. Collaborating with a third party reduces the upfront investment, but depending on the arrangement, you may need to share revenue with them.
Agility and Flexibility
While your telco is building up its capabilities, it could take longer to adjust to market changes than working with an experienced and specialised telco partner.
Technical Debt of Existing Software
Some traditional telcos have strong network capabilities but may lack the software infrastructure to offer flexible mobile plans and add-ons.
One approach to upgrading existing software involves layering and integrating new software on top existing legacy software, which can become messy and expensive to maintain. Another approach is to build new software from scratch, but that could mean investing in build and technical training that will take time to bear fruit while continuing to pay for existing solutions.
Talent and Organisation
Launching a new DMO brand using new software, a new paradigm, and new teams could require an organisational shake up. Expertise may be tied up in other parts of the business or need to be trained from scratch.
Time
The time needed to launch the venture depends more on your telco’s existing infrastructure and expertise. Building internal capabilities might not be the right choice when developing a new DMO.
Control: Branding and Experience
Targeting a new niche market requires a new brand. Bringing in experienced third parties more familiar with this niche could go a long way in building a brand that resonates with them.
Control: Branding and Experience
Targeting a new niche market requires a new brand. Bringing in experienced third parties more familiar with this niche could go a long way in building a brand that resonates with them.
Agility and Flexibility
While your telco is building up its capabilities, it could take longer to adjust to market changes than working with an experienced and specialised telco partner.

The Pros and Cons of In-house vs. Third-party Digital Mobile Operator Development

With the most common challenges covered, let’s summarize the pros and cons of building in-house or working with a third party to produce a DMO brand.

You can check out an overview of these comparisons in the graphic below:

Building Digital Mobile Operator brands: In-house vs partnerships - In-house gives you Control and Ownership. External Partnerships gives you speed and cost sharing

The Case for In-house DMO Development

In-house development offers more control, brand continuity, lower risks, ownership, and long-term potential cost savings but comes with high upfront costs, longer timelines, and talent challenges.

Pros of In-house DMO Development

Complete Ownership and Control
By developing capabilities, talent, and software for your DMO in-house, your telco will fully own every aspect of the DMO, from the brand, messaging, and customer experience. All intellectual property (IP) around technology, product offerings, and innovations developed stays within the company.
Your telco will also have full control over the data, minimizing the risk of third-party data breaches and helping you maintain compliance with increasingly stringent privacy regulations.
Growing Internal Capabilities
While the learning curve is steep, building in-house capabilities gives you access to talent, operations, and software fully in-house. This includes critical areas such as digital service delivery, automation, cloud architecture, and customer data management. All of this is valuable for future initiatives and for reducing reliance on third parties.
Long-term Cost Efficiency
While initial capital expenditure for building DMO capabilities in-house is high, the operational costs tend to be lower in the long run as there are no third-party fees to pay and also no revenue sharing required.

Cons of In-house DMO Development

Time-Intensive
Building a DMO and its required capabilities from scratch requires substantial time, resources and coordination, often taking multiple years to implement and go to market.
High Upfront CAPEX with Ongoing Operational Costs
Building a full-stack digital platform, implementing new technologies, and upskilling staff require large upfront capital investments, which can strain financial resources.
During this time, your telco will also pay for ongoing operational expenses for existing processes and systems, including software maintenance, infrastructure upgrades, and cybersecurity.
Limited speed and agility 
An in-house solution could lack the agility to respond quickly to market shifts, new trends, or competitor actions, as legacy systems and internal hierarchies could hinder rapid decision-making and implementation.
Traditional telcos may lack internal expertise in digital-native areas like data analytics, AI, user experience (UX) design, or cloud architecture, leading to a steep learning curve or recruitment delays.

The Case for Partnering with an Experienced DMO Joint Venture (JV) Partner

Partnering with a JV enables faster market entry, reduced financial risk, and access to cutting-edge digital solutions, but at the cost of reduced control, revenue sharing, data security sharing, and potential dependency on the partner.

Pros of Collaborating on a DMO with a Third-party

Faster Time to Market
When chosen well, a good JV partner’s expertise and technology stack can help you set up a DMO quickly without limitations from legacy infrastructure.
Sometimes, your partner’s ready-made, full-stack digital solution can help you launch a DMO brand within 16 weeks, like how we launched povo with KDDI in Japan.
Lower Upfront CAPEX and Shared OPEX
Leveraging your partner’s software and expertise can significantly reduce initial setup costs.
Depending on your arrangement, many operational expenses, including IT infrastructure and maintenance, may be shared with the partner, spreading risk and reducing ongoing costs.
Access to Proven Expertise and Playbooks
Partners can complement your expertise through their knowledge of your DMO’s chosen target audience and how best to serve them. This includes digital transformation, cloud architecture, customer experience, and customer data analytics.
Shared Risks, Including Branding
In addition to sharing costs, your partner’s expertise in serving your target audience can help mitigate the risk of building a new brand to serve a target audience you are not familiar with.

Cons of Collaborating on a DMO with a Third-party

Reduced Control Over Decisions
Telcos may need to give up some decision-making power, particularly regarding product features, customer experience design, and operational processes, which could create friction.
Branding Limitations
Your DMO brand may need to be distinct from the parent telco’s core brand, and the partner’s branding approach may not align fully with the telco's vision or corporate identity.
Revenue Sharing and Dependence on the Partner
Revenue generated by the DMO is typically shared between the telco and the JV partner, reducing the overall financial gains compared to an in-house model.
Your telco must also rely on the partner to maintain high service standards, innovate rapidly, and keep pace with market demands. If the partner fails to meet these expectations, it could damage the telco’s reputation and financial performance.
Data Sharing
Telcos must share customer data with their JV partner, raising concerns about data security and privacy. This could become a compliance risk in regions with strict data protection laws (e.g., GDPR in Europe).

To Summarize:

In-house development works well if you want to have full control over all aspects of your DMO and its associated capabilities. You will not need to rely on third parties and will also keep all the software, expertise, and processes that will pay dividends down the road. However, it requires high upfront capital expenditure and can take years to achieve success.

Collaborating on a DMO with third parties works well if you need a faster time to market and want to mitigate the risks of entering new markets, offers, and target audiences with their experience. However, you must rely on them and cede some control over the brand and process.

Ultimately, your decision will depend on your telco’s strategic priorities, finances, and the speed with which your DMO brand needs to produce results. 

If you are looking to fast-track your DMO’s results with minimal risk and proven expertise, a JV with an experienced DMO partner, like Circles, may provide a clearer path to success.

Get Your Free SaaS Demo

Heading 1

Heading 2

Heading 3

Heading 4

Heading 5
Heading 6

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.

Block quote

Ordered list

  1. Item 1
  2. Item 2
  3. Item 3

Unordered list

  • Item A
  • Item B
  • Item C

Text link

Bold text

Emphasis

Superscript

Subscript

Personalizing the Customer Experience at Every Touchpoint

 One of the most immediate and impactful uses of AI is in personalization. Telcos have long recognized that customer experience is more than just a differentiator—it’s central to loyalty and long-term success. AI enables telcos to create customer journeys that are tailored based on actual behavior and preferences.             

Complicated Billing and Bill Shock
“Why am I being charged for this?!"
Complicated Billing and Bill Shock
“Why am I being charged for this?!"
Complicated Billing and Bill Shock
Content
Complicated Billing and Bill Shock
“Why am I being charged for this?!"
The telco industry has been notorious for poor customer service - in some cases, marketing professors even point to older telco ‘bad profit’ practices as poor examples of customer relationship management. Examples like these
This lack of transparency repulses customers and frustrates those who want to switch to better deals.

Heading

Content
Complicated Billing and Bill Shock
“Why am I being charged for this?!"
Complicated Billing and Bill Shock
“Why am I being charged for this?!"
Complicated Billing and Bill Shock
“Why am I being charged for this?!"
Complicated Billing and Bill Shock
“Why am I being charged for this?!"

Learn More

Insights

What the Ideal Telco-to-Techco Could Be

Connect, Delight, Beyond
Insights

Telco Digital Transformation

Why the Clean Slate Full-Stack Approach is Mission Critical
Insights

Telco Digital Transformation

Data Migration Risks and Mitigation Strategies

Insights

15 Oct 2024

In-house vs. Third-party Digital Mobile Operator Development

What CEOs Need to Know

Insights

15 Oct 2024

In-house vs. Third-party Digital Mobile Operator Development

What CEOs Need to Know

Written by

Picture this:

As a telco CEO, your task is transforming your company into a tech-centric, customer-first company. Your telco has many markets worldwide, and you don’t have enough time to bring new digital experiences to your customers. 

One way of quickly introducing new digital products and digital telco experiences is through Digital Mobile Operator (DMO) brands. 

DMOs have the added benefit of letting telcos experiment with different target audiences and experiences before sharing the learnings with the rest of the company. With telcos under pressure to move beyond traditional services and into digital-first business models, this decision has long-term financial and operational implications.

Now the question becomes: to Build or to Partner?

The main challenges of producing DMO capabilities are time and expertise. Depending on your telco’s current set of challenges, there are times when it makes sense to build and times when it makes sense to collaborate with a partner.

Challenges and Considerations When Building a Digital Mobile Operator (DMO) Brand

Telcos of different sizes, locations, and technological maturity have their own challenges. When it comes to considering building in-house capabilities or partnering, these are the most common challenges:

Technical Debt of Existing Software
Some traditional telcos have strong network capabilities but may lack the software infrastructure to offer flexible mobile plans and add-ons.
One approach to upgrading existing software involves layering and integrating new software on top existing legacy software, which can become messy and expensive to maintain. Another approach is to build new software from scratch, but that could mean investing in build and technical training that will take time to bear fruit while continuing to pay for existing solutions.
Talent and Organisation
Launching a new DMO brand using new software, a new paradigm, and new teams could require an organisational shake up. Expertise may be tied up in other parts of the business or need to be trained from scratch.
Time
The time needed to launch the venture depends more on your telco’s existing infrastructure and expertise. Building internal capabilities might not be the right choice when developing a new DMO.
Control: Branding and Experience
Targeting a new niche market requires a new brand. Bringing in experienced third parties more familiar with this niche could go a long way in building a brand that resonates with them.
Financial Management
Managing DMO brand costs isn’t straightforward. Building your own capabilities requires upfront capital expenditure but pays off with long-term operational cost savings. Collaborating with a third party reduces the upfront investment, but depending on the arrangement, you may need to share revenue with them.
Agility and Flexibility
While your telco is building up its capabilities, it could take longer to adjust to market changes than working with an experienced and specialised telco partner.
Technical Debt of Existing Software
Some traditional telcos have strong network capabilities but may lack the software infrastructure to offer flexible mobile plans and add-ons.
One approach to upgrading existing software involves layering and integrating new software on top existing legacy software, which can become messy and expensive to maintain. Another approach is to build new software from scratch, but that could mean investing in build and technical training that will take time to bear fruit while continuing to pay for existing solutions.
Talent and Organisation
Launching a new DMO brand using new software, a new paradigm, and new teams could require an organisational shake up. Expertise may be tied up in other parts of the business or need to be trained from scratch.
Time
The time needed to launch the venture depends more on your telco’s existing infrastructure and expertise. Building internal capabilities might not be the right choice when developing a new DMO.
Control: Branding and Experience
Targeting a new niche market requires a new brand. Bringing in experienced third parties more familiar with this niche could go a long way in building a brand that resonates with them.
Control: Branding and Experience
Targeting a new niche market requires a new brand. Bringing in experienced third parties more familiar with this niche could go a long way in building a brand that resonates with them.
Agility and Flexibility
While your telco is building up its capabilities, it could take longer to adjust to market changes than working with an experienced and specialised telco partner.

The Pros and Cons of In-house vs. Third-party Digital Mobile Operator Development

With the most common challenges covered, let’s summarize the pros and cons of building in-house or working with a third party to produce a DMO brand.

You can check out an overview of these comparisons in the graphic below:

Building Digital Mobile Operator brands: In-house vs partnerships - In-house gives you Control and Ownership. External Partnerships gives you speed and cost sharing

The Case for In-house DMO Development

In-house development offers more control, brand continuity, lower risks, ownership, and long-term potential cost savings but comes with high upfront costs, longer timelines, and talent challenges.

Pros of In-house DMO Development

Complete Ownership and Control
By developing capabilities, talent, and software for your DMO in-house, your telco will fully own every aspect of the DMO, from the brand, messaging, and customer experience. All intellectual property (IP) around technology, product offerings, and innovations developed stays within the company.
Your telco will also have full control over the data, minimizing the risk of third-party data breaches and helping you maintain compliance with increasingly stringent privacy regulations.
Growing Internal Capabilities
While the learning curve is steep, building in-house capabilities gives you access to talent, operations, and software fully in-house. This includes critical areas such as digital service delivery, automation, cloud architecture, and customer data management. All of this is valuable for future initiatives and for reducing reliance on third parties.
Long-term Cost Efficiency
While initial capital expenditure for building DMO capabilities in-house is high, the operational costs tend to be lower in the long run as there are no third-party fees to pay and also no revenue sharing required.

Cons of In-house DMO Development

Time-Intensive
Building a DMO and its required capabilities from scratch requires substantial time, resources and coordination, often taking multiple years to implement and go to market.
High Upfront CAPEX with Ongoing Operational Costs
Building a full-stack digital platform, implementing new technologies, and upskilling staff require large upfront capital investments, which can strain financial resources.
During this time, your telco will also pay for ongoing operational expenses for existing processes and systems, including software maintenance, infrastructure upgrades, and cybersecurity.
Limited speed and agility 
An in-house solution could lack the agility to respond quickly to market shifts, new trends, or competitor actions, as legacy systems and internal hierarchies could hinder rapid decision-making and implementation.
Traditional telcos may lack internal expertise in digital-native areas like data analytics, AI, user experience (UX) design, or cloud architecture, leading to a steep learning curve or recruitment delays.

The Case for Partnering with an Experienced DMO Joint Venture (JV) Partner

Partnering with a JV enables faster market entry, reduced financial risk, and access to cutting-edge digital solutions, but at the cost of reduced control, revenue sharing, data security sharing, and potential dependency on the partner.

Pros of Collaborating on a DMO with a Third-party

Faster Time to Market
When chosen well, a good JV partner’s expertise and technology stack can help you set up a DMO quickly without limitations from legacy infrastructure.
Sometimes, your partner’s ready-made, full-stack digital solution can help you launch a DMO brand within 16 weeks, like how we launched povo with KDDI in Japan.
Lower Upfront CAPEX and Shared OPEX
Leveraging your partner’s software and expertise can significantly reduce initial setup costs.
Depending on your arrangement, many operational expenses, including IT infrastructure and maintenance, may be shared with the partner, spreading risk and reducing ongoing costs.
Access to Proven Expertise and Playbooks
Partners can complement your expertise through their knowledge of your DMO’s chosen target audience and how best to serve them. This includes digital transformation, cloud architecture, customer experience, and customer data analytics.
Shared Risks, Including Branding
In addition to sharing costs, your partner’s expertise in serving your target audience can help mitigate the risk of building a new brand to serve a target audience you are not familiar with.

Cons of Collaborating on a DMO with a Third-party

Reduced Control Over Decisions
Telcos may need to give up some decision-making power, particularly regarding product features, customer experience design, and operational processes, which could create friction.
Branding Limitations
Your DMO brand may need to be distinct from the parent telco’s core brand, and the partner’s branding approach may not align fully with the telco's vision or corporate identity.
Revenue Sharing and Dependence on the Partner
Revenue generated by the DMO is typically shared between the telco and the JV partner, reducing the overall financial gains compared to an in-house model.
Your telco must also rely on the partner to maintain high service standards, innovate rapidly, and keep pace with market demands. If the partner fails to meet these expectations, it could damage the telco’s reputation and financial performance.
Data Sharing
Telcos must share customer data with their JV partner, raising concerns about data security and privacy. This could become a compliance risk in regions with strict data protection laws (e.g., GDPR in Europe).

To Summarize:

In-house development works well if you want to have full control over all aspects of your DMO and its associated capabilities. You will not need to rely on third parties and will also keep all the software, expertise, and processes that will pay dividends down the road. However, it requires high upfront capital expenditure and can take years to achieve success.

Collaborating on a DMO with third parties works well if you need a faster time to market and want to mitigate the risks of entering new markets, offers, and target audiences with their experience. However, you must rely on them and cede some control over the brand and process.

Ultimately, your decision will depend on your telco’s strategic priorities, finances, and the speed with which your DMO brand needs to produce results. 

If you are looking to fast-track your DMO’s results with minimal risk and proven expertise, a JV with an experienced DMO partner, like Circles, may provide a clearer path to success.

Learn More

Insights

What the Ideal Telco-to-Techco Could Be

Connect, Delight, Beyond
Insights

Telco Digital Transformation

Why the Clean Slate Full-Stack Approach is Mission Critical
Insights

Telco Digital Transformation

Data Migration Risks and Mitigation Strategies