Fiddling around with software configuration, making guesses about your stack, and the increased development time this takes will hurt your ability to serve businesses.

Whether you are building a marketing website or a backend dashboard, you will need to make decisions about:

1. Programming language
2. Framework
3. Database
4. ORM for migrations, querying, etc...
5. View layer - whether templating engine or decoupled from backend
6. Job Queue for long running tasks
7. Server and Deployment Strategy

Your choices will significantly impact your speed to delivery, your ability to maintain the project, it's stability long term, and your ability to focus on feature updates in the future.

Running an agency over the years has produced joys and sorrows, hopes and fears and one overriding conviction: the Rails philosophy is 100% correct.
                                                      
1. DRY (Do Not Repeat Yourself)
2. Convention Over Configuration

Ultimately, serving businesses well means reasonable costs, dependable solutions, and deep understanding of a client's business domain. Time is money and you need to use it responsibly; fiddling with configs and reinventing wheels only creates scar tissue.

The Rails Philosophy makes reasonable costs, dependable solutions, and more time for understanding business domain possible.

When getting ready for your next project, consider an old and boring stack like Laravel, Django, Adonisjs or Ruby on Rails.