The same people who hate on no-code also often hate when they have to develop some simple CRUD app (which is where no-code excels). I personally think that ther

The same people who hate on no-code also often hate when they have to develop some simple CRUD app (which is where no-code excels). I personally think that there will be a huge no-code revolution, because of the simple fact that there are still a lot of manual paper-based poor efficiency processes in businesses. Without no-code software, the cost to automate a simple business process which takes a low paid admin worker 3 hours per week might be: * Requirements Gathering (Let's say 1 day) * Development time (Let's say only 5 days) * Testing time (Let's say its fast and only takes 1 day) * Bug fixing (Another day) * Ongoing Support and changes (estimated 25% per year) So at $500 per day and this incredibly conservative timeline, let's say that solving that simple business process costs $4,000 capex with $1,000 annual costs including infra. This saves 3 hours of work for someone on minimum wage... $2,340 per year. A few problems: * Problem Number 1 - This doesn't meet most companies hurdle rates (>2 year payback). * Problem Number 2 - The problem wont be deemed 'big value' enough to get IT resource assigned * Problem Number 3 - People in general want to work on 'bigger problems' and will hate going solo on a tiny piece of work to reduce a single workers week very slightly. Ok, so that's fine from a company perspective, but look at it from the minimum wage workers perspective - They might be doing something that they KNOW they themselves could automate, but their IT department won't do it because they deem their time too valuable, and they aren't allowed to do it themselves because they aren't deemed knowledgeable enough. No-Code shouldn't aim to solve all problems, it should aim to solve the problems that are below IT's threshold but still deliver user value, otherwise there is value left on the table and you have people doing work that could be better automated or put on a better platform. It's not to replace everything, its to build something that's better than excel and paper, when your IT department can't/won't build it because of capacity/hurdle rates/investment.