O Wizards of Word! Bless me with your insight!

I thought I would post a question here before I even attempt to develop a
solution - might save me a headache or 2. ;-)

The process I'm trying to support is this: We provide templates to our
partners. Each partner gets the same set of templates, and each type of
template is identical in function for each partner - differing only in the
logo, the partner's address and a few other minor details. The code behind
each template never varies.

When we add a new partner I create a customised set of templates as follows:
I open a 'master' for each template, save it with a new file name (specific
to the partner), modify the few bits that vary (logo, address, etc.), and
then lock it down and distribute it. This works OK at the moment because I've
got a good eye for detail and I'm very familiar with each of the templates.
However, my concern is that I'll miss something or (more likely) someone will
need to take over for me at some point - either because I get hit by a bus or
my open-ended contract finally runs out or some such.

Sooo... What I'd like to do is develop an automated process for creating
partner-specific templates from the master template. Writing the code to
collect the partner details and saving the resulting document as a template
is a piece of piss, but I'm not sure how to go about the rest of it. For
instance, the current 'partner' templates use an AutoNew macro and I expect
that I'd want to use something similar for the 'master', but 2 AutoNews
obviously won't work. And then how would I go about removing the 'master'
code from the 'partner' template (or adding the 'partner' code as the case
may be)? And... and... and...

Anyway, you get the idea. Any suggestions? I guess the first question is
really: Can I use an automated template to create an automated template?

Cheers!

Kiwi Koder