Currently Being ModeratedDec 6, 2012 6:30 AM (in response to Michael Superczynski)
Well, there is sort of a middle ground actually, it's the volume purchase program - but that's not a very good fit either in this case.
We'll figure something out. Maybe we'll use HTML5 (although that's limiting for the things we want to do...)
If the application branding is labels, graphics, and whether specific features are enabled/disabled, consider a single app that dynamically brands itself after the user registers. The user probably needs to supply a server URL, username, and password to connect to your product suite, at this point you know what customer branding to configure. You could download a configuration file specific to that customer.
If your product suite is a commercial-off-the-shelf product with a single code baseline that supports multiple customers, there is a good bet the server components already follow this design pattern themselves.