I have recently been 'promoted' to the title of architect and do my best to follow architecture on the P&P & MSDN sites, and discovered a new offering: SaaS Sample Application: LitwareHR. In reviewing the accompanying documentation, starting with the discussion of the "single-instance multi-tenancy patterns" to the discussion "Modularity" in the documentation, I could only think: what planet were these guys on?

Dig into the documentation, and you quickly realize the single-instance multi-tenancy pattern is a super inflated term for 'portal.'  I (and thousands of others I am sure) have used DotNetNuke for just a scenario. In one of my favorite projects, I developed a 'SaaS Solution' for pharmaceutical prepackaging and labeling, whereby I hosted an application used by multiple pharmacies to scan bulk quantity drugs for the printing of single dose labels. I only say this because DotNetNuke has been capable of this all-along.

That being said, the application appears to be an ideal candidate for conversion to a DotNetNuke module, and has at least one neat feature, a workflow editor.

SaaS Site: http://www.skyscrapr.net
MSDN Page: http://msdn2.microsoft.com/en-us/architecture/bb229292.aspx
Codeplex Site: http://www.codeplex.com/litwarehr