How can I ensure a database service starts on the preferred node after a database restart?

We have three potential workarounds none of which are ideal so I was hoping someone had a better suggestion.

1. Simply restart the services after all the database instances are up. This is what we are doing now but it means that any apps which reconnect automatically will have connections to the alternate node.
2. Start the instances individually with the preferred node coming up first. This doesn't work for those databases which have multiple services each with a different preferred node. It also requires manual intervention to first check the preferred instance for each node.
3. Script the database startups to start the instances in the correct order. This still doesn't work for those databases which have multiple services as well as requiring a fair amount of work and education.

Any ideas?

Thanks,
Jay