For a reasonable number of services the "correct" solution is to configure the service via debconf during the installation (or by pre populating debconf answers before installation).

After a long time using other distributions I'm installing a Debian box and I'm in shock that this absolutely idiotic behavior is a thing. Get this: You install a package which contains a systemd service. You then go to configure it and start it, only to realize that Debian has already started the service with defaults which are not only completely wrong but actively harmful given the rest of the setup is not done yet.

Looking around the internet reveals that people have had the same problem for 10+ years and find a myriad of hacks and workarounds for a problem which should not exist in the first place. The fact that Debian still struggles with the transition from RC scripts is just a cherry on top. I knew I should have just kept eating Christmas cookies and stayed away from these freaking computer things.

And now I realize that this is probably the reason why you sometimes open a website only to be greeted with the default "You web server is installed" page. These people most likely don't know their web server is even running because they didn't start it themselves...