KTree Computer Solutions
Overall Review Rating
4.8 (8 Ratings)
Services
- AI Development
- MVP Development
- .NET Development
- CMS Development
- Web Development
- CMS Solutions
- iOS App Development
- Enterprise App Development
- Android App Development
- Cross Platform Development
- Data Science & Big Data
- Mobile App Development
Industries Served
KTree Computer Solutions Reviews
Have a look at these client reviews on previously delivered projects.
Omar Al-Farsi
Chief Technology Officer - Falcon Digital VenturesTechnically strong, commercially fair, and genuinely good to work with
What set this team apart in practice was their engineering judgment — specifically, their willingness to tell us when our requirements were wrong and explain what to do instead. Not every vendor does that. The consultative element elevated the final output well beyond what our original brief described. We ended up with something better than what we had asked for, which is not a sentence I expected to be writing in a review.
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.
Pieter van den Berg
Senior Product Manager - Polder SaaS BVOur team stopped worrying about infrastructure. The value of that is hard to overstate.
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
Open banking changes required us to rebuild our API layer properly — compliant by design, not patched together. We needed specialist engineers, not generalists.
Marcin Lewandowski
Engineering Manager - Kraków Digital Sp zooCheckout completion rate improved from day one of production. Not week three — day one.
I have been through several technology implementations in my career. The pattern I am used to is: detailed proposal, optimistic timeline, scope creep, overrun, excuses at the end. This engagement broke that pattern at every stage. The timeline was realistic from the start. Changes were managed through process. The final delivery matched what was agreed. Simple, but uncommon.
Project summary
Open banking changes required us to rebuild our API layer properly — compliant by design, not patched together. We needed specialist engineers, not generalists.
Nisha Pillai
Director of Engineering - GrowthBridge VenturesConnected platform that turned our maintenance team from reactive to predictive
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
OTA dependency was hurting our margins. A direct booking experience that could genuinely compete required an investment we had been postponing for too long.
Declan Hartley
Chief Digital Officer - Southern Cross TechnologyE-commerce rebuild that generated positive ROI before the end of its first quarter live
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
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.