InVooDoo
Overall Review Rating
4.2 (6 Ratings)
Services
- DevOps & Cloud
- iOS App Development
- Cross Platform Development
- Hyperledger
- PHP Development
- Android App Development
- Business Analysis & Consulting
- Mobile App Development
- CMS Solutions
- Cloud Computing
- 3D & Interior Design
- Web Development
Industries Served
InVooDoo Reviews
Have a look at these client reviews on previously delivered projects.
Hyun-Su Lim
Director of Platform - Hanam Tech SolutionsIT partner that understands our business, not just our ticket queue
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
Dynamic pricing had been managed manually for years. The revenue opportunity was obvious but building the models and connecting them to the booking engine required expertise we lacked.
Elliot Thorne
Managing Director, Technology - Redwood Capital AdvisorsInfrastructure-as-code that our team uses as a reference example internally
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
The project had a board-level visibility date. We needed a partner who would treat the deadline as their own.
Bram de Vries
Chief Technology Officer - Windmill Tech BVPositive ROAS in the first full campaign cycle. We did not expect it quite that quickly.
Three months post-launch our key metrics are all moving in the right direction — user adoption ahead of target, support volume down, time-on-task reduced for our core workflows. The product team has started planning features that were never viable on the previous platform. That is the real proof of the investment: it opened up possibilities rather than just replacing what was there before.
Project summary
A failed engagement the previous year had made us more rigorous about vendor selection. We took the time to find a partner we actually trusted before we committed.
Melissa Ortega
VP of Product - Brightline EdTech IncOur marketing team can now update the site without filing a ticket. Life-changing.
The platform has been live for six months and is handling three times the transaction volume we scoped for. That is not because we underestimated — it is because the architecture choices made during discovery were genuinely forward-thinking. Most vendors design for exactly what you tell them. This team designed for what you are likely to need. We are already scoping the next phase and there was no question about who we would use.
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.
Erik Lindqvist
Chief Technology Officer - Nordic Cloud ABERP went live on the agreed date. Those of you who have been through ERP projects understand.
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
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.