Platform Solutions
Overall Review Rating
4.5 (7 Ratings)
Overview
Platform is an IT support company located in Jordan that aims to provide secure and efficient IT solutions to Jordanian market and companies. Established in 2014 to provide Support, Networking, Infrastructure consultation, Security solutions, and backups. Platform was born to respond to the abundant amount of requests for various entities, dedicated to help and support them through their IT infrastructure issues and concerns.
Services
- Enterprise App Modernization
- DevOps & Cloud
- Cryptocurrency Wallet Development
- Cross Platform Development
- PhoneGap App Development
- iOS App Development
- AngularJS Development
- Crypto Exchange Development
- Mobile App Development
- Big Data
- Web Development
- Android App Development
Industries Served
Platform Solutions Reviews
Have a look at these client reviews on previously delivered projects.
Melissa Ortega
VP of Product - Brightline EdTech IncArchitecture review that saved us from a vendor decision we would have regretted
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
The project had a board-level visibility date. We needed a partner who would treat the deadline as their own.
Siobhan Gallagher
Chief Technology Officer - Northumbria FinTech LtdFinance and operations finally working from the same numbers. That alone was worth it.
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
Our product thinking was strong. Our execution capacity in this specific domain was limited. We needed deep expertise, not a generalist willing to learn on our time.
Shreya Krishnaswamy
VP of Product - Luminar Tech Pvt LtdThe outcome we needed, on the timeline we needed it, by people we would use again
We handed them an aggressive deadline, a complex scope, and a client-side team that was stretched and not always available when they needed us. They handled that gracefully. They were precise about what they needed and when they needed it. Where they could proceed independently they did. The delivery landed on time in spite of the constraints we added. I regard that as strong evidence of genuine professional maturity — not just capability.
Project summary
Route optimisation was being handled in spreadsheets. The operational cost of that was measurable and the fix was obvious — but it required engineering investment we had been deferring.
Radosław Kowalczyk
Head of Development - Wisła Software Sp zooData science team is actually productive now. First time in two years.
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
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.
Flynn Buchanan
GM of Technology - Pacific Rim Commerce GroupEnd-to-end testing that our development team now considers a productivity asset
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
Expanding to a second clinic location exposed how much of our current platform assumed a single-site model. We needed an architectural overhaul before scaling further.