Nisos Technologies
Overall Review Rating
4.4 (5 Ratings)
Services
- CMS Solutions
- iOS App Development
- Android App Development
- Cloud Computing Software
- Mobile App Development
- Cross Platform Development
- Web Development
- Magento
- ERP Development
- Mobile App Design
- CRM Development
- MySQL
Industries Served
Nisos Technologies Reviews
Have a look at these client reviews on previously delivered projects.
Amit Goldstein
VP of Product - Tel Aviv Ventures LtdQA coverage that finally made Friday deployments a professional activity
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
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.
Alejandro Ruiz
CTO - Ibertech Solutions SLComplex project, zero drama. That is how you know the project management is real.
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
Peak season traffic would regularly expose platform instability. Every year we patched. Finally we decided to fix it properly rather than worry about it again twelve months later.
Pieter van den Berg
Senior Product Manager - Polder SaaS BVAd spend efficiency improved 40% without reducing reach. The targeting work was the difference.
We have worked with a few agencies over the years and the comparison is honestly not close. What stood out from the start was that they spent serious time understanding the problem before they proposed anything. Once development started, every sprint review was clean — no hidden surprises, no slipped milestones. The production system has been running for four months without a single critical issue. Our internal developers reviewed the codebase at handover and were genuinely complimentary about the quality. That does not happen often.
Project summary
Multi-touch attribution across our full media mix was the most consistently requested capability by every client in our book. We could not deliver it without rebuilding the data foundation.
Kenji Watanabe
Senior Engineering Manager - Fuji Software CorpHeadless CMS that let designers and developers finally work in parallel
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
Accreditation requirements had raised the bar on how we needed to document and track student progress. Our existing tools were not capable of meeting the new reporting standards.
Marcin Lewandowski
Engineering Manager - Kraków Digital Sp zooLegacy-to-cloud-native in a timeline our previous vendor said was impossible
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 regulatory change required us to rearchitect how we stored and processed customer call data. The timeline was set externally, not by our roadmap preferences.