About Tumba Solutions
Tumba Solutions is a technology company founded in 2014. Tumba Solutions focuses on Mobile App Development. The company operates with a team of 10 - 49 professionals. Projects are generally billed around $50 - $99 / hr/hr. Tumba Solutions holds a 4.7-star rating across 6 client reviews. The team is based in Sofia, Bulgaria. Overall, Tumba Solutions is one of the options worth shortlisting for a technology project.
Where We Specialize
Industry Expertise
Typical Project Size
Tumba Solutions Reviews
Write a ReviewProject execution that matched the proposal in every dimension that mattered
Zofia Kamińska / CTO - Odra Tech StudioMay 19, 2026
Project summary: A content deal had given us the rights to a major catalogue but our delivery infrastructure could not stream it reliably at scale. We needed a cloud-native video platform in under six months.
The integration layer was the part of the project I was most concerned about going in. Our system landscape is complex, several of the upstream APIs we relied on were poorly documented, and two third-party vendors had a history of unpredictable response times on integration questions. This team managed all of that. They documented what the upstream vendors could not, built resilience into the integration architecture where the upstream behaviour was unreliable, and delivered a solution that works as specified in production. I could not have asked for more.
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
The engagement was priced at the quality level rather than the budget level. We evaluated the alternatives and concluded that the delta was a reasonable premium for the reduction in delivery risk
Questions & Answers
Security team that communicated findings clearly to non-technical stakeholders — genuinely rare
Radosław Kowalczyk / Head of Development - Wisła Software Sp zooApr 21, 2026
Project summary: A content deal had given us the rights to a major catalogue but our delivery infrastructure could not stream it reliably at scale. We needed a cloud-native video platform in under six months.
The technical quality of the final deliverable is the easiest thing to point to. The automated test coverage is thorough, the deployment pipeline is reliable, the documentation is genuinely useful rather than ceremonially produced. But the metric I keep returning to is the number of post-launch conversations we have not had to have. No incident calls at two in the morning. No emergency patches. No retrospective discussions about what went wrong. The absence of those events is the evidence I would show to someone considering this vendor.
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
The engagement was priced at the quality level rather than the budget level. We evaluated the alternatives and concluded that the delta was a reasonable premium for the reduction in delivery risk
Questions & Answers
Headless CMS that finally allowed our designers and developers to work in parallel
Maja Söderström / Head of Product Engineering - Scandia Digital ABMar 04, 2026
Project summary: Several years of incremental development had left us with a platform that was technically functional but strategically limiting. A structured rebuild was the agreed path forward.
The integration layer was the part of the project I was most concerned about going in. Our system landscape is complex, several of the upstream APIs we relied on were poorly documented, and two third-party vendors had a history of unpredictable response times on integration questions. This team managed all of that. They documented what the upstream vendors could not, built resilience into the integration architecture where the upstream behaviour was unreliable, and delivered a solution that works as specified in production. I could not have asked for more.
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 engagement was priced at the quality level rather than the budget level. We evaluated the alternatives and concluded that the delta was a reasonable premium for the reduction in delivery risk
Questions & Answers
Performance marketing that produced positive ROAS in the first full campaign cycle
Kelsey Drummond / Director of Digital Health - Crestline Health PartnersMar 04, 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.
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.
Deep domain knowledge that reduced the discovery overhead significantly, proactive risk identification before issues became incidents, delivery cadence that our stakeholders found reassuring
We underestimated the input required from our subject matter experts during the requirements phase. The team flagged this early but our resource planning did not fully reflect it — our responsibility, not theirs
Questions & Answers
Project execution that matched the proposal in every dimension that mattered
Takashi Morimoto / Director of IT Strategy - Sakura Digital KKMar 01, 2026
Project summary: Our field service management system had not been updated significantly in six years. Rising technician count and increasing job complexity had exposed every one of its limitations.
What made the most difference in practice was the quality of the engineering judgment on this team. Not the ability to execute a specification — that is a baseline expectation. The ability to recognise when a specification was suboptimal, explain why, propose an alternative, and support the client in making a decision about it. That consultative dimension elevated the output beyond what the brief described and resulted in a product that is more fit for purpose than the one we had originally specified.
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
We underestimated the input required from our subject matter experts during the requirements phase. The team flagged this early but our resource planning did not fully reflect it — our responsibility, not theirs
Questions & Answers
A technology investment that delivered returns ahead of the business case we approved
Théo Beaumont / VP of Innovation - Laurentian Tech PartnersMar 01, 2026
Project summary: Evolving open banking obligations required us to rebuild our API layer from the ground up. The architecture needed to be compliant by default, not bolted on after the fact.
Our stakeholder group included board members, clinical leads, compliance officers, and end users — each with different technical literacy and different success criteria. This team navigated that stakeholder landscape as well as any vendor I have seen. They adjusted their communication register depending on the audience without losing the substance. They managed expectations honestly throughout. And they delivered a system that each group can point to as meeting their requirements. That breadth is genuinely uncommon.
Production system that has performed as specified since go-live without remediation work, documentation thorough enough to support internal maintenance, knowledge transfer that left our team genuinely capable
Their insistence on a detailed functional specification before development began felt like friction at the time. In retrospect, it was the reason the development phase ran without the ambiguity that has derailed similar projects for us previously
Questions & Answers
Test automation that our developers adopted as a genuine aid rather than a compliance exercise
Gustavo Ferreira / VP of Technology - Amazônia Digital LtdaJan 07, 2026
Project summary: Cross-agency data sharing had been blocked by incompatible systems for four years. A secure integration platform was the prerequisite for every transformation initiative in our roadmap.
The technical quality of the final deliverable is the easiest thing to point to. The automated test coverage is thorough, the deployment pipeline is reliable, the documentation is genuinely useful rather than ceremonially produced. But the metric I keep returning to is the number of post-launch conversations we have not had to have. No incident calls at two in the morning. No emergency patches. No retrospective discussions about what went wrong. The absence of those events is the evidence I would show to someone considering this vendor.
Production system that has performed as specified since go-live without remediation work, documentation thorough enough to support internal maintenance, knowledge transfer that left our team genuinely capable
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