The Refinery
Overall Review Rating
4.3 (8 Ratings)
Overview
At The Refinery they believe in being partners. When you and your project succeeds, so do they. They develop ambitious web applications that never lose sight of the people who use them. Their activities are controlled by corporate policies that define the ways of managing business, staff and client relations. Their mission is to transform traditional business industry and allow more opportunities by using the digital technology.
Services
- Android App Development
- iPhone App Development
- Maintenance
- Private Blockchains
- Cross Platform Development
- Content Marketing
- iOS App Development
- Web Development
- Research & Investigation
- Mobile App Development
- Advertising, Media
- Digital Strategy Management
Industries Served
The Refinery Reviews
Have a look at these client reviews on previously delivered projects.
Abdullah Al-Shehri
Head of Innovation - Desert Tech VenturesProposal matched the outcome. That alignment is rarer than vendors acknowledge.
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
Our campaign workflow ran across twelve different tools. The reconciliation overhead was hurting both speed and accuracy, and our team was absorbing the cost.
Imogen Tanner
Head of Engineering - Outback Data SolutionsBlockchain expertise delivered with plain-English explanations at every step
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
Grid modernisation funding required us to demonstrate demand-response capability. The ML models existed on paper — we needed an engineering partner to build and deploy them.
Hamza Qureshi
Senior Engineering Manager - Karachi Tech SolutionsEvery milestone hit. Every commitment met. No excuses, just delivery.
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
Our LMS was built for classroom-first delivery. Hybrid learning had exposed every assumption it was built on, and student satisfaction data confirmed it.
Nora Al-Otaibi
VP of Engineering - Salam Digital SolutionsBlack Friday traffic spike was the real test. The platform passed without a sweat.
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
Our campaign workflow ran across twelve different tools. The reconciliation overhead was hurting both speed and accuracy, and our team was absorbing the cost.
Khalid Al-Mansoori
Director of Innovation - Emaar Digital GroupFirmware, cloud layer, and dashboard — all three actually talk to each other. Novel.
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
Telehealth demand had turned a pilot into a core service line faster than our technology could keep up. We needed a compliant, reliable platform and we needed it quickly.