projekt202
Overall Review Rating
4.6 (8 Ratings)
Services
- PhoneGap App Development
- Web Development
- AI Development
- Custom Application Development
- Cross Platform Development
- iOS App Development
- Enterprise App Modernization
- Android App Development
- Chat Bots & AI Development
- Mobile App Development
- Cloud Migration Services
- E-Commerce
Industries Served
projekt202 Reviews
Have a look at these client reviews on previously delivered projects.
Nisha Pillai
Director of Engineering - GrowthBridge VenturesEditorial team adopted it without a single support escalation. That is a first.
The platform has been live for six months and is handling three times the transaction volume we scoped for. That is not because we underestimated — it is because the architecture choices made during discovery were genuinely forward-thinking. Most vendors design for exactly what you tell them. This team designed for what you are likely to need. We are already scoping the next phase and there was no question about who we would use.
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.
Matthieu Renard
Directeur Technique - Lumière Technologies SASSecurity posture went from liability to competitive differentiator in one engagement
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
The business case had been approved but the internal resource to execute it had not materialised. External delivery was the pragmatic solution.
Julien Moreau
Co-Founder & CTO - TechLyon SASEnd-to-end testing that our development team now considers a productivity asset
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
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.
Sarah Kimball
Product Manager - Clearpath Health SolutionsThe outcome we needed, on the timeline we needed it, by people we would use again
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
Clinical trial data management was running on a system that had been extended well past its design intent. Quality risks in that context are not acceptable — we needed a proper rebuild.
Tobias Lindemann
Leiter Digitalisierung - Lindemann Industrie GmbHReal-time dashboards that finance and operations both agree on. That alone was worth it.
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
Warehouse management errors were accumulating at a rate our clients could see. A proper WMS was the agreed fix — we needed a development partner who had built one before.