You know the market, the language, the regulator and the customer. Avante brings the product, the delivery experience behind it and the second line. Together that is a BSS or MVNx project a local team can win and keep.
Reviewed by Alexander Donskoy, Sales Director, Avante · Last reviewed 2026-09
A partner is not a lead source. The partnerships that work are the ones where somebody on your side can sit in front of an operator's CTO or a bank's programme director, understand what is being asked, and still be in the room after go-live. Four shapes of company usually fit that description.
01You already deliver core, OSS or IT projects for operators in your region and know how their procurement, testing and change processes actually work. Avante gives you the BSS and MVNx layer to bid with when the tender asks for billing, charging, CRM, provisioning or partner management.
02The customer already trusts you with their systems and is starting to think about a mobile proposition, or about telecom-grade billing for something that is not mobile at all. You bring the relationship and the local delivery; we bring the platform and the operator-side experience nobody expects an IT house to have.
03You advise operators on target architecture, revenue assurance or a BSS replacement, and sooner or later the recommendation needs a product behind it. Partnering keeps you in the delivery instead of handing the project to whoever wins the software selection afterwards.
04You already carry telecom software or infrastructure and have the contracts, the invoicing and the local presence to resell them. Avante adds a BSS/OSS line that comes with implementation, localisation and support work attached, rather than a licence to move on its own.
Where we are usually not a fit: a pure lead-referral arrangement with nobody to carry the technical conversation, or a market where the first line would still have to come from us. An arrangement where Avante stays invisible to the customer is a separate discussion that depends on the market, so assume nothing and ask early. If none of this matches what you had in mind, say so in the first call: it is a much shorter conversation than a partnership neither side can deliver.
A partnership only holds if both sides can name what they are paid for. The lines below are the work itself, sorted by who does it. What each line is worth, and how licence and subscription revenue is shared, is commercial: it belongs in the partner agreement for your market, not on a public page.
On the partner's side
On the Avante side
The split is a working arrangement, not a legal fiction: it decides who the customer calls, who changes the configuration, and who fixes the product when the answer is in the code. The bands below are how we usually draw it.
You, in your market
Interface
Deal registration, joint pre-sales and one scope both sides can quote from
Avante
Interface
Shared working surface — documentation, test environment, certification and an escalation path with names on it
The customer's environment
| Stage | The partner | Avante |
|---|---|---|
| Qualification and deal registration | owns the customer relationship, registers the opportunity | confirms the fit and that the deal is not already in play |
| Pre-sales, demo and RFP | leads the conversation, in the local language | joins demos and workshops, answers product and architecture questions |
| Scope and proposal | owns the customer-facing proposal and the local scope | scopes platform, interfaces and migration; reviews the estimate |
| Contracting | owns the contract with the customer | licence or subscription terms with the partner |
| Implementation | configuration, integrations to the customer's systems, localisation, testing | solution architecture, host and network interfaces, product-side work, migration |
| Acceptance and go-live | owns acceptance with the customer | technical readiness and cutover support |
| Support after launch | first line, in local language and working hours | second line on the product: defects, escalations, patches |
| Change and growth | small changes and catalogue configuration | releases, roadmap, new modules, a change of model |
This is the shape we work to, not a contractual RACI. On any given deal the line moves: some partners run the whole implementation with us in the background, others hand over after scoping.
There is no tier list to join and no portal to sign up on. What follows is how we work with partners today: five steps from a first conversation to a first joint deal.
01
Your market, the customers you already serve, what you want to sell and how much of the delivery you want to own. We say honestly where we see a fit and where we do not.
02
Scope, roles, territory and the commercial terms are agreed for your market and written down. Everything about money belongs in this step and nowhere else.
03
Product and configuration training for your delivery team, a positioning session for the commercial one, access to the documentation and a test environment your engineers are meant to break.
04
You bring the opportunity and register it; our architects join the demo, the workshop or the RFP answer; the scope is written so both sides quote from the same document.
05
You deliver locally with our delivery core behind you, keep the first line, and pick up the change and managed-service work that comes after go-live. What you take on next widens with what you have actually delivered.
Avante publishes no partner tiers, commission schemes or certification levels, and none are invented here. The steps above describe how the work is organised; the conditions attached to them are agreed per market and confirmed in the partner agreement.
Two things to sell, on one platform. Avante BSS/OSS is the stack an operator runs its commercial business on. Avante MVNx Suite is that same stack packaged for MVNOs, MVNEs and MVNAs. Both are sold as the modules a customer's model actually needs, not as an all-or-nothing suite.
01
02
03
0421
BSS projects delivered for MNOs and MVNOs
15
live MVNOs on Avante
3
MVNE platform deployments
since 2006
BSS delivery experience
Avante project data. It is the delivery record a partner presents next to its own; the commercial terms of a partnership are agreed per market and not published.
Part of the pipeline will be mobile: a bank, a retailer or an ISP that wants its own mobile proposition, or an operator that wants to host others. That deal has a shape of its own. Somebody owns the customer and the brand, somebody owns the licence and the network, and somebody owns the platform in between. The revenue divides along those lines, not along anyone's org chart.
The customer's operating model decides where the division falls, which is why it is worth settling before the platform shortlist. A reseller on someone else's platform keeps the brand and little else. A Medium MVNO on its own BSS keeps the catalogue, the charging, the billing and the subscriber data. An enabler keeps all of that for every tenant it hosts, and sells the hosting: that side is covered on the MVNE and MVNA platform page. For a partner, this is the difference between a small resale and a delivery project with years of work behind it.
01
Owns the customer, the brand and the channel, and sells inside the catalogue scope and price envelope the platform owner allows.
02
Owns the licence, the radio and the core, and the wholesale agreement the traffic is bought under.
03
Owns the BSS: catalogue, charging, billing, tenants, commissions and settlement, and therefore the numbers the other two are paid from.
A market you already work in, customer relationships you already have, and people who can carry a technical conversation with an operator or a large enterprise. Local delivery capacity matters more than telecom billing experience: product knowledge is trainable, trust in your market is not.
No. A large part of the demand for this platform comes from banks, retailers, public bodies and ICT providers, not from operators themselves, and the integrators around them are usually IT companies, not telecom specialists. One thing is not optional: somebody on your side who owns the technical conversation and stays in it after go-live.
They are agreed per market and per deal, and this page publishes no rates, shares or tiers because there is no standard scheme to quote. Ask in the first conversation: it is the second thing we discuss, after whether there is a fit at all.
You do. Deal registration exists so that the partner who brought an opportunity is the one credited for it, and so that two routes do not arrive at the same customer with the same platform. Our architects join demos, workshops and RFP answers when you want them there.
You keep the first line, in the local language and local working hours. Second line on the product sits with Avante: defects, escalations that reach the code, patches. Where the customer buys managed operations, which side runs them is settled before the contract is signed.
Over time, a large part of it: configuration, integrations to the customer's systems, localisation and support are exactly what a local team should own. The product-side work stays with us until your team has delivered enough to take it: architecture, host and network interfaces, migration of a live base. That judgement is made per project, not by a certificate.
Then the operating model decides most of the scope: who owns the catalogue, the charging, the billing and the subscriber data, and who owns the licence and the network. Start from the operating models page, bring us in early, and expect the host agreement and the regulator to set the timeline rather than the software.
Tell us where you work, who you already sell to and how much of the delivery you want to own. If there is a fit we will say so and put the terms for your market in writing; if there is not, that is a shorter conversation.
