Overall Review Rating
4.1 (7 Ratings)
Overview
Creuna is the leading customer experience agency in the Nordic region. Creuna is an agency with a unique, interdisciplinary business concept and covers everything in digital business and communication from idea to action. They help clients develop brands, grow business and drive change in the connected world.
Services
- DevOps
- PHP Development
- Cross Platform Development
- Cloud Security Services
- ICO consulting Blockchain Implementation
- Enterprise App Modernization
- Research & Investigation
- Mobile App Development
- Android App Development
- Maintenance
- iOS App Development
- Web Development
Industries Served
Creuna Reviews
Have a look at these client reviews on previously delivered projects.
Vikram Srinivasan
Head of Platform - Cascade EdTech SolutionsEvery milestone hit. Every commitment met. No excuses, just delivery.
Looking back, what strikes me most is how little drama there was. Real technology projects have problems. This one had them too — but every problem was flagged before it became a crisis, every scope change was handled through a proper process, and every risk was managed rather than buried. Our project manager said it was the smoothest vendor engagement he had been involved in. Given how complex the technical requirements were, I think that reflects genuine delivery maturity.
Project summary
Streaming quality issues were generating subscriber churn at a rate that made the technical investment case straightforward to approve.
Carlos Vázquez
Director of Technology - Azteca Digital SA de CVMobile experience so polished we have had three enterprise prospects mention it unprompted
Three months post-launch our key metrics are all moving in the right direction — user adoption ahead of target, support volume down, time-on-task reduced for our core workflows. The product team has started planning features that were never viable on the previous platform. That is the real proof of the investment: it opened up possibilities rather than just replacing what was there before.
Project summary
The project had a board-level visibility date. We needed a partner who would treat the deadline as their own.
Nisha Pillai
Director of Engineering - GrowthBridge VenturesPrimary keywords moved from page two to position three in five months
The platform has been live for six months and is handling three times the transaction volume we scoped for. That is not because we underestimated — it is because the architecture choices made during discovery were genuinely forward-thinking. Most vendors design for exactly what you tell them. This team designed for what you are likely to need. We are already scoping the next phase and there was no question about who we would use.
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.
Beatriz Cavalcanti
Chief Digital Officer - Cerrado Tech SAConsulting engagement that paid for itself in avoided rework within six months
What I appreciated most was that they were honest when things were not going to plan. There was one point mid-project where a dependency was going to affect our timeline and they told us three weeks before it would have become critical. That gave us time to adjust. Vendors who manage upward proactively are rare. This one did it consistently throughout the engagement.
Project summary
Moving to a direct-to-consumer model required a platform capability we had never needed before. The build needed to be right the first time given the marketing spend committed to the launch.
Clémentine Aubert
Head of Digital Products - Arc-en-Ciel Digital SASOur engineering team reviewed the handover codebase and was impressed. That rarely happens.
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
Our internal team was committed to maintenance and could not absorb a new build of this complexity. An external partner was the only way to hit the timeline.