Sportsbook trading has traditionally been positioned behind the product.
The trading team creates prices, manages liabilities, suspends markets and oversees settlement. The product team takes those outputs and presents them to customers.
That division is becoming increasingly artificial.
Modern sportsbook experiences depend directly on trading capability.
Trading determines which markets exist, how long they remain available, which combinations can be built, whether bets are accepted, how quickly prices react, how cash-out behaves and which customer propositions are economically possible.
Trading is no longer only a supplier of odds.
It is becoming a product function.
Customers experience trading decisions directly
A customer may never interact with a trader.
They still experience the consequences of trading through rejected bets, changed prices, suspended markets, limits, settlement, player-market depth, live availability and Bet Builder combinations.
These are product moments.
When they work well, the sportsbook feels responsive and reliable.
When they fail, customers blame the application or brand, not the internal function responsible.
The organisational separation is invisible to them.
Product ideas increasingly begin with pricing capability
A product manager may propose a next-goal window, a player-substitution feature, a tournament-wide Bet Builder, an injury-protected prop, a personalised market, a next-drive parlay or a live player-performance grid.
Each idea requires trading decisions.
The team must determine:
- Can the outcome be modelled?
- Is the data available?
- How are correlations handled?
- What limits are required?
- When does the market suspend?
- How is it settled?
- What happens during an exception?
- Can the proposition scale across events?
The product cannot be designed fully before these questions are answered.
Trading feasibility and customer experience need to develop together.
FanDuel’s NCAA product shows the operating scale
FanDuel developed a proprietary NCAA basketball trading model beginning in 2021.
By March 2026, its March Madness operation supported approximately 40 to 50 markets per game across a 67-game tournament, alongside Same Game Parlays, futures and live betting. Flutter said the operation had grown roughly fivefold since 2021 and involved more than 130 colleagues across North America, Australia and Europe. (Flutter)
The visible product included redesigned grid views and more ways to combine tournament outcomes.
Behind it sat trading models, market creation, global staffing, pre-created event structures, live pricing, engineering and operational coordination.
The product proposition and trading operation were the same strategic system.
AI changes what trading can produce
Kambi prepared its 2026 World Cup offering to be fully AI traded, using automation to keep live markets open more consistently and reduce friction during changing game states. (Kambi)
The value is not simply fewer manual pricing decisions.
Automation can make possible more player markets, more live markets, faster updates, greater combinability, more consistent coverage, lower operational cost per market and faster expansion into new propositions.
Those outputs change the customer-facing product.
AI trading should therefore be evaluated through both model performance and product impact.
Market availability is a product metric
Trading may measure market uptime operationally.
Product teams should treat it as part of customer experience.
A beautifully designed live event page has limited value when its most relevant markets remain suspended.
Shared measures should include suspension frequency, suspension duration, availability during decisive moments, successful bet acceptance, price-change rate, time from data event to price update and customer abandonment after suspension.
These metrics connect risk decisions to customer outcomes.
Bet Builder removed the boundary
Bet Builder is one of the clearest examples of trading becoming product.
The customer sees a construction interface.
The underlying system must price correlated outcomes, validate combinations, update all related selections, manage exposure, support cash-out, handle player changes and settle each leg correctly.
Product design determines whether the experience is intuitive.
Trading determines whether it is possible.
Neither side can independently create a leading proposition.
Trading can create customer-friendly rules
Product differentiation increasingly includes what happens when real sport becomes unpredictable.
FanDuel’s 2026 World Cup proposition included 120-minute markets and Super Sub, which can transfer a player bet to a substitute when the original selection leaves the field. Flutter said Super Sub originated at Sisal before being adapted for FanDuel’s US customers. (Flutter)
These are presented as product features.
They require trading, settlement and risk logic.
The customer-friendly experience is created through rules embedded in the betting system.
This is where trading moves from pricing existing markets to helping design new forms of value.
Trading and product incentives can conflict
Trading teams may prioritise margin, exposure, accuracy and operational control.
Product teams may prioritise availability, simplicity, adoption and customer satisfaction.
Both sets of priorities are legitimate.
Problems arise when they are optimised separately.
For example:
- Aggressive suspensions reduce risk but weaken live engagement.
- More markets improve product depth but increase operational complexity.
- Simplified settlement rules improve trust but change expected economics.
- Wider bet acceptance improves experience but increases liability.
- Higher margin may improve revenue per stake while weakening competitiveness.
The solution is not to make product responsible for risk or trading responsible for interface design.
It is to establish shared proposition decisions.
Category ownership can help
Flutter described using a dedicated soccer category team for FanDuel’s 2026 World Cup proposition. That team owned the through-line across product and commercial elements while working with Flutter’s wider global football trading operation. (Flutter)
Category-based operating models can connect sport expertise, trading, product, marketing, content and customer research.
Instead of handing outputs between functions, one group becomes accountable for the complete customer proposition within a sport.
The model will not suit every organisation.
The principle is valuable: ownership should follow the customer experience rather than only the internal function.
Traders need product context
As pricing becomes more automated, human traders can contribute more to proposition development.
They possess knowledge about which markets customers value, where models are strongest, which event states create risk, how local behaviour differs, which correlations are difficult, when market availability can improve and which new concepts are economically realistic.
That knowledge should enter product planning early.
Traders should not first see the customer interface when the final requirements reach implementation.
Product teams need trading literacy
Product managers do not need to become quantitative traders.
They should understand implied probability, margin, correlation, liability, suspension, bet acceptance, settlement, data confidence and live delay.
Without this literacy, teams may design experiences that look attractive but cannot operate reliably.
The better the shared language, the faster the organisation can move from concept to production.
A shared product-trading scorecard
Customer
- Successful bet placement
- Market discovery
- Customer understanding
- Complaints and disputes
Product
- Adoption
- Repeat usage
- Tracking engagement
- Feature reliability
Trading
- Margin
- Exposure
- Model performance
- Manual intervention
Joint outcomes
- Market availability
- Bet acceptance
- Price-change frequency
- Settlement time
- New-market launch speed
- Product contribution
The joint outcomes are where strategic advantage appears.
The Adria Nexus view
Trading is still a specialist discipline with responsibility for pricing and risk.
Its strategic role is becoming broader.
Every advanced sportsbook product now depends on the ability to create, manage and explain dynamic markets at scale.
Product teams cannot treat odds as content delivered by another department.
Trading teams cannot treat customer experience as a layer added after the pricing work is complete.
The next generation of sportsbook differentiation will be created where the two functions meet.