PAAS tends to lock you in. You don't notice it happening as you add features, then you discover that escaping the platform requires significant re-engineering. (When freelancing, one of my more lucrative gigs was helping a company de-Herokuize their app after the original developers moved on).
Raw EC2 instances usually end up with wizards SSHing in to deploy & tweak. It's sooo tempting.
Having participated in all of these scenarios in the past, I'd recommend any sized company go right to containers. It's the straightest road from zero through MVP to scale, and the best for onboarding new developers.
That said, don't get sidetracked! Pay a company to manage the orchestration. And don't burn time on accessories like CI pipelines or blue-green deploys until the important stuff works.
Same for raw EC2 instances. When you start reaching double-digit numbers, it gets annoyingly harder especially if they aren't identical (for example, due to having different applications, or applications that can't live together, etc)
Getting something up, running, and making money is really the first priority for a business. Fixing it to not suck or eat all the profits comes later.
And we would have close to zero efficiency benefits related to developing the applications, for the price hike that would allow us to hire dedicated engineers to fix issues that would be either common with PaaS or help us making everything work fine on k8s.
Honestly, it's a lot simpler to either do PAAS, lambdas, or even something like raw EC2 instances to begin with.
The road to containerization and full devops is something that can happen after you've got a working app out in the wild (hopefully) making money.