We have answers to your questions. But it goes both ways: we do ask questions too, especially at the outset, so you better have answers. We work as single team with your people.
We want to know you and your business very well in order to design a system matching your unique needs. We will then build it efficiently, following your guidance, keeping you involved (and thus informed) about the process. We will deploy it as quickly as possible and keep it running for as long as it takes.
In the terms of software, 12+ years which have passed since the first version of Ruby on Rails was published seems like a very long time. Certainly there are newer frameworks out there. But newer does not always mean better. Rails has aged well, it has matured over years, it has been refined - like good wine aging in a barrel. It has made itself known and a large a friendly community has grown around it. Which brings us to the next point ...
There are many developers out there, if you ever need to enlarge your team. It is not always the case with other frameworks, where the pool of experienced developers is small and hiring a specialist might be a lengthy and costly affair.
…for there is an abundance of learning materials, use cases, extensions (known as gems) providing additional functionality. Consequently, we will not waste your resources by reinventing the wheel, solving problems for which there are already solutions within the Rails ecosystem. Instead, we will be able to concentrate on problems which are unique and essential for your business to thrive.
You’re taking huge risks with the business itself anyway, not knowing if it will catch on and bring you profits you are expecting. Why lower your chances for success by having additional risk in the tech stack. Rails is proven to work and allows you to quickly build your MVP / prototype and start growing your user base.
We have been using it since July 2006, when it was at version 1.1.3 We do remember every lesson we learnt along the way. It takes a few weeks to learn a new language or framework, but it takes years to fully master one. We did master Rails. We want to make sure our clients are getting the most value for their money - we’re using a proven technology that we know well.
With the right approach and discipline, it’s easy to keep the project accessible to new developers. They know what to expect, where to look for things. It’s not as easy in the JS world. This makes it easy to onboard new people and to eventually hand the project off to the client’s team.
We’re not hired to stroke our programming egos or to show off how clever the code we write is. Simple and reliable is the way to go.
Sometimes clients approach us with a problem that’s a perfect match for another toolkit / framework / technology. That’s when we will not use Rails - only when it makes sense.