Quick answer: An OTT or IPTV platform RFP works best when it starts from the revenue model and the operating plan, then asks vendors to prove four things: how fast they can change what you sell, whether SVOD, AVOD and TVOD can run side by side, how subscribers move during migration and how platform cost grows with your subscriber base. Feature coverage still matters, but it rarely separates serious bids.
Many OTT and IPTV RFPs follow the same pattern. A long requirements matrix, a few hundred rows of features, a column marked "compliant" and a pricing template at the end. Vendors fill in the matrix, nearly every row comes back as a yes and the shortlist is decided on the one number that still looks different: price.
The trouble shows up later. A year after launch, the commercial team wants an ad-supported tier for price-sensitive households. The sports rights team wants a weekend pass. Finance wants to know why the platform invoice grew faster than revenue. None of those questions were in the matrix, so none of them were tested.
Why feature lists stop being useful
Live TV, EPG, catch-up, VOD, multi-DRM and apps for smart TVs and set-top boxes are expected from any credible platform in 2026. Asking whether a vendor supports them filters out the weakest bids and very little else.
What separates platforms is how they behave once the service is running. How quickly they let you change what you sell. How much each change costs. Whether the commercial model still makes sense at three times your launch subscriber base. An RFP that never asks these questions leaves the most expensive decisions to be discovered after signature.
Start with a one-page business brief
Before the requirements section, give vendors a single page that describes the business you are building. It should cover:
- Revenue model at launch and in 24 months. The mix of subscription, advertising, transactional and bundled revenue you expect, and in which markets.
- Distribution. Direct to consumer, bundled with broadband or mobile, sold through partners or a combination of these.
- Subscriber scenarios. A conservative, an expected and an ambitious case, with peak concurrency for your biggest live events.
- Starting point. A new launch, or a replacement for an existing IPTV or OTT platform with live subscribers and installed set-top boxes.
- Team. Who will run the service day to day and what you expect the vendor to run for you.
This page gives every bidder the same frame of reference. It also lets you judge each proposal against your plan instead of against the vendor's brochure.
Eight questions your RFP should make every vendor answer
1. How many days does it take to launch a new package?
Change velocity is the most underrated metric in platform selection. Ask vendors how long it takes, in days, to go from a commercial decision to a live bundle, add-on or promotion. Ask who does the work, too. If the answer involves a change request, a development sprint or a release window, you now know what every future commercial experiment will cost you.
Better still, ask for a live test during the demonstration. Create a package, attach content and a price, then make it available on a test device while your team watches.
2. Can SVOD, AVOD and TVOD run side by side for the same subscriber?
Many platforms support each monetization model on its own. Fewer run them in parallel on one account, with a single entitlement logic deciding what a viewer can watch. Ask how one household could hold a subscription, watch ad-supported content and buy a pay-per-view event in the same week. Then ask how that appears in billing and reporting.
Then ask what it takes to change the model in one market without touching another. If the answer is a new deployment, the platform was built for one business model at a time.
3. What does the commercial model look like at 10,000, 100,000 and 500,000 subscribers?
Launch-day pricing tells you very little. Ask every vendor to price the scenarios from your business brief over the same period and with the same assumptions. Define the charging unit (a registered account, an active subscriber or a household) and list what is included in it.
Then compare the shape of the curve rather than the starting point. An OPEX-aligned, pay-as-you-grow model keeps platform cost proportional to the revenue it supports. A model built on large upfront licences and fixed infrastructure moves risk onto your balance sheet before the first subscriber pays.
4. What happens to existing subscribers on migration day?
For operators replacing a platform, migration is the riskiest part of the project, yet it often sits in an appendix. Move it to the front. Ask how subscriber accounts, entitlements and viewing history are transferred, whether installed set-top boxes stay in service, how DRM is transitioned and what the rollback plan looks like if a cohort needs to move back.
And ask who pays for it. Some proposals look competitive until migration is quoted as a separate professional services project.
5. Which parts of the platform can we replace later?
Your billing system, ad server or recommendation engine may change during the life of the contract. Ask which components can be swapped for your own or a third party's without rebuilding the rest, and whether everything in the admin console is also available through an API.
This is also the place to ask about exit: data export formats, transition support and contract terms. A platform you can leave is usually a platform that has to keep earning its place.
6. Who owns the outcome after launch?
A support desk that resolves tickets is necessary. It is a different thing from a team that reviews your ARPU, churn and package performance and suggests what to change. Ask vendors who will be working with you six months after go-live, what they will review with you and how often.
7. How will we know what is working?
Ask whether viewing, revenue, churn and quality of experience data sit in one place, broken down by package, region and device. If subscription data lives in billing, ad revenue in the ad server and viewing data in a separate analytics tool, every pricing decision starts with a reconciliation exercise.
8. Where does subscriber data live and who can access it?
For services in Europe, this is a compliance question before it is a technical one. Ask about data residency, GDPR processes, role-based admin access and audit trails. Ask for evidence rather than a policy statement. Operators running several markets across Africa or CEE should also ask how different regional data requirements are handled from one platform.
A scoring model that reflects the business
Agree the weightings before the first proposal arrives. The split below is an illustrative starting point for a regional operator launching or replacing a service. Adjust it to your own priorities.
| Criterion | What you are testing | Illustrative weight |
|---|---|---|
| Monetization flexibility | Parallel SVOD, AVOD and TVOD, bundling, per-market changes | 20% |
| Commercial model and total cost | Cost across three subscriber scenarios, charging units, exit terms | 20% |
| Migration risk | Subscriber and entitlement transfer, legacy devices, rollback | 15% |
| Change velocity | Days from decision to a live package or promotion | 15% |
| Viewer experience and devices | Key journeys on your target devices, including older hardware | 15% |
| Operating and partnership model | Who runs what, post-launch growth support, SLAs | 10% |
| Security and compliance | Data residency, GDPR, access control, audit trails | 5% |
Score each criterion on evidence. A capability demonstrated on your own devices deserves more credit than one described in a document, and both deserve more than one listed on a roadmap.
Warning signs in vendor responses
| What the response says | What to ask next |
|---|---|
| "Supported" with no further detail | Is it standard, configured, integrated or custom built? At what cost? |
| "Planned for a future release" | Treat it as unavailable today. What is the committed date and your remedy if it slips? |
| Monetization models priced as separate modules | What will it cost to add AVOD or TVOD in year two? |
| Migration marked "to be scoped" | What is the method, who carries the risk and is it included in the price? |
| Pricing given only for launch volumes | What does the same service cost at three and five times that base? |
| Support described only as SLA tiers | Who works with us on growth after go-live? |
How Vucos approaches an RFP
We prefer to answer RFPs in business terms, because that is how the platform is designed. Vucos runs SVOD, AVOD and TVOD in parallel, so operators can change models per market without re-platforming. Standard deployments go live across nine connected platforms, including mobile, web, smart TVs and set-top boxes, in under 30 days. The exact timeline depends on billing, CAS, CDN and subscriber database integrations.
The commercial model is OPEX-aligned: no upfront platform replacement cost, no multi-year vendor lock-in and terms that scale with your subscriber base. For IPTV operators, we support zero-downtime migration with tokenized database transfers, legacy STB backward compatibility and phased DRM transitions. After launch, a dedicated growth team works with you on packaging and performance instead of leaving you with a ticket queue.
If you are preparing an RFP for a new service or a platform replacement, we are happy to review your business brief and show how we would answer the eight questions above.
Book a Call15 minutes · Free · No commitment
Frequently asked questions
What should an OTT or IPTV platform RFP include? A one-page business brief, functional and technical requirements, migration requirements for existing services, subscriber and concurrency scenarios, a commercial template covering several growth scenarios and a scoring model agreed before proposals arrive.
How do you compare OTT platform pricing fairly? Ask every vendor to price the same subscriber scenarios over the same period, define the charging unit and list everything included. Compare how cost grows with the subscriber base, not only the launch price.
How long does it take to launch an OTT service? It depends mostly on integrations. With a whitelabel platform, launch can take weeks rather than months. Standard Vucos deployments go live across nine connected platforms in under 30 days.
Can an IPTV operator move to OTT without losing subscribers? Yes, if the migration plan covers account and entitlement transfer, legacy set-top box compatibility, a phased DRM transition and a tested rollback. Ask vendors to demonstrate the method rather than describe it.
What is hybrid OTT monetization? Running subscription, advertising and transactional revenue models in parallel on one platform, so an operator can bundle them, switch them per market and change them without re-platforming.