Sparkfish
Overall Review Rating
4.2 (6 Ratings)
Services
- CMS Solutions
- Cross Platform Development
- iOS App Development
- Private Blockchains
- Chat Bots & AI Development
- DevOps
- AngularJS Development
- Web Development
- Mobile App Development
- E-commerce Development
- CMS Development
- Android App Development
Industries Served
Sparkfish Reviews
Have a look at these client reviews on previously delivered projects.
Alejandro Ruiz
CTO - Ibertech Solutions SLSupport response times that exceed what we achieved with an internal team
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 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.
Zanele Dlamini
Director of Engineering - Cape Digital SolutionsWent live on time and under budget. Our CFO framed the project charter.
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
Our audience data sat in eight different tools with no shared identity. Personalisation was impossible without first solving that foundation problem.
Siobhan Gallagher
Chief Technology Officer - Northumbria FinTech LtdData science team is actually productive now. First time in two years.
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 internal team was committed to maintenance and could not absorb a new build of this complexity. An external partner was the only way to hit the timeline.
Priya Chandrasekaran
VP of Data & AI - Wavefront Analytics IncSecurity findings explained clearly to our non-technical board. Genuinely uncommon.
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
Our field service scheduling ran on a system that predated smartphones. Technician productivity was suffering and customer satisfaction scores reflected it.
Ji-Woo Park
VP of Engineering - Seoul Digital CorpThe kind of web build that makes you realise how bad the previous one really was
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.