Persona:  Sales executive working on a sales proposal for a large enterprise cusotmer.
Scenario: Opportunity management in a CRM system for a large enterprise customer. The life cycle of this project spans many weeks and typically involves many people at different levels.
Applications in play:
CRM System: Main workbench with information about the customer, the sales process etc 
MS Word: Create proposal document with tie-ins to back end ERP systems to retrieve real time inventory, pricing, supplier information etc.
MS Outlook to send/receive prosposals both internally and externally.

LH Scenario:
The user has already set up the WinFS system with information about the customer and the main contacts under a special category identifiable to the CRM application. This category also includes relationships established to other contacts in the system who are part of the virtual team of this sales opportunity. This schema is also synchronized with other users of  the virtual team of the oportunity. When the state of an associated document changes ( an  email with the document comes in from one of the contacts of the account team / or /  someone makes a change to critical section of the document ( price for example ) / or / the CRM autogenerates a proposal), the system automatically looks at the document and the user who sent it and automatically forwards it to the other members of the virtual team with the right DRM attached to it based on the user's security level. Based on the contents of the document, it creates a  sharepoint workspace and posts the document on the server. The user sets up his system to automatically forward emails to other participants in the system. Rules can also be written to auto associate documents with customer contacts, proposal IDs etc. LH systems can use the Sync manager to ensure that the other virtual team members also see the metadata and the related associations. This allows the user to automate many tasks associated with working on a simple sales proposal document and ensures that his virtual team is also kept in sync. The user is also able to establish and maintain rich metadata ( through the CRM app or manually ) that can be subsequently used for faster searching and strorage. In a future blog I will explore extending this concept to metadata of the CRM system itself and self propogation of contexts from one app to another. This is a fascinating scenario that might make it seamless to switch from one app to another - For example to go from the CRM system to outlook to word and still maintain a context cache of the CRM data.