Made by Munsters
Overall Review Rating
4.2 (6 Ratings)
Overview
They specialize in crafting web and mobile products that enhance a user's experience and produce results their clients need to succeed. Their team has myriad skills designing and developing web, mobile, interactive and print products. They help establish a complete vision for your product. They combine design, strategy, and development in a process to create compelling user experiences.
Services
- Mobile App Development
- CRM Development
- Android App Development
- Content Management System
- MySQL
- Cloud Computing Software
- iOS App Development
- Cross Platform Development
- ERP Development
- Data Analytics
- Web Development
- Branding
Industries Served
Made by Munsters Reviews
Have a look at these client reviews on previously delivered projects.
Radosław Kowalczyk
Head of Development - Wisła Software Sp zooObservability stack that caught three production issues before any user reported them
The part of this project I had been most worried about was the integration work. Our system landscape is complex, some of the upstream APIs were barely documented, and one of our third-party vendors was notoriously slow to respond. This team documented what the upstream vendors could not, built resilience into the architecture where third-party reliability was uncertain, and delivered integrations that have worked exactly as specified since day one. I genuinely could not have asked for more.
Project summary
Post-pandemic buyer behaviour had shifted heavily to online. Our digital infrastructure had not kept pace with that shift and it was showing in our inquiry volumes.
Yuki Hashimoto
Head of Product Development - East Asia Commerce KKSEO foundation they built is still generating organic traffic eighteen months later
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
A content licensing deal gave us rights we did not have the infrastructure to monetise. We needed a streaming platform that could scale before the deal window opened.
Maja Söderström
Head of Product Engineering - Scandia Digital ABSmart sensor network that paid back the project cost in under two quarters
The knowledge transfer at the end of the project was notably good. Too many vendors see handover as a tick-box exercise. This team ran structured sessions, produced documentation our internal team actually references, and spent real time making sure we understood the architecture decisions well enough to maintain and extend the system independently. Six months later we are doing exactly that without needing to go back to them for every question.
Project summary
Our client portal had not been updated since 2018. Prospects were mentioning competitor portals in pitches. We could not keep deferring the investment.
Callum Parata
CTO - Kiwi Cloud Solutions LtdThe outcome we needed, on the timeline we needed it, by people we would use again
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
Supply chain disruptions had made demand forecasting critical. Our planning team was working off data that was always two weeks out of date.
Marcin Lewandowski
Engineering Manager - Kraków Digital Sp zooPen 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
Matter administration time had grown to the point where it was showing up in utilisation metrics. Every hour spent on systems was an hour not billed — the business case did not need modelling.