Public Alliance
Overall Review Rating
4.7 (5 Ratings)
Overview
Public Alliance is a dynamic marketing, advertising, and public relations agency. They create ambitious, compelling, and beautiful content to change the way people think, feel, and act. Public Alliance is proud to have worked with some leading brands and organizations, and while they are well known for their creativity and responsiveness, it is their commitment to a culture of integrity, transparency, and accountability that truly sets them apart.
Services
- Web Development
- Data Analytics
- Mobile App Development
- ERP Development
- iOS App Development
- Cloud Computing Software
- Cross Platform Development
- .NET Development
- Android App Development
- IT Consulting
- Platform Development
- Mobile App Marketing
Industries Served
Public Alliance Reviews
Have a look at these client reviews on previously delivered projects.
Marco Ferrante
VP of Engineering - Adriatic Tech SrlThe outcome we needed, on the timeline we needed it, by people we would use again
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
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.
Vikram Srinivasan
Head of Platform - Cascade EdTech SolutionsDelivered what the proposal described. More rare than it should be.
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
Years of incremental development had left us with a platform that was functional but limiting. A structured rebuild was the agreed path forward.
Bram de Vries
Chief Technology Officer - Windmill Tech BVFive years of siloed records are now a single analytical asset. Worth every dollar.
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
The business case had been approved but the internal resource to execute it had not materialised. External delivery was the pragmatic solution.
Fiona MacPherson
Operations Director - Highland Analytics LtdAutomation that gave our analysts back 12 hours a week. Real ROI, not projected.
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 merger left us maintaining two incompatible student systems. Data was duplicated, staff were frustrated, and the consolidation had been deferred twice. It could not wait any longer.
Tanya Wolfe
Senior Product Manager - Harbor Point ConsultingDesign system that finally brought visual consistency to a product with four years of debt
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.