How would you design a New Organization workflow that automatically creates a parent organization?

Summary:

Users struggle to follow the data design process which includes first creating a parent organization (if it doesn't exist) and then the child organization and then creating a child organization.

Content (required):

Our systems require a parent-> child relationship for organizations. Many of our customers have many, many organizations rolling up to one parent, however a fair amount exist where it's simply parent->child.

We would like to create a New Organization workflow where the parent is created if needed, reducing the duplicative work.

Do you have any ideas to make this possible?

Version (include the version you are using, if applicable):