Simpalm | Digital Product Development Company

Wat was het doel van de samenwerking?We wanted to spend less time on office work so our team could stay focused on our clients. As our practice kept growing, simple tasks started taking more time than they should, and we knew we needed a better way to manage them.

Wat vond je het leukst tijdens de samenwerking?They were willing to learn how our practice actually works instead of trying to fit us into a standard setup. I appreciated that they asked about our day-to-day process before offering ideas.

Zijn er verbeterpunten?A little more time at the beginning to map out the full process on paper would have helped everyone picture the long-term plan sooner. Once we reached that point together, the conversations became much easier.

Wat was het doel van de samenwerking?We wanted a progressive web app that would give our users a mobile-friendly experience without asking everyone to install a native app. It needed to work well across devices and fit into the way our existing platform already operated.

Wat vond je het leukst tijdens de samenwerking?They looked at the project from a user's point of view, not just from a development perspective. More than once, they suggested simplifying a workflow that we had originally made more complicated than it needed to be.

Zijn er verbeterpunten?We needed them to work on a Netsuite project, but it looks like they don't work on Netsuite.

Wat was het doel van de samenwerking?We already had a mobile app in use, but we needed a reliable team to keep it updated and running well as our platform evolved. The goal was to improve stability, handle ongoing changes, and make sure users had a consistent experience.

Wat vond je het leukst tijdens de samenwerking?Simpalm do not jump straight into making changes. They normally look into why an issue is happening first, even if the fix seems obvious. That approach has saved us from creating new problems later.

Zijn er verbeterpunten?Simpalm do not jump straight into making changes. They normally look into why an issue is happening first, even if the fix seems obvious. That approach has saved us from creating new problems later.