Overall Review Rating
4.3 (6 Ratings)
Overview
Established in 2001, M-STAT has since become a major value-added services provider in the Greek mobile market. M-STAT focuses on developing mobile products and mobile messaging services that support effective mobile marketing campaigns and business processes. They embrace the constant evolution of technology and mix innovation with market needs to deliver meaningful products.
Services
- Logo Designing
- Maintenance
- Android App Development
- Mobile App Development
- Cloud Provisioning Services
- AR App Development
- Web Development
- Branding
- Cross Platform Development
- iOS App Development
- Hyperledger
- Ionic App Development
Industries Served
M-STAT Reviews
Have a look at these client reviews on previously delivered projects.
Bram de Vries
Chief Technology Officer - Windmill Tech BVUser research surfaced friction points we had stopped noticing. Eye-opening.
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
Open banking changes required us to rebuild our API layer properly — compliant by design, not patched together. We needed specialist engineers, not generalists.
Ji-Woo Park
VP of Engineering - Seoul Digital CorpEvery milestone hit. Every commitment met. No excuses, just delivery.
We received proposals from six vendors. Four of them quoted us prices that bore no relationship to the actual scope. This team came back with something realistic and then delivered against it exactly. I have worked on enough technology projects to know that the gap between what is proposed and what is delivered is where trust gets destroyed. There was no gap here. What was promised is what we got, and the ongoing relationship we have built from this is something we intend to continue.
Project summary
B2B customer churn was concentrated in accounts that rated our self-service portal poorly. A redesign was necessary before the next wave of contract renewals.
Ryan Calloway
Founder & CTO - Apex Digital Media LLC99.97% uptime since go-live. Our SRE team finally sleeps.
We received proposals from six vendors. Four of them quoted us prices that bore no relationship to the actual scope. This team came back with something realistic and then delivered against it exactly. I have worked on enough technology projects to know that the gap between what is proposed and what is delivered is where trust gets destroyed. There was no gap here. What was promised is what we got, and the ongoing relationship we have built from this is something we intend to continue.
Project summary
Digital service standards required citizen-facing systems that our inherited infrastructure simply could not meet. Remediation was not viable — the only credible path was replacement.
Sebastian Lapointe
CTO - Boreal Systems IncUser research surfaced friction points we had stopped noticing. Eye-opening.
We received proposals from six vendors. Four of them quoted us prices that bore no relationship to the actual scope. This team came back with something realistic and then delivered against it exactly. I have worked on enough technology projects to know that the gap between what is proposed and what is delivered is where trust gets destroyed. There was no gap here. What was promised is what we got, and the ongoing relationship we have built from this is something we intend to continue.
Project summary
A new product line required machine tooling integrations we had no experience with internally. We needed engineering expertise that had done this before.
Tanya Wolfe
Senior Product Manager - Harbor Point ConsultingPen test found things our previous vendor had missed for two consecutive years
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
Years of incremental development had left us with a platform that was functional but limiting. A structured rebuild was the agreed path forward.