Regent Branding
Overall Review Rating
4.7 (6 Ratings)
Services
- Android App Development
- Web Development
- Advertising, Media
- Digital Strategy
- Cross Platform Development
- Mobile App Development
- DevOps
- 3D & Interior Design
- Custom Software Development
- Enterprise App Development
- Platform Development
- iOS App Development
Industries Served
Regent Branding Reviews
Have a look at these client reviews on previously delivered projects.
Nora Al-Otaibi
VP of Engineering - Salam Digital SolutionsUsers come back daily. The engagement data confirmed what we hoped for.
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 mobile app sat at 2.9 stars. Every negative review mentioned the same two things — speed and checkout complexity. Both were fixable with the right engineering approach.
Katrin Bauer
Head of Product Management - Bayern Software KGThe outcome we needed, on the timeline we needed it, by people we would use again
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
The project had a board-level visibility date. We needed a partner who would treat the deadline as their own.
Declan Hartley
Chief Digital Officer - Southern Cross TechnologyAutomation that gave our analysts back 12 hours a week. Real ROI, not projected.
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
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.
Samantha Doyle
Product Manager - Reef Digital Pty LtdZero-trust implementation approved by our enterprise clients' security teams first pass
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
First notice of loss was averaging three days. The market benchmark was under four hours. Automating intake and triage was the agreed priority for the year.
Aarav Mehta
Chief Data Officer - Zenith FinServ LtdPen test found things our previous vendor had missed for two consecutive years
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
A new public-facing service had to launch alongside a policy announcement. The timeline was fixed externally. We needed a delivery partner who would treat it the same way we did.