How we work
The people you test with are the people you go live with.
Most feed relationships are excellent until the contract is signed, and then a ticket queue appears between you and anyone who can help. We built the support story as one continuous relationship instead of three departments.
Getting started
How we start.
Step 1
A 45-minute call
You tell us what you want to fix. No standard demo, and no deck unless you ask for one.
Step 2
You test
Test access, a technical channel and the detailed coverage pack for your markets.
Step 3
You go live
Assisted integration, then production with the same team beside you.
Integration
Testing this doesn’t mean rewriting your world.
The real reason operators stay with a feed they have stopped trusting is the cost of leaving it. So we start with a parallel run against what you already have, nothing switches until you have seen both side by side.
The path
Four steps, and you can stop after any of them.
Step 1
Access
Credentials for the test environment, documentation and working examples, plus a direct technical channel with the engineers.
Step 2
Mapping
Your platform’s sports, competitions and markets mapped against ours, the step that usually decides how long everything else takes.
Step 3
Parallel run
Our feed running next to your current one, on your own fixtures, so the comparison is yours and not a slide.
Step 4
Go-live
Switch when you are ready, per sport or per brand if that suits you better, with the same engineers on the channel.
Timings depend almost entirely on mapping. Ask on the call and you will get the honest range for a setup like yours.
What you get
Documentation, examples, and someone who answers.
Integration goes wrong in the gaps between documents. We would rather you asked a person than guessed from a PDF, so the technical channel opens at evaluation, not at contract.
Documentation
Reference material for the endpoints and structures you will actually use, kept in step with what the feed does.
Working examples
Sample requests and responses your developers can run, rather than pseudo-code in a specification.
A direct technical channel
A line to the engineers building the feed, open from the first test through to production.
Hands-on help to go-live
Practical support through mapping and the parallel run, down to sample code where it is faster than explaining.
Your developers get the full reference through the technical channel as soon as a test starts.
Phase 1
Evaluation
You get a test environment and a technical channel before you have committed to anything, plus straight answers on content, results and performance. If something is not there yet, we say so at this stage rather than after signature.
You are treated as a client before you are one.
Phase 2
Integration
The same channel carries through the build: documentation, working examples and a direct line to the engineers who wrote the feed, until you are running in production.
Practical help, down to sample code.
Phase 3
Production
A dedicated channel for both software and content issues, staffed by the people you already dealt with during evaluation. You are not reintroduced to a new team at the moment things matter most.
Same channel, same people, after go-live.
Who answers
A channel, not a queue.
Content questions go to the people who run the feed. Software questions go to the people who build it. You do not have to know which is which, you write in one place and the right person answers.
Content issues
Missing events, market behaviour, result questions, answered by the feed team directly.
Software issues
Integration, back office and Feed Control Panel questions, answered by the engineers.
Continuity
The same names through evaluation, integration and production.
Hours and response times
Ask on the call. We would rather tell you what we can actually hold to than put a number on a page.