The question under the question
Most agents ask this as a software question. It is not one. A sportsbook is not a product you install and own, it is an operation that has to be awake whenever your players are, which is most of the week. The choice is whether you run that operation yourself or rent it from someone who already does.
Running it yourself is a real option. It is also a second business, sitting next to the one you already have.
What a book is made of
Price the parts before you price the build. A working book needs a number on every game you offer, kept current around the clock. It needs a site that behaves on a phone, because that is where the wagers come from now. It needs grading that is right every single time, because one wrong grade costs you more trust than a losing week costs you money. Add a casino and a racebook if your players expect them, limits you can set per player and per sport, an agent tree if you carry sub-agents, reports you can close a week from, and hosting that holds up on the heaviest Sunday of the season.
None of that is the half of the business that makes you money. The half that does is who you take, what they are allowed to bet, and what you pay out and when. That half is yours on either path. The argument is only ever about the other half.
The odds feed is a subscription, not a purchase
Numbers have to come from somewhere, and they arrive as a recurring bill. The Odds API, one of the commercial feeds an independent developer would reach for, publishes its plans openly: 500 credits a month free, then $30 a month for 20,000 credits, up to $249 a month for 15 million. Those are list prices for reading odds. They are not the price of running a book on them.
That distinction is the one worth sitting with. An aggregated feed tells you what other books are showing. It does not price your book. Somebody still has to decide what your number is, move it when the money lands on one side, and leave it alone when the move is noise. Buying the feed buys you the raw material, not the trade.
People are the line that never ends
Software that nobody can change is software you are stuck with. Someone has to be able to open it. The United States Bureau of Labor Statistics puts the median annual wage for software developers at 135,980 dollars in May 2025. One developer is not a team, and a team of one is a single point of failure who takes holidays and eventually takes another job.
There is a quieter cost behind that. The person who built your book is the only person who understands it. Losing them is not losing an employee, it is losing the documentation.
The bill that starts on launch day
The build is the cheap half, and that is the part people get wrong. A 2013 review in Acta Informatica Medica reports estimates that roughly 90 percent of a software system's lifetime cost sits in the maintenance phase rather than in the original build. Read that as an order of magnitude rather than a precise figure, because the paper gives it as a general estimate. The direction is not in dispute by anyone who has run software for five years.
Maintenance is not a word for bug fixes. It is the phone operating system changing, the feed provider changing a field name, a payment rail changing its rules, a security patch that cannot wait until Monday, and the sport itself adding a market your players now ask for.
What a weekly fee prices instead
On this platform the rate is $8 per active player per week on Standard and $11 on Pro, with live dealer casino at $13 on top if you take it. The unit is an active player, meaning one whose bet was graded that week, so your cost moves with your week instead of sitting there in quiet months. The two tiers differ in what the player gets, not in how the bill is worked out, and what the weekly bill is made of goes through it line by line.
Worth saying plainly, because this is the part providers blur: BookiePerHead is software and a support line. It takes no wagers and holds no player money. The action, the credit and the settling stay with the agent, exactly as they would if the agent had built the platform himself.
An agent who ran the numbers
Take an agent, call him Nico, running about forty players out of Verano Springs. At forty active heads on Standard he can work out his weekly software cost in his head, and it drops in the weeks his players go quiet.
To match that by building, Nico needs the feed subscription, the hosting, at least one developer who answers on a Sunday afternoon, and several months before any of it takes a bet. He also carries a risk nobody puts in the spreadsheet: that the thing he builds is simply worse than the thing he could have rented, and that he finds out during his busiest week.
His real constraint is not money. It is attention. Every hour Nico spends on a deployment is an hour he is not spending on Tito, the player who has quietly started beating his number.
When building is the right call
Sometimes it is. If you are operating at a scale where the weekly fee has become a large number, if you want the technology as an asset rather than a cost, and if you already employ people who can keep it running, then owning the stack is a strategic choice rather than a hobby.
The honest test is whether you would still build it if building were not cheaper. If cost is the only argument, the arithmetic usually goes the other way once the maintenance years are in it.
The option in the middle
There is a third answer that gets skipped. A white label site puts your own name and domain in front of the same platform, so your players see your book rather than somebody else's, while the pricing, grading and reporting underneath stay somebody else's problem.
It is not ownership. It is most of what agents actually wanted when they said ownership, at a fraction of the commitment.
How to decide
Write down what you are trying to own. If it is the relationship with your players, you already own it, and no build will change that. If it is the technology, price the whole thing: feed, people, hosting, and the maintenance years, not the launch. Then ask who fixes it at two in the morning when a game grades wrong, and whether you want that person to be you.
One more thing, and it needs a lawyer rather than a blog. Whether you may take bets at all, and under what licence, depends entirely on where you are and where your players are. That answer changes by country and by state, it does not change based on whether you built the software or rented it, and it is worth paying someone to answer it properly before you spend a year on either path.