Configuration, not integration: how VMS puts a product live on every operator
Why launching a new subscription product on 40+ operators no longer means a new technical project for each one, and what VMS does instead.
For most of the history of value-added services, launching a product with a mobile operator meant a project. A new integration with the operator’s billing platform, a new subscription flow to certify, new reporting to reconcile. Multiply that by every operator in every market and a good product could take months to reach the people who would pay for it.
We built VMS, our Value-added services Management System, to remove that bottleneck for our own apps. It is now the same system partners use.
The problem with one integration per product
Every operator connection has its own rules: how a user subscribes, how consent is captured, how charges and renewals are reported, which price points are allowed. When each product carries its own integration, every one of those rules is rebuilt and retested product by product.
That has three costs:
- Time to market. The product waits for the integration, not the other way round.
- Fragile operations. Each integration is another thing to monitor and maintain.
- Uneven data. Revenue and subscriber numbers arrive in different shapes from different places.
What changes with VMS
VMS is already connected with every operator we bill through, more than 40 of them in over 25 countries. The connection belongs to the platform, not to a product. So adding a new product is configuration:
- Configure the product, its plans and its price points.
- Choose the operators and markets to switch on.
- Go live on the existing billing connections.
There is no new technical integration. The subscription flows, consent capture and billing behaviour that already run in each market apply to the new product from the first day.
The connection belongs to the platform, not to the product.
Running the business after launch
Going live is the start. The same system runs the service day to day:
| Area | What VMS covers |
|---|---|
| Revenue intelligence | ARPU analytics and prediction, subscriber and transaction analysis, multi-dimensional reports, monitoring and alerts |
| Growth | Campaigns and traffic sources, landing pages and templates |
| Operations | User and employee management, content management, complaints and support automation |
| Partners | Documented APIs for third-party integration |
Because every product reports through one platform, an ARPU figure or a renewal curve means the same thing across operators and markets. That is what lets us compare, forecast and act quickly.
Who it is for
We built VMS for our own portfolio, and every flow is proven in market on our own products before a partner uses it. Today it is available to operators and aggregators who want new services on their network, to content owners who want reach without integration work, and as a white-label service under a partner’s brand.
If you want to see what going live would look like in your market, talk to us.
