Stoller & Company
Overall Review Rating
4.6 (7 Ratings)
Overview
Stoller & Company remains trust that their customers begin things out & there is not a viable option for the class of service. Their services & solutions cover emerging technologies, constant learning, change and each possible work that would give to the success of their clients. They remain trust that their customers begin things out & there is not a viable option for the class of service.
Services
- Machine Learning
- Branding
- Cross Platform Development
- Azure Services
- iOS App Development
- Automotive R&D
- Android App Development
- Digital Strategy
- Web Development
- Game Development
- Advertising, Media
- Mobile App Development
Industries Served
Stoller & Company Reviews
Have a look at these client reviews on previously delivered projects.
Hamza Qureshi
Senior Engineering Manager - Karachi Tech SolutionsSecurity team that treated our risk as their own. That ownership made all the difference.
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
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.
Tobias Lindemann
Leiter Digitalisierung - Lindemann Industrie GmbHMarketing stopped being a cost conversation and became a revenue conversation
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
The project had a board-level visibility date. We needed a partner who would treat the deadline as their own.
Niamh O'Sullivan
Director of Product - Munster Digital LtdA vendor that earned a place on our preferred supplier list through delivery, not sales
We received proposals from six vendors. Four of them quoted us prices that bore no relationship to the actual scope. This team came back with something realistic and then delivered against it exactly. I have worked on enough technology projects to know that the gap between what is proposed and what is delivered is where trust gets destroyed. There was no gap here. What was promised is what we got, and the ongoing relationship we have built from this is something we intend to continue.
Project summary
The project had a board-level visibility date. We needed a partner who would treat the deadline as their own.
Danielle Westbrook
Chief Digital Officer - BlueSky Retail HoldingsThe outcome we needed, on the timeline we needed it, by people we would use again
Looking back, what strikes me most is how little drama there was. Real technology projects have problems. This one had them too — but every problem was flagged before it became a crisis, every scope change was handled through a proper process, and every risk was managed rather than buried. Our project manager said it was the smoothest vendor engagement he had been involved in. Given how complex the technical requirements were, I think that reflects genuine delivery maturity.
Project summary
Our actuarial models had outgrown the reporting infrastructure feeding them. Data latency was introducing risk into pricing decisions at a rate the business would no longer accept.
Zanele Dlamini
Director of Engineering - Cape Digital SolutionsData science team is actually productive now. First time in two years.
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
The business case had been approved but the internal resource to execute it had not materialised. External delivery was the pragmatic solution.