Redwerk
Overall Review Rating
4.6 (8 Ratings)
Overview
It is a software development company. Their core business is to establish and service fully managed by skilled development teams. They take an honest look at your business model and targeted audience. Redwerk specializes in decreasing risk and providing maximum value for your budget.
Services
- Cloud Migration Services
- Android App Development
- Mobile App Development
- CRM Development
- PhoneGap App Development
- Cross Platform App Development
- DevOps
- Cross Platform Development
- Magento
- iOS App Development
- CMS Solutions
- Web Development
Industries Served
Redwerk Reviews
Have a look at these client reviews on previously delivered projects.
Erik Lindqvist
Chief Technology Officer - Nordic Cloud ABZero-trust implementation approved by our enterprise clients' security teams first pass
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
As a technology company ourselves we hold our vendors to the same standard our clients hold us to. Finding a partner who could meet that bar without being hand-held through the process was the challenge.
Imogen Tanner
Head of Engineering - Outback Data SolutionsMulti-region setup and automated failover that we tested twice and it worked both times
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.
Rupert Ashford
Director of eCommerce - Hargrove Retail PLCGameplay feel matched the design intent exactly. Harder than it sounds.
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 product thinking was strong. Our execution capacity in this specific domain was limited. We needed deep expertise, not a generalist willing to learn on our time.
Aarav Mehta
Chief Data Officer - Zenith FinServ LtdA development partner who pushed back when our approach was wrong — exactly what we needed
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
Cross-agency data sharing had been blocked by incompatible legacy systems for four years. We needed a secure integration layer before any of the transformation projects in our roadmap could proceed.
Melissa Ortega
VP of Product - Brightline EdTech IncA vendor that earned a place on our preferred supplier list through delivery, not sales
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 regulatory change required us to rearchitect how we stored and processed customer call data. The timeline was set externally, not by our roadmap preferences.