Telecom · Carrier-grade BSS/OSS, charging and mobile core
You win the side projects. The incumbent keeps the core.
You sell core BSS/OSS, charging, mobile core or MVNO enablement to MNOs, MVNOs and Tier 1 and Tier 2 carriers. A few large deals decide your year, and strong evaluations end in ‘not this year’. Your real window opens an estimated 12–18 months before the incumbent’s term ends.
- Typical deal
- €250k+ a year Illustrative
- Sales cycle
- 12–36 months Illustrative
- Buying panel
- 8–12 or more people Illustrative
Updated 5 October 2026 · Based on Panelhop research, October 2026
At a national operator buying core BSS or charging8–12 or more people Illustrative
The short answer
How do carrier-grade BSS and core vendors sell to mobile operators and Tier 1 carriers?
Carrier-grade BSS/OSS, charging and mobile core vendors sell to mobile operators, MVNOs and Tier 1 and Tier 2 telecom carriers through few, large deals. By Panelhop’s estimate, selections at national operators take 12–36 months, and security holds a veto under UK and German security law. Incumbents rarely lose core BSS, so renewal windows and new business lines decide the pipeline.
Carrier-grade BSS/OSS, charging and mobile core · How a deal really moves
‘Not this year’ is your biggest competitor. Security vetoes late, and a few big deals carry the year. The same deals, planned around the term end. Security in before terms; every big deal weighted by evidence.
One national operator, 8–12 or more people and an estimated 12–36 months per core selection.
What opens a deal
- Incumbent term end: Contract
- New line of business: Technology
- Acquisition completes: Consolidation
- TSA supplier clauses by 2027: Regulation · UK
- NIS2 supplier duties: Regulation · DE
Signal Desk · weekly: In-market accounts, scored and mapped
Your buyer and who decides
A national operator
MNO, converged carrier or full MVNO
38 Tier 1 and Tier 2 providers in the UK
Panel Check · coverage baselined
- CIO or head of BSS, can Veto: A multi-year programme that overruns and breaks billing.
- CTO and core architects, can Veto: Losing service while the core migrates.
- Finance, can Veto: Discretionary spend cut halfway through a programme.
- Security, TSA and legal, can Veto: Third-party access becoming the breach path.
- Group procurement, can Veto: Single-vendor dependency across the group’s countries.
- New-line product owner: Waiting on a core replacement before launch.
How the deal moves
Account planning
Renewal window Typical time: 12–18 months out
- Where it stalls
- ‘Not this year’, again
- With Panelhop: Leak Fix
- Incumbent and term end on every buying centre, with renewal-window tasks
RFP
Proof of concept Typical time: 1–3 months
Supplier assurance Typical time: 2–8 weeks
- Where it stalls
- The security veto arrives after the price
- With Panelhop: Leak Fix
- No terms until your trust pack and TSA or NIS2 mapping reach security
Negotiation Typical time: 2–6 wk + board
- Where it stalls
- The quarter rests on a few deals
- With Panelhop: Leak Fix
- Each large deal weighted by seats engaged and assurance started
Implementation
Expansion
- Where it stalls
- Expansion slides to next year
- With Panelhop: Panel Ops
- Expansion plays on acquisitions and new lines, reported monthly
Panel Ops · monthly: Scores and plays tuned against the baseline
Illustrative Source: Stages, seats, triggers and stalls from Panelhop research, October 2026; Ofcom; the services as described on the Services page. Note: Durations, panel sizes and cycle lengths are Panelhop estimates from our research, not measurements.
At a glance
| Typical deal | €250k+ a year Illustrative |
|---|---|
| Sales cycle | 12–36 months Illustrative |
| Buying panel | 8–12 or more people Illustrative |
| How deals start | An RFP, a renewal window or a new line of business; contact sales is the main web path at 4 of 4 carrier-grade vendors we analysed |
Source: Panelhop research, October 2026. Note: Values marked Illustrative are Panelhop estimates from our research, not measurements.
Carrier-grade pipelines leak at timing, security and the forecast.
Where do core BSS and mobile core deals at large operators stall?
Core BSS and mobile core deals at large telecom operators stall at renewal, in supplier assurance, in the forecast and at expansion. Lost evaluations are rarely reopened at the incumbent’s term end. Security meets the vendor last, and a few large deals hide a weak quarter.
Where the pipeline leaks: 4 points across 8 stages.
BSS evaluations end in ‘not this year’ and never return
- What you see
- Wins stay limited to MVNO, IoT or side projects, and core deals go quiet.
- Why it happens
- We flag incumbent lock-in as a likely risk at all 4 carrier-grade vendors we analysed, and none shows a way to track term ends or end-of-support windows per buying centre.
Stage Renewal window
Security meets you after the commercial terms
- What you see
- The deal sits in supplier assurance for weeks after the price is agreed.
- Why it happens
- Security and legal are not mapped at discovery, and none of the 20 vendors we analysed maps its content to TSA supplier measures or NIS2 duties.
Stage Supplier assurance
A strong pipeline still misses the quarter
- What you see
- Pipeline looks strong at board meetings while revenue misses on deal timing.
- Why it happens
- A few large deals carry the year, and stage criteria do not weight them by evidence such as seats engaged or supplier assurance started.
Stage Negotiation
Upgrades slide to next year, and the forecast misses
- What you see
- Upgrades slide to the next financial year and the expansion forecast misses.
- Why it happens
- No account plan ties expansion to the operator’s own triggers, such as an acquisition or a new product line.
Stage Expansion
Term ends and new lines open core deals.
What opens a core BSS or mobile core deal at a large operator?
Large operators open core BSS and mobile core deals when an incumbent’s term nears its end, a new line of business launches, an acquisition completes or a security rule changes supplier contracts.
The 5 events that open or close the window for a deal.
Contract
Incumbent term end
- What happens
- A core BSS, charging or OSS contract approaches its term, and the operator decides to renew, extend or re-tender.
- Where to spot it
- Signing announcements plus the known term, and operators’ annual reports.
- Window
- Engage 12–18 months before term end, by our estimate.
Technology
New line of business
- What happens
- An operator launches an MVNO, a second brand or an IoT service and buys outside its core stack.
- Where to spot it
- Operator announcements, trade press and published launch dates.
- Window
- Short: MVNO and digital-brand projects run to a launch date within 1–6 months, by our estimate.
Consolidation
Acquisition completes
- What happens
- An operator completes an acquisition, and one platform has to onboard the acquired subscriber base.
- Where to spot it
- Competition authority decisions and completion announcements.
- Window
- From completion through integration; expansion orders follow the platform choice.
Regulation
UK TSA supplier deadline
- What happens
- The Telecoms Security Code of Practice expects Tier 1 and Tier 2 providers to have supplier measures in all contracts by 31 March 2027.
- Where to spot it
- The Code of Practice, Ofcom’s security reports and operators’ supplier security standards.
- Window
- Every renewal and new purchase until the deadline, and every contract after it.
Regulation
German NIS2 supplier duties
- What happens
- Since 6 December 2025, operators in scope must secure their supply chain, including direct suppliers, and management must approve the measures.
- Where to spot it
- BSI guidance and supplier questionnaires from German operators.
- Window
- New tenders and renewals, where supplier assessments arrive with the RFP.
Security, procurement and finance each hold a veto.
Who signs off on a core BSS or mobile core deal at a large telecom operator?
At a large telecom operator, a steering committee signs off on core BSS and mobile core deals, and security, procurement, finance and legal each hold a veto. The CIO or head of BSS runs BSS and charging selections; the CTO and core network architects lead mobile core deals. A product owner for a new line often sponsors the first project.
At a national operator buying core BSS or charging, 8–12 or more people sit on the panel and 6 seats can stop the deal.
At a national operator buying core BSS or charging: 8–12 or more people
CIO or head of BSS
Can Veto
CIO · Head of BSS/OSS
- Cares about
- Open architecture, a clear roadmap and clean data migration.
- Worries about
- A multi-year programme that overruns and breaks billing.
CTO and core network architects
Can Veto
CTO · VP Engineering
- Cares about
- Standards conformance and carrier-grade reliability.
- Worries about
- Losing service while the core migrates.
Product owner for a new line
MVNO business owner · Head of Wholesale
- Cares about
- Speed to launch a new brand, MVNO or IoT service.
- Worries about
- Waiting on a core replacement before launch.
Security and TSA compliance
Can Veto
CISO · TSA compliance lead · ISMS lead
- Cares about
- Supplier measures, secure third-party access and exit plans.
- Worries about
- Third-party access becoming the breach path.
Group procurement
Can Veto
Head of Procurement · Procurement Manager
- Cares about
- A scored, defensible selection and the supplier’s financial standing.
- Worries about
- Single-vendor dependency across the group’s countries.
Finance
Can Veto
CFO · Finance Director
- Cares about
- Total cost of ownership across a multi-year term.
- Worries about
- Discretionary spend cut halfway through a programme.
Legal and data protection
Can Veto
General Counsel · DPO · Contracts Manager
- Cares about
- Audit rights, exit plans and transition clauses.
- Worries about
- Offshore access to UK network data.
You sell the systems a national operator cannot let fail.
What do carrier-grade vendors sell, and to which operators?
Carrier-grade vendors sell core BSS/OSS, charging, mobile core and MVNO enablement to large operators. In the UK alone, 38 Tier 1 and Tier 2 providers are expected to follow the Telecoms Security Code of Practice.
What vendors of this type sell
- Core BSS/OSS and billing
- Real-time charging and policy
- Mobile core and network functions
- MVNO and MVNE enablement platforms
Which operators buy it
- National and regional MNOs
- Incumbents and converged Tier 1 and Tier 2 operators
- Full MVNOs and MVNEs
- Wholesale-only fibre platforms
- Pan-European groups that buy centrally
Core BSS deals move on the incumbent’s contract term.
How does a core BSS or mobile core deal move at a large telecom operator?
A core BSS or mobile core deal at a large telecom operator moves from account planning and the incumbent’s renewal window through an RFP, a proof of concept and supplier assurance to a long, phased implementation. Durations are Panelhop estimates of the operator’s side.
Stage by stage: what you do, what the operator does, and what changes at the 4 stages where deals stall.
| Stage | What you do | What the operator does | Today | With Panelhop |
|---|---|---|---|---|
| Account planning | Maps buying centres by group and country, with each incumbent and its term. | Sets a multi-year roadmap; group buying can cover several countries. | Buying centres are listed, but their seats are not mapped. | A Panel Check measures how many buying centres you cover and baselines engagement per account before anything changes. Panel Check GTM audit · 2–3 weeks |
| Renewal window Typical time: 12–18 months before term end | Engages the full panel before the incumbent’s term ends. | Decides whether to renew, extend or re-tender. | The incumbent’s term end is found by chance. Stalls: ‘Not this year’, again. Operators fear changing systems that carry live revenue and use new vendors mainly for new lines of business, so core displacement rarely happens at the first attempt. | Leak Fix adds the incumbent and its term end as required fields on every buying centre, with renewal-window tasks and the full panel mapped. Leak Fix We build the fixes |
| RFP | Answers an RFI and RFP across BSS, charging or core scope. | Group procurement runs a formal, scored selection. | The RFP team meets IT and procurement only. | A role map per buying centre seeks security, procurement, finance and legal before the RFP closes, with coverage tracked. Leak Fix We build the fixes |
| Proof of concept Typical time: 1–3 months | Supports the operator’s proof of concept or TM Forum Catalyst, with no structured pilot offer of its own. | IT and network teams test against a plan and agreed criteria. | No pilot offer with written success criteria. | A mutual action plan sets the success criteria, owners and dates for the proof of concept. Leak Fix We build the fixes |
| Supplier assurance Typical time: 2–8 weeks | Maps contracts and controls to TSA supplier measures and NIS2 duties. | Security, legal and procurement review the evidence, and security holds a veto. | Security questions arrive after the price is agreed. Stalls: The security veto arrives last. The Code of Practice expects UK Tier 1 and Tier 2 providers to flow supplier measures into contracts, so late evidence requests add weeks or end the bid. | Stage exit criteria require that your trust pack and TSA or NIS2 clause mapping reach the operator’s security team before commercial terms. Leak Fix We build the fixes |
| Negotiation Typical time: 2–6 weeks, then board approval | Agrees term, SLAs, audit rights and exit plans. | The steering committee and board approve a multi-year commitment. | The forecast counts deals at face value. Stalls: The quarter rests on a few deals. A handful of large deals land unevenly through the year, so an unweighted pipeline looks strong while the quarter still misses. | A deal risk score weights each large deal by evidence, such as seats engaged and supplier assurance started, and forecast accuracy is tracked against bookings. Leak Fix We build the fixes |
| Implementation | Delivers a phased migration off the incumbent’s system. | Accepts each phase; on-premises programmes take the longest. | Sales promises reach delivery by word of mouth. | A handoff document built from the deal records scope, acceptance steps and what was promised about migration. Leak Fix We build the fixes |
| Expansion | Sells new modules, countries or an acquired subscriber base. | Expands after an acquisition, or defers discretionary spend. | Expansion waits for the customer to ask. Stalls: Expansion slides to next year. Cost-cautious operators push licence expansions and upgrades into the next financial year, and a forecast that assumed installed-base growth misses. | Panel Ops keeps expansion plays on acquisition and new-line triggers running and reports progress against the baseline every month. Panel Ops We run it monthly |
Panelhop times each buying centre and weights each deal.
How does Panelhop help carrier-grade vendors sell to operators?
Panelhop helps carrier-grade vendors by baselining coverage of each buying centre with a Panel Check (GTM audit). Leak Fix (we build the fixes) puts each incumbent’s term end on the account with renewal tasks, brings security in early and weights the forecast by evidence. Panel Ops (we run it monthly) keeps expansion plays running and reports against the baseline every month, and nothing here is a promised result.
What we baseline and report
- Buying centres with engaged security, procurement and finance contacts, against the baseline
- Forecast accuracy against actual bookings, quarter by quarter
- Days each deal spends in supplier assurance, against the baseline
Other vendor types in telecom.
What other vendors sell to operators?
The same operators buy from these vendor types too, through different panels and pipelines.
- Vendor type
BSS/OSS for independent operators
Billing, provisioning, field service and integration platforms for rural telcos, co-operatives, municipal networks, WISPs and altnets.
Read the pipeline - Vendor type
Broadband funding and compliance software
BEAD grant reporting, FCC BDC filing and broadband location-data tools sold to US subgrantees, rural telcos, co-operatives and WISPs.
Read the pipeline - Vendor type
Network planning, fibre design and GIS documentation
FTTH and radio network planning, design automation and GIS network documentation sold to fibre builders, rural telcos, altnets and MNOs.
Read the pipeline - Vendor type
Assurance, customer data and fraud intelligence
Service assurance, telco customer data platforms and fraud detection sold to mobile, converged and fibre operators on top of their BSS/OSS.
Read the pipeline
The words your buyers use, defined.
What do terms like “Full MVNO” and “MVNE” mean?
Plain definitions of the terms that come up when you sell carrier-grade BSS/OSS, charging and mobile core to operators.
- Full MVNO
- A mobile virtual network operator that runs its own core and BSS while renting radio access from a host mobile network.
- MVNE
- A mobile virtual network enabler: a company that hosts the core, BSS and operations for many MVNOs, and can act as a channel to them.
- Tier 1 and Tier 2 providers (UK)
- In the UK Telecoms Security Code of Practice, the public telecoms providers ranked largest by relevant turnover. Both tiers are expected to follow the Code’s measures, including its supplier security measures.
- TM Forum Catalyst
- An industry proof-of-concept project in which operators, suppliers and integrators test a product together inside TM Forum’s programme.
- Charging system
- The real-time system that rates and charges usage for mobile and converged services. Operators replace charging systems rarely, on long investment cycles.
- Trust pack
- A vendor’s ready set of security and compliance evidence, such as SOC 2 or ISO 27001 reports, policies, questionnaire answers and the DPA, shared with an operator’s security team.
Answers before your next operator deal.
What do vendors of carrier-grade BSS/OSS, charging and mobile core ask about selling to operators?
How long does it take to sell BSS to a Tier 1 operator?
By Panelhop’s estimate, selling core BSS or OSS to a Tier 1 or national telecom operator typically takes 12–36 months, with about 18 months most common. Operators run formal multi-year selections with proofs of concept, UK Telecoms Security Act or NIS2 supplier assurance and group steering committees. MVNOs buy faster, often in an estimated 1–6 months. Both ranges are inferred from how operators buy.
How do challengers displace an incumbent BSS vendor at a telecom operator?
Challengers rarely displace an incumbent BSS at a telecom operator in one step. Operators fear moving live revenue systems and use new vendors mainly for new lines of business, such as an MVNO, a second brand or IoT. Win the new line first and record the incumbent’s term end. By our estimate, engage the full buying panel 12–18 months before that term ends.
How do MVNOs buy BSS and core platforms?
MVNOs and digital mobile brands buy BSS and core platforms quickly, often in 1–6 months by our estimate, because a launch date sets the project’s deadline. Their teams are small and cloud-first, and they skip on-premises BSS/OSS. Enablers that host many MVNOs can act as a channel to them. Telecom vendors selling to MVNOs win on speed to launch and comparable references.
How does the UK Telecoms Security Act affect vendors selling to Tier 1 and Tier 2 providers?
The UK Telecoms Security Act puts vendors selling to Tier 1 and Tier 2 telecom providers inside the operator’s security duties. Under the Code of Practice, providers should flow supplier measures into contracts, keep exit plans and have the measures in all contracts by 31 March 2027. Almost a quarter of the Code of Practice measures concern the supply chain. Vendors should map their controls and contracts before the security team asks.
How should carrier-grade vendors forecast lumpy telecom deals?
Carrier-grade vendors selling to telecom operators should weight each large deal by evidence, not by stage name. Record which seats are engaged, whether supplier assurance has started and when the steering committee meets, then compare the forecast with actual bookings every quarter. A few large deals carry the year, so an unweighted pipeline can look strong while the quarter misses.
Who signs off on a BSS or core network deal at a Tier 1 operator?
At a Tier 1 or national telecom operator, a steering committee signs a core BSS deal after the CIO or head of BSS runs the selection. The CTO and core network architects lead mobile core deals and can stop them. Security, group procurement, finance and legal each hold a veto, and UK Telecoms Security Act or German NIS2 duties give security a formal say. Product owners for new lines, such as an MVNO, often sponsor the first project, and by our estimate the panel has 8–12 or more people.
Where the numbers come from.
Sources
Sourced figures link to their source below. Figures marked Illustrative, and figures given as estimates, are inferred from Panelhop research. Vendors appear only as types, never by name.
- Ofcom’s Telecoms Security report 2024–2025 (2025)
- Department for Digital, Culture, Media and Sport and Department for Science, Innovation and Technology, Telecommunications Security Code of Practice 2026 (version 1.1) (2026)
- Bundesamt für Sicherheit in der Informationstechnik (BSI), Fragen und Antworten zu NIS-2 (2026)
- Panelhop research, October 2026: our analysis of the vendors, buying panels, pipelines and triggers for carrier-grade BSS/OSS, charging and mobile core in telecom, from public sources. Vendor names are not published.
