RedTree Web Design
Overall Review Rating
4.6 (5 Ratings)
Overview
RedTree is a web design and UX/UI company located in Pittsburgh, PA. specializing in website and user experience. RedTree's main goal is to help businesses best exemplify themselves online with a high-functioning website. With the core of the architecture built and supported, developing on WordPress means accelerated build times and lower project costs.
Services
- IT Consulting
- iOS App Development
- Mobile App Development
- ERP Development
- Web Development
- Agile Coaching
- Maintenance
- Game Development
- PhoneGap App Development
- Cross Platform Development
- Android App Development
- Platform Development
Industries Served
RedTree Web Design Reviews
Have a look at these client reviews on previously delivered projects.
Kenji Watanabe
Senior Engineering Manager - Fuji Software CorpA studio that plays the games they build. It is obvious in the final product.
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
OTA dependency was hurting our margins. A direct booking experience that could genuinely compete required an investment we had been postponing for too long.
Radosław Kowalczyk
Head of Development - Wisła Software Sp zooSession time up 35% since the AR feature launched. The numbers confirm the experience.
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 LMS was built for classroom-first delivery. Hybrid learning had exposed every assumption it was built on, and student satisfaction data confirmed it.
Wei Xin Chua
Product Director - Lionhead Digital Pte LtdOur team stopped guessing and started deciding. That is what good ML looks like.
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 project had a board-level visibility date. We needed a partner who would treat the deadline as their own.
Nisha Pillai
Director of Engineering - GrowthBridge VenturesObservability stack that caught three production issues before any user reported them
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
OTA update orchestration for our software-defined vehicles needed to be bulletproof. The liability implications of getting it wrong were significant enough to justify specialist development.
Erik Lindqvist
Chief Technology Officer - Nordic Cloud ABVR training module preferred by 89% of trainees over the classroom alternative
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.