Softhis
Overall Review Rating
4.3 (5 Ratings)
Services
- Game Development
- Android App Development
- iOS App Development
- Content Management System
- Digital Strategy
- Cross Platform Development
- .NET Development
- Automotive R&D
- CMS Development
- Market Research
- Web Development
- Mobile App Development
Industries Served
Softhis Reviews
Have a look at these client reviews on previously delivered projects.
Zanele Dlamini
Director of Engineering - Cape Digital SolutionsThe kind of web build that makes you realise how bad the previous one really was
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
Years of incremental development had left us with a platform that was functional but limiting. A structured rebuild was the agreed path forward.
Cameron Aldrich
Head of Digital Operations - Northstar Logistics CorpOur remote team now collaborates in VR daily. It changed how we work.
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
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.
Giulia Conti
Product Manager - Colosseum Digital SrlMarketing stopped being a cost conversation and became a revenue conversation
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
Our OEE reporting relied on manual data entry at the line level. We needed real-time, reliable data and our existing systems were not going to provide it without a significant rebuild.
Beatriz Cavalcanti
Chief Digital Officer - Cerrado Tech SASoftware project that finished on time. Simple as that, and rarer than it should be.
We went with a smaller team than we had originally planned for. I had concerns about whether the capacity would be sufficient given our timeline. Those concerns were unfounded. The team was focused, communication was constant, and the quality at each milestone review was consistent throughout. Smaller does not mean slower when the people are the right ones and this engagement proved that.
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.
Kenji Watanabe
Senior Engineering Manager - Fuji Software CorpPen 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
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.