Fintech business concept for a telecom operator: from idea to prioritized roadmap
A regional telecom operator considered launching a fintech direction — own wallet, credit products, embedded finance for the subscriber base. The concept was developed over 3 months — segment selection, product portfolio, partner strategy with a bank, regulatory constraints, phased roadmap.
Real case of developing a fintech direction concept for a regional telecom operator. Embedded finance strategy through bank partnership, regulatory plan, phased roadmap.
Typical Problem
A regional telecom operator saw ARPU growth slowdown and looked for new revenue sources. One discussed option — fintech: own wallet, embedded credit for subscribers, partnership with a bank in payments. Inside the company there were different positions: some considered it a natural evolution, others — risky entry into a foreign regulated sector. The board requested an independent concept with realistic opportunity and risk assessment.
Why This Happens
Initial internal discussions had two systemic weaknesses. First — vague segment: fintech in general, without answer to 'which client, which task, which product'. Second — underestimation of regulatory perimeter: assumption that you could start with a wallet and gradually add credit, without understanding each step requires a separate license or bank partnership. In parallel — overestimation of existing stack readiness (BSS, CRM) for fintech load. Without a concept with realistic assessment, the project could start with the wrong scale and wrong first product.
How We Diagnose It
I worked as strategic advisor on the fintech concept. Conducted a series of interviews with operator leadership (CEO, CMO, CFO, legal block), with potential partner banks, with regulatory experts. Reviewed actual subscriber base picture: which segments, which solvent, with what readiness for financial products. In parallel — analysis of international cases (M-Pesa in Kenya, GCash in Philippines, Beeline wallet in Russia) understanding what is portable to local specifics and what is not.
The Right Model
Strategy — embedded finance as partnership with a bank, not standalone fintech. The operator provides subscriber identification, consents, communication channel. The bank — licensed product parts (account, card, credit, deposit). Target segment for phase one — active subscriber base with confirmed income (about 30% of base), products — wallet and small-amount embedded credit for existing subscribers. Phase 2 — product portfolio expansion (insurance, investments). Phase 3 — entry into adjacent segments (SME, corporate).
How We Implement It
Concept developed over 3 months with operator team, partner bank, and regulatory consultants. Document includes: market assessment, product strategy, operating model, regulatory plan, technology architecture, 3-year financial model, phased roadmap, risks and mitigations. Board approved the concept and gave mandate to launch the program. First operational steps — product team formation, negotiations with the bank on partnership form, regulatory document preparation.
How the Team Works
I worked as lead advisor on the concept. The operator team provided data, conducted internal alignment, did operational hypothesis verification. The partner bank and regulatory consultants participated in specific sections. My role ended after concept approval by the board and formation of the operational launch team. Further operational implementation went without me.
Results
Fintech for a telecom operator is not 'let us launch a wallet' but a serious strategic discussion about the company's position in the financial ecosystem. Standalone path with license requires significantly larger investments than partnership with a bank. For most regional operators, the right choice is embedded finance as partnership.
Key Lessons
- • Embedded finance as partnership with a bank is usually the right strategy for an operator
- • Standalone fintech with own license is a separate strategic discussion at different investment scale
- • Regulatory work is a critical concept part, not an addition
- • Operator BSS/CRM usually not ready for fintech load, Subscriber 360 layer needed
- • Subscriber consents to fintech program — separate legal work
- • International cases (M-Pesa, GCash) portable only partially, local specifics critical
Similar challenge?
Tell me what's going on. I'll review the situation and suggest a concrete path forward.
Usually respond within a few hours