The initial aim of Rippler was to solve the problem we were facing as a software agency; So many of our clients were using their personal money to build the software they required to get their MVP created and as a result, they were understandably very price sensitive.
In order to grow our revenues, we wanted to be able to provide bespoke, flexible and high quality software at lower costs, making it affordable for more early stage businesses to build innovative technology products.
We also wanted to reduce the time to market of these products, as entrepreneurs generally want something done yesterday and something done quicker is generally accepted as an improvement.
At the time we did not know it but achieving that vision required a shift in the bespoke software development landscape; A reduction in the cost and development time of bespoke, flexible and quality MVPs by a number of multiples. What we had in mind was £10,000 and one month, from an original starting point of closer to £30,000 in five months.
After much toiling we are now at a stage where we are beginning to deliver on that vision. We have a stable backend and frontend codebase which will reduce development time by multiples, and with the right approach to the development of the project, the costs should be closer to the £10,000 mark than our previous £30,000.
As we troubled ourselves with solving this problem we inadvertently fell into the exciting low code space, or possibly something closer to “less code”, as code is still central to the development of a final MVP with Rippler, we’re just requiring far less leg work in that department for it to be achieved.
We like to think that Rippler will do for bespoke, flexible MVPs, what WordPress has done for the CMS. Of course, we’re a long way away from their level of success, and can currently only dream of having the impact that WordPress have had, in particular via a largely open source solution, but if you don’t dream it, then it’s unlikely to occur.