Short answer: if you're new to betting, testing a market or don't have a tech team, buy a white-label or turnkey platform. A custom backend pays off once your edge comes from how you operate: your channels, your payments, your promotions, your data. At that point, a platform built for everyone starts working against you.
We've been on the "build" side for a long time. One of our longest-running projects is a USSD betting platform for the African market: the MVP took a year with a team of four engineers, and it has been in continuous development for over seven years since. We've also told plenty of people not to hire us. This article explains how we make that call.
What "buying" actually means
"Buy" covers a few quite different models:
- White-label sportsbook. You run your brand on someone else's platform, and often under their licence. It's the fastest to launch and gives you the least control. You usually pay a share of gross gaming revenue, so the cost grows as you grow.
- Turnkey platform. You hold the licence and the platform is licensed to you. You get more control over configuration and payments, but you're still limited to what the vendor's roadmap offers.
- Bought core, custom edges. A provider handles odds, trading and risk. You build the parts that make you different around it. More on this below, because it's where most serious operators end up.
When buying is the right call
We give the same advice outside betting. When a solo founder wants to sell products online, we point them to an established webshop platform, not a custom build. Someone has already solved payments, checkout and order flows, it's well documented, and thousands of businesses have already found the bugs.
Betting works the same way. Buy if:
- You're new to the industry and still learning how your market behaves.
- You want to test a market before committing to it.
- Speed to launch matters more than anything else.
- You don't have (and don't want) a technical team to own a system long-term.
- Your business model is close to how everyone else operates.
In those cases a custom backend means spending a year building something that already exists, before you know whether the business works.
When a custom backend pays off
For more established companies our advice usually flips: build systems around your own processes, instead of bending your processes around someone else's system. In betting, these are the signs:
1. Your channel isn't a website or an app
In much of Africa, mobile internet is still patchy or expensive, and many players use basic feature phones. In Europe this barely matters. There, your channel might be USSD: the *123#-style menus that work on any GSM phone with no data plan. Most platforms are designed for web and app first, and USSD has its own strict limits. Screens are tiny, sessions time out, and every step of building a ticket has to survive a dropped connection. If a channel like this is your main way to reach players, you need software built around it, not an add-on.
2. Local payments are part of the product
Deposits, stakes and payouts through local mobile-money systems and operators aren't just a settings screen. If a payment provider your players rely on isn't on the platform's list, you'll wait on the vendor's roadmap, or you won't get it at all.
3. You need real-time data, not reports on a schedule
Many platforms produce reports on intervals: hourly, nightly, or whenever a batch job runs. In our systems that has never been an issue, because reporting is real-time from the start. When you're watching liability on a big match, a jackpot that's climbing, or a promotion that's being abused, a report from an hour ago is too late.
4. Your promotions and retention are your edge
Bonus bets, jackpots, referral schemes and re-engagement campaigns are often what sets an operator apart. If you can only use the promotion types the platform supports, you look like every other operator on it.
5. The revenue share starts to hurt
A revenue share is cheap when you're small and expensive when you succeed. At some volume, the share you pay every month costs more than a team that would own and develop your platform.
Why tailored software wins over the long run
One example from outside betting stuck with us. In 2015 we built a warehouse and asset management system for a retail network that today spans 1,200 locations in 18 countries. A few years later the company brought in Microsoft Dynamics NAV (Navision), one of the most capable business platforms there is. For a while both ran side by side, connected so data flowed between them. In the end they gave up on Navision for this work and kept ours. It wasn't more powerful. It simply followed how their teams actually worked, with no workarounds. (Read the case study.)
That's the real argument for building. The big platforms win on features. Tailored software wins on fit, and people use the tool that fits.
The hybrid path
You rarely have to choose all or nothing. A common, sensible setup:
- Buy the parts that are commodity, or that are risky to get wrong on your own: odds feeds, trading, risk management.
- Build the parts where you compete: channels (USSD, SMS, retail screens), local payments, promotions and retention, real-time reporting, and back-office tools shaped around your operations.
This gives you a fast, proven core and full control where it matters.
The hidden costs on both sides
When you buy
- Revenue share that grows with your turnover.
- Waiting on a vendor roadmap for features your market needs now.
- Staff working around the system instead of with it.
- Limited access to your own data in the form you need it.
When you build
The cost clients underestimate most is change. Even with a detailed agreement up front, once the product takes shape and real people start using it, you'll find things you want done differently. That's normal, and it's actually the point of custom software, but it has to be in the budget and the timeline from day one.
The second one: it's never finished. A custom platform is a product, not a project. Our USSD platform launched as a one-year MVP and has been in development for seven-plus years since, because the market, the regulations and the business keep moving. That's a strength if you plan for it, and a nasty surprise if you don't.
What a custom build realistically takes
For reference, here's our USSD betting platform.
The MVP: about 12 months, four engineers
From nothing to live with real money, the first version had:
- The USSD product itself: menus players navigate through, plus menu generators so the offer could be rebuilt without code changes.
- Integration with the mobile network operator's USSD gateway.
- One payment provider for deposits, stakes and payouts.
- Automatic settlement of tickets from sports results.
- A back office with reports for the operator's team.
- Security that passed both the bank's and the network operator's requirements. This is easy to underestimate. When real money moves over a telecom network, both partners review how you connect, authenticate and handle transactions, and you don't go live until they sign off.
Notice what's not on that list: no bonuses, no jackpots, no second market. An MVP is the smallest thing that can safely take a real bet and pay it out.
Since launch: 7+ years of continuous development
- Several African markets instead of one.
- Many more payment integrations across mobile-money providers and operators.
- Bonuses, jackpots and referral mechanics.
- Risk alerts, SMS notifications and scaling for peak traffic.
Your numbers will differ, but the shape is typical. Expect about a year to reach a solid MVP for a full platform, less for a single custom module on top of a bought core. Budget time for partner security reviews, and plan for ongoing development after launch.
A quick decision guide
The longer version: the more of these you answer "yes" to, the stronger the case for building:
- Have you already operated in this market and know how your players behave?
- Do you reach players through a channel the platforms handle badly, such as USSD, SMS or retail?
- Do you depend on local payment methods that the platforms don't support well?
- Do you need live data for liability, jackpots or fraud, rather than scheduled reports?
- Are your promotions or retention mechanics a key competitive edge?
- Has your revenue share grown to the cost of a dedicated engineering team?
- Are your staff working around your current system more than with it?
- Are you ready to treat the platform as a long-term product, not a one-off project?
Mostly "no"? Buy, launch, and learn. Revisit the question when the answers start changing.
Not sure which side you're on?
Tell us about your setup. We'll tell you honestly whether to build, buy, or mix both, even if the answer is "don't hire us yet".
Talk to us