42 Coffee Cups
Overall Review Rating
4.8 (6 Ratings)
Overview
42 Coffee Cups is a growing team of highly experienced Python/Django developers with over 15 years experience in web development and more than 9 years using Django, doing various projects over the US, Canada, Australia, UK & Europe. The main expertise is in heavy backend development using Python. Provides a high-quality web and mobile development service using Python and Django, native iOS and Android development.
Services
- Blockchain Development
- Mobile App Development
- Cross Platform Development
- MongoDB Development
- Web Development
- AWS Services
- iOS App Development
- Android App Development
- Maintenance
- DevOps
- Ionic App Development
- Branding
Industries Served
42 Coffee Cups Reviews
Have a look at these client reviews on previously delivered projects.
Siobhan Gallagher
Chief Technology Officer - Northumbria FinTech LtdOur old app had a 2.8 rating. The new one is at 4.6. The comparison is all you need.
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
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.
Tariq Al-Harbi
Director of Technology - Saudi Cloud HoldingsRebuilt from the ground up. Launched on time. Zero regression issues.
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
Traceability legislation had set a compliance deadline that was not negotiable. Our supply chain system needed targeted development and we needed people who had done it before.
Callum Parata
CTO - Kiwi Cloud Solutions LtdCRM that connects marketing automation to revenue data seamlessly at last
Our stakeholder group was unusually broad — board sponsors, operational users, compliance leads, and an IT team with strong opinions. I have watched vendors handle that kind of environment badly. This team adjusted how they communicated depending on who they were talking to, managed expectations honestly when things shifted, and delivered something that each group considers a success. Getting everyone to agree on that outcome was not straightforward and they deserve credit for making it happen.
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.
Gustavo Ferreira
VP of Technology - Amazônia Digital LtdaSession time up 35% since the AR feature launched. The numbers confirm the experience.
What set this team apart in practice was their engineering judgment — specifically, their willingness to tell us when our requirements were wrong and explain what to do instead. Not every vendor does that. The consultative element elevated the final output well beyond what our original brief described. We ended up with something better than what we had asked for, which is not a sentence I expected to be writing in a review.
Project summary
Track-and-trace had gone from differentiator to baseline expectation in our client contracts. Our platform had neither and the gap was showing up in tender evaluations.
Preet Sandhu
Senior Engineering Manager - Prairie Tech Solutions IncPlatform engineering work that finally let product teams move independently
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 EV transition had created dealer network management requirements our existing DMS was not designed for. A targeted rebuild was the only path forward that timeline would allow.