About Roller Gaming Ltd.
Roller Gaming Ltd. works with clients to plan, build, and ship digital products. Their core services include Mobile App Development and Custom Software Development. With 10 - 49 people on staff, Roller Gaming Ltd. can take on projects of varying size. Typical hourly rates run around $50 - $99 / hr/hr. Roller Gaming Ltd. operates out of Sofia, Bulgaria. These details offer a useful starting point when evaluating Roller Gaming Ltd.
Where We Specialize
Industry Expertise
Typical Project Size
Roller Gaming Ltd. Reviews
Write a ReviewThe team understood mobile-first thinking before we finished the brief
Aarav Mehta / Chief Data Officer - Zenith FinServ LtdMay 28, 2026
Project summary: A previous engagement had delivered something that worked in staging and struggled in production. We approached this project with greater rigour in vendor selection as a result.
We gave this team an aggressive timeline, a technically complex scope, and a client-side project team that was stretched thin and not always available at the speed the engagement required. They absorbed all of that gracefully. Where they needed input they were precise about what they needed and when. Where they could proceed independently they did. The result was a delivery that landed on time despite the constraints on our side, which I regard as evidence of genuine professional maturity.
Senior-level engineering presence throughout the entire project, not just during the pitch, honest and commercially fair handling of scope changes, codebase that our internal team praised on review
The quality of documentation they produce means our team needed to set aside dedicated review time to do it justice — a minor scheduling point rather than a genuine criticism
Questions & Answers
Technically rigorous, commercially grounded, and a genuine pleasure to work with
Reuben Loh / CTO - Marina Bay Ventures Pte LtdMay 16, 2026
Project summary: Our engineering capacity was committed to maintaining existing systems and could not absorb a net-new build of this complexity. An external partner with the right skills was the only viable option.
I came into this engagement as a sceptic. We had been through a failed implementation with a previous vendor and I had high standards for what evidence of competence looked like before I would trust a partner with our core systems. This team earned that trust progressively — through the quality of the discovery documentation, the rigour of the technical proposals, the consistency of the sprint deliveries, and ultimately the stability of the production system. I no longer lead with scepticism when recommending them.
Clear and consistent communication adapted appropriately for both technical and non-technical stakeholders, shared tooling that gave our team real-time visibility, reliable sprint delivery throughout
Time zone coordination required some deliberate overlap management from both sides in the first couple of sprints, after which we had an efficient async rhythm that worked for the whole project
Questions & Answers
A partnership that began with a single project and earned a place on our preferred vendor list
Marcus Holloway / SVP of Engineering - Vertex Cloud DynamicsApr 16, 2026
Project summary: Our legacy LMS had been built for a classroom-first world. Hybrid delivery had exposed its limitations and student satisfaction scores had reflected that for two consecutive years.
We had worked with three agencies before this engagement. The comparison is not flattering to the others. What distinguished this team was a systematic approach to understanding the problem before proposing a solution — something that sounds obvious and is practiced far less often than it should be. The delivery phase ran to schedule, the codebase is clean enough that our internal engineers made positive comments during handover review, and we have not logged a critical incident in five months of live operation. We intend to use them for our next phase of work.
Deep domain knowledge that reduced the discovery overhead significantly, proactive risk identification before issues became incidents, delivery cadence that our stakeholders found reassuring
Pipeline availability for kickoff required a few weeks of lead time — in hindsight that selection pressure means you are working with a team that is in demand for the right reasons
Questions & Answers
The outcome we specified, delivered the way we needed it, by people we would hire again
Takashi Morimoto / Director of IT Strategy - Sakura Digital KKApr 03, 2026
Project summary: Time-to-market for new tariff structures had become a direct competitive disadvantage. Our product configuration layer was the bottleneck and it needed to be modernised as a priority.
The project brief was ambitious and we had received proposals ranging from two to five times our eventual budget from other vendors. This team came back with a proposal that was commercially realistic and technically credible — and then delivered against it. That alignment between proposal and outcome is not something I take for granted. I have been on the other side of it enough times to know it requires both honesty in the sales process and discipline in delivery. We experienced both.
Collaborative culture that made the team feel like a genuine extension of our organisation, strong asynchronous communication across time zones, zero-drama handling of the inevitable mid-project changes
Time zone coordination required some deliberate overlap management from both sides in the first couple of sprints, after which we had an efficient async rhythm that worked for the whole project
Questions & Answers
Technically rigorous, commercially grounded, and a genuine pleasure to work with
Clémentine Aubert / Head of Digital Products - Arc-en-Ciel Digital SASFeb 15, 2026
Project summary: Our agents were spending more time managing data across disconnected systems than managing relationships. We needed a unified platform to give them that time back.
Six months after go-live our platform is processing three times the transaction volume we specified in the original brief. The architecture choices made during discovery accommodated that growth without remediation work. That is the difference between a team that designs for what you tell them and a team that designs for what you are likely to need. We are in conversation about a Phase 2 engagement and I expect to be using this partnership for several years.
Collaborative culture that made the team feel like a genuine extension of our organisation, strong asynchronous communication across time zones, zero-drama handling of the inevitable mid-project changes
Time zone coordination required some deliberate overlap management from both sides in the first couple of sprints, after which we had an efficient async rhythm that worked for the whole project
Questions & Answers
Performance-first web development that Google Core Vitals confirmed was the right approach
Adriana Voss / Director of Platform Engineering - Cascadia Digital VenturesJan 20, 2026
Project summary: Our engineering capacity was committed to maintaining existing systems and could not absorb a net-new build of this complexity. An external partner with the right skills was the only viable option.
We gave this team an aggressive timeline, a technically complex scope, and a client-side project team that was stretched thin and not always available at the speed the engagement required. They absorbed all of that gracefully. Where they needed input they were precise about what they needed and when. Where they could proceed independently they did. The result was a delivery that landed on time despite the constraints on our side, which I regard as evidence of genuine professional maturity.
Deep domain knowledge that reduced the discovery overhead significantly, proactive risk identification before issues became incidents, delivery cadence that our stakeholders found reassuring
Pipeline availability for kickoff required a few weeks of lead time — in hindsight that selection pressure means you are working with a team that is in demand for the right reasons