You might have missed the boat on something, I'm no longer developing dMaintenance, DHM, dEvent, or dSupport. They have been retired for sale on my website pretty much right after I got dSS released and stable, and in fact, next time I do some spring cleaning on the old PC, I think the source will be deleted entirely for those legacy dApps, just so I have a good reason not to fix or improve anything with them. As much as I hate to retire a product that I've sold to people, who would otherwise expect me to continue developing it forever like D7, they have all been completely replaced by dSupportSuite which has all of their functionalty and then quite a bit more, with the added benefit that all the various functionality in dSS works together, not separately like the other apps, so reports can be consolidated and other information shared between functions. I only wish I could get everyone to upgrade to dSS so I could just erase those apps from my servers/cloud/etc.
That is exactly why I'm practically giving away dSupportSuite to anyone who bought the legacy dApps. My vision is to develop only two apps, one for the tech (D7) and one for the tech's clients (dSS) and no more. My attention is too divided between different apps and it was starting to wear down on me.
Let me address your suggestions with dSS as the solution:
dSupportSuite does store client information, name, phone, and email in the registry for usage elsewhere. D7 will have the ability to pull the client name from dSS for it's reports when used. I'm not doing it yet, but what I can do is have dSS pull D7's client name IF it cannot find its own.
Maintenance reports - in dSS you can configure them to go to you, the client, or BOTH. The maintenance emails could be a little more friendly, but they aren't bad. As long as you don't include the heartbeat or event logs in the report, it will remain simple.
Automatic expiration - I got nothing for you there right now, but I can *imagine* a way to do this with dSS.
For the nutshell, you can create a custom installer for the client, embed it with their client ID, name, email, and phone. You can configure it any way you want to for that specific client too before deployment. Then upload it to your webserver and send them the download link just as you imagine. Once installed it will appear in your dCloudConsole and you'll need to do nothing else - but from there you can customize it further (if you didn't already when you created the custom installer.)