Watermelon Web Works
Overall Review Rating
4.1 (6 Ratings)
Overview
Watermelon Web Works was established in 2002 to develop amazing websites for small businesses & non-profits. They always happy to sit down and meet face-to-face with local clients. The key to great web design is communication – they strive to listen to their client's demands so that they can provide the best results possible that meet their expectations.
Services
- Digital Strategy
- PHP Development
- Android App Development
- iOS App Development
- Machine Learning
- Digital Marketing
- Web Development
- Mobile App Development
- Cross Platform Development
- AI Development
- Cloud Migration Services
- Enterprise App Modernization
Industries Served
Watermelon Web Works Reviews
Have a look at these client reviews on previously delivered projects.
Sabrina Vollmer
Chief Innovation Officer - Rheintal Digital AGPurpose-built platform that made our competitors' off-the-shelf tools look outdated
The part of this project I had been most worried about was the integration work. Our system landscape is complex, some of the upstream APIs were barely documented, and one of our third-party vendors was notoriously slow to respond. This team documented what the upstream vendors could not, built resilience into the architecture where third-party reliability was uncertain, and delivered integrations that have worked exactly as specified since day one. I genuinely could not have asked for more.
Project summary
The business case had been approved but the internal resource to execute it had not materialised. External delivery was the pragmatic solution.
Zofia Kamińska
CTO - Odra Tech StudioSecurity team that treated our risk as their own. That ownership made all the difference.
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
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.
Victoria Haines
Chief Product Officer - Solaris Media GroupMulti-region setup and automated failover that we tested twice and it worked both times
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
Our clinic management system and patient app had never integrated cleanly. The manual workaround had become a daily operational burden that the engineering team had run out of ways to patch.
Danielle Westbrook
Chief Digital Officer - BlueSky Retail HoldingsCheckout completion rate improved from day one of production. Not week three — day one.
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
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.
Maja Söderström
Head of Product Engineering - Scandia Digital ABPerformance-first development that Google confirmed was worth it
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
A new product line required underwriting logic that our legacy system could not support without a rewrite of the rules engine. The workarounds had accumulated to the point of being unmanageable.