Fact 1 - developers love shiny new tools
Fact 2 - proper adoption of new technologies on a project or in a team takes time and money
Fact 3 - most technologies that stick around, stick around because they are bringing in more value than their predecessors

So how do we know when is the right time to go serverless?
Serverless aren't only functions - serverless are also containers, auxiliary services, services which glue your system together, as well as a mindset.
Also, functions aren't only serverless - you can run them on-prem if you will.

Containers nowadays have a critical mass behind them, regardless of them being hosted on-prem, on a VM in the cloud or on a serverless cloud infrastructure.
So the first thing we need to answer is what the business values of developing functions are. But we also need to address what are the downsides.

Only after we've absolved functions can we really start talking about business values which serverless brings, both short term and long term, but we shouldn't do it without mentioning all the pitfalls possibly waiting on that journey.

So, to give you a hint - the answer is, as always, "it depends".

But the very first thing to discuss here is the massive value that teams get by moving to the cloud because all of a sudden a small team or even a single person can set up and develop anything from simple "Hello World" examples to complex distributed systems spread around continents. And all of that can be done without a massive team taking care of servers or planning their deployments.

Now, let's find out which parameters are important for your business success on the serverless journey.