Kreactive
Overall Review Rating
4.3 (5 Ratings)
Overview
They mobilize their experts and tools to set up your "digital factory" to assist you throughout the entire value chain of your projects. They practice a collaborative agile style of development. Their customers become part of their team, they are strongly involved in the development process at all stages. The effectiveness of their approach and high qualifications are confirmed by their excellent reputation and a lot of good feedback from the clients.
Services
- iOS App Development
- DevOps & Cloud
- Cross Platform Development
- Mobile App Development
- Automotive R&D
- Mobile App Design
- AR App Development
- AWS Services
- Business Analysis & Consulting
- Android App Development
- Web Development
- CRM Development
Industries Served
Kreactive Reviews
Have a look at these client reviews on previously delivered projects.
Théo Beaumont
VP of Innovation - Laurentian Tech PartnersSmooth launch, great reviews, no embarrassing bug reports from users in the first month
The technical quality is the obvious thing to highlight. The automated test suite is comprehensive, the deployment pipeline is solid, and the documentation is actually useful rather than written to satisfy a checklist. But the metric I keep coming back to is what has NOT happened since go-live. No 2am incident calls. No emergency patches. No post-launch retrospectives about what went wrong. For a system of this complexity, that outcome is exactly what we paid for.
Project summary
Open banking changes required us to rebuild our API layer properly — compliant by design, not patched together. We needed specialist engineers, not generalists.
Maja Söderström
Head of Product Engineering - Scandia Digital ABMore media coverage from one AR launch than from anything we shipped in the previous year
I have been through several technology implementations in my career. The pattern I am used to is: detailed proposal, optimistic timeline, scope creep, overrun, excuses at the end. This engagement broke that pattern at every stage. The timeline was realistic from the start. Changes were managed through process. The final delivery matched what was agreed. Simple, but uncommon.
Project summary
Expanding to a second clinic location exposed how much of our current platform assumed a single-site model. We needed an architectural overhaul before scaling further.
Beatriz Cavalcanti
Chief Digital Officer - Cerrado Tech SAAccessibility improvements that broadened our audience and satisfied our enterprise clients
Our stakeholder group was unusually broad — board sponsors, operational users, compliance leads, and an IT team with strong opinions. I have watched vendors handle that kind of environment badly. This team adjusted how they communicated depending on who they were talking to, managed expectations honestly when things shifted, and delivered something that each group considers a success. Getting everyone to agree on that outcome was not straightforward and they deserve credit for making it happen.
Project summary
Our property search experience was not matching the quality of the properties we listed. Digital-first buyers noticed, and it was costing us inbound leads.
Khalid Al-Mansoori
Director of Innovation - Emaar Digital GroupOur executives now open the dashboard before their email. That is adoption.
Honestly, I came into this engagement with some scepticism. We had a bad experience with a vendor twelve months earlier and I wanted to see evidence of competence, not just hear about it. The discovery documentation was the first signal. The sprint delivery consistency was the second. By go-live I had stopped being sceptical and started planning how to expand the engagement. The production system has been stable from day one and our internal team loves working with the codebase they left us.
Project summary
A failed engagement the previous year had made us more rigorous about vendor selection. We took the time to find a partner we actually trusted before we committed.
Marcus Holloway
SVP of Engineering - Vertex Cloud DynamicsERP went live on the agreed date. Those of you who have been through ERP projects understand.
The technical quality is the obvious thing to highlight. The automated test suite is comprehensive, the deployment pipeline is solid, and the documentation is actually useful rather than written to satisfy a checklist. But the metric I keep coming back to is what has NOT happened since go-live. No 2am incident calls. No emergency patches. No post-launch retrospectives about what went wrong. For a system of this complexity, that outcome is exactly what we paid for.
Project summary
Cross-agency data sharing had been blocked by incompatible legacy systems for four years. We needed a secure integration layer before any of the transformation projects in our roadmap could proceed.