Many Hats
Overall Review Rating
4.2 (5 Ratings)
Services
- Android App Development
- iOS App Development
- Web Development
- Cross Platform Development
- Agile Coaching
- Mobile App Development
- MongoDB Development
- CMS Solutions
- Game Development
- Chat Bots & AI Development
- IoT App Development
- IT Consulting
Industries Served
Many Hats Reviews
Have a look at these client reviews on previously delivered projects.
Amit Goldstein
VP of Product - Tel Aviv Ventures LtdSingle source of truth — if you understand how rare that is, you understand why we rate them so highly
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.
Tariq Al-Harbi
Director of Technology - Saudi Cloud HoldingsPen test found things our previous vendor had missed for two consecutive years
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
A merger left us maintaining two incompatible student systems. Data was duplicated, staff were frustrated, and the consolidation had been deferred twice. It could not wait any longer.
Derek Watts
Director of Operations - Stonebridge Capital LLCTechnically strong, commercially fair, and genuinely good to work with
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
A merger left us maintaining two incompatible student systems. Data was duplicated, staff were frustrated, and the consolidation had been deferred twice. It could not wait any longer.
Victoria Haines
Chief Product Officer - Solaris Media GroupFinally — ML that our operations team actually uses rather than ignores
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
Seven years of incremental changes had left our trading platform fragile. Latency was worsening, technical debt was growing, and the rebuild conversation had been postponed long enough.
Marcin Lewandowski
Engineering Manager - Kraków Digital Sp zooSeven legacy systems replaced. One consolidated data model. Genuinely transformative.
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
A new care pathway required patient data to move between systems in a way our current architecture did not support. The integration complexity was beyond what we could handle in-house.