I beg to differ; there are a couple of other good reasons why systemd is a good idea.
Before: "Owch, the job failed to start. Now which syslog file did it log its error message to? Oops, it was stderr, so hack the initscript; lather,rinse,repeat".
After: "systemctl status NAME.service"
Before: "This job needs to auto-restart when it dies for whatever reason. Write a hacky wrapper which utterly fails to *not* restart the thing when it *should* die."
After: "This job needs to auto-restart? Add a single well-documented line to the .service file."