Leafcutter
Overall Review Rating
4.5 (8 Ratings)
Overview
Leafcutter is a digital innovation company specialized in accelerating change within organizations by technology. With an experienced team of mobile developers, the company works truly hard with digital masters in order to give the best user experience. At each & every level, they ensure that they continue only with your complete support and full satisfaction.
Services
- Mobile App Development
- Magento
- Cloud Provisioning Services
- iOS App Development
- Automotive R&D
- Web Development
- Cross Platform Development
- Cloud Solutions
- Custom Software Development
- Cloud Computing Software
- Android App Development
- AngularJS Development
Industries Served
Leafcutter Reviews
Have a look at these client reviews on previously delivered projects.
Imogen Tanner
Head of Engineering - Outback Data SolutionsCore Web Vitals are green across the board. Our SEO team sent a thank-you note.
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
Time-to-market for new tariff products had become a competitive liability. Our product configuration layer was the bottleneck and it had been identified as the priority fix.
Takashi Morimoto
Director of IT Strategy - Sakura Digital KKA 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
The business case had been approved but the internal resource to execute it had not materialised. External delivery was the pragmatic solution.
Giulia Conti
Product Manager - Colosseum Digital SrlFinance and operations finally working from the same numbers. That alone was worth it.
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
Our internal team was committed to maintenance and could not absorb a new build of this complexity. An external partner was the only way to hit the timeline.
Zara Hussain
Head of Technology - Ravi Digital AgencyA DevOps engagement that changed both the tooling and the culture
Looking back, what strikes me most is how little drama there was. Real technology projects have problems. This one had them too — but every problem was flagged before it became a crisis, every scope change was handled through a proper process, and every risk was managed rather than buried. Our project manager said it was the smoothest vendor engagement he had been involved in. Given how complex the technical requirements were, I think that reflects genuine delivery maturity.
Project summary
Smart meter rollout generated data volumes our analytics infrastructure could not handle. We needed a platform that scaled without requiring a rebuild every two years.
Tom Harding
Founder - Meridian SaaS LtdComplex project, zero drama. That is how you know the project management is real.
Honestly, I came into this engagement with some scepticism. We had a bad experience with a vendor twelve months earlier and I wanted to see evidence of competence, not just hear about it. The discovery documentation was the first signal. The sprint delivery consistency was the second. By go-live I had stopped being sceptical and started planning how to expand the engagement. The production system has been stable from day one and our internal team loves working with the codebase they left us.
Project summary
Expanding to a second clinic location exposed how much of our current platform assumed a single-site model. We needed an architectural overhaul before scaling further.