We are Cactus S.L.
Overall Review Rating
4.3 (8 Ratings)
Overview
They believe in beautiful design in the service of superb user experience. Their job is to help their clients with resolving problems by building great digital products. Their owners passion for web development made them together under one roof. Their power remains in developing, slicing and changing a graphic line that will subtly blend emotion with a connection.
Services
- Mobile App Development
- Azure Services
- Cross Platform Development
- IoT App Development
- Cloud Computing
- Android App Development
- iOS App Development
- Agile Coaching
- Content Management System
- Platform Development
- Web Development
- Internet Marketing
Industries Served
We are Cactus S.L. Reviews
Have a look at these client reviews on previously delivered projects.
Théo Beaumont
VP of Innovation - Laurentian Tech PartnersFirst CMS our content team has genuinely preferred over the alternatives they used before
We went with a smaller team than we had originally planned for. I had concerns about whether the capacity would be sufficient given our timeline. Those concerns were unfounded. The team was focused, communication was constant, and the quality at each milestone review was consistent throughout. Smaller does not mean slower when the people are the right ones and this engagement proved that.
Project summary
Our actuarial models had outgrown the reporting infrastructure feeding them. Data latency was introducing risk into pricing decisions at a rate the business would no longer accept.
Abdullah Al-Shehri
Head of Innovation - Desert Tech VenturesWe went from arguing about the numbers to acting on them. The platform made that possible.
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 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.
Niamh O'Sullivan
Director of Product - Munster Digital LtdMixed reality experience that impressed the client audience we were trying to win
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
A content licensing deal gave us rights we did not have the infrastructure to monetise. We needed a streaming platform that could scale before the deal window opened.
Nisha Pillai
Director of Engineering - GrowthBridge VenturesFirmware, cloud layer, and dashboard — all three actually talk to each other. Novel.
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
Open banking changes required us to rebuild our API layer properly — compliant by design, not patched together. We needed specialist engineers, not generalists.
Beatriz Cavalcanti
Chief Digital Officer - Cerrado Tech SAQA coverage that finally made Friday deployments a professional activity
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
The EV transition had created dealer network management requirements our existing DMS was not designed for. A targeted rebuild was the only path forward that timeline would allow.