Sticksnleaves
Overall Review Rating
4.8 (5 Ratings)
Overview
Sticksnleaves is a Ruby on Rails web and mobile development firm located in Indianapolis, IN. They help their clients develop new ideas and then translate those ideas into products and services that live on the web or on mobile devices. They are one of the few studios in the business that can take a product idea from napkin sketch to a real-world product.
Services
- Web Development
- Hybrid App Development
- Mobile App Development
- Agile Coaching
- Android App Development
- Ruby on Rails
- IT Consulting
- Cross Platform Development
- MongoDB Development
- iOS App Development
- Big Data
- MVP Development
Industries Served
Sticksnleaves Reviews
Have a look at these client reviews on previously delivered projects.
Elliot Thorne
Managing Director, Technology - Redwood Capital AdvisorsThe kind of game studio that treats production quality as non-negotiable
We handed them an aggressive deadline, a complex scope, and a client-side team that was stretched and not always available when they needed us. They handled that gracefully. They were precise about what they needed and when they needed it. Where they could proceed independently they did. The delivery landed on time in spite of the constraints we added. I regard that as strong evidence of genuine professional maturity — not just capability.
Project summary
Our OEE reporting relied on manual data entry at the line level. We needed real-time, reliable data and our existing systems were not going to provide it without a significant rebuild.
Imogen Tanner
Head of Engineering - Outback Data SolutionsFriday deployments used to be stressful. Now they are routine.
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
The project had a board-level visibility date. We needed a partner who would treat the deadline as their own.
Lynne Robichaud
Director of Product - Atlantic Digital CorpProposal matched the outcome. That alignment is rarer than vendors acknowledge.
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 new practice area required document management workflows that did not exist in our current system. We needed them in place before the first client matter opened.
Soo-Yeon Choi
Product Manager - Gangnam Ventures Co LtdCore 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
The project had a board-level visibility date. We needed a partner who would treat the deadline as their own.
Katrin Bauer
Head of Product Management - Bayern Software KGDelivered on scope, on budget, and with zero critical bugs at go-live
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
Our compliance team had flagged gaps that needed fixing before our next regulatory review. The work was too specialist for our internal team to absorb without dropping the product roadmap entirely.