Abstract: Rules created in a computerized sales playbook system are stored in a rules library. Rules can be shared among playbooks, stages, plays, content and other playbook elements. Any playbook element can be associated with one or more rules. Such rules include one or more conditions that trigger the rule. If the conditions are met, then a playbook element is enabled for use by the user. Rules can be selected from the rules library as the playbook is being created. For example, when adding a play or a content item to a play, a user is prompted to add a rule to be associated with the playbook element. If the user adds a rule, an interface is presented allowing the user to select an existing rule from the rules library or create a new rule. If a new rule is created, it is added to the rules library.

Abstract: By combining information from a CRM system about changes in status of entities, such as customers, leads, and the like, with information about usage of a sales playbook and content related to such playbook usage, metrics describing the effectiveness of content can be determined.

Abstract: Rules created in a computerized sales playbook system are stored in a rules library. Rules can be shared among playbooks, stages, plays, content and other playbook elements. Any playbook element can be associated with one or more rules. Such rules include one or more conditions that trigger the rule. If the conditions are met, then a playbook element is enabled for use by the user. Rules can be selected from the rules library as the playbook is being created. For example, when adding a play or a content item to a play, a user is prompted to add a rule to be associated with the playbook element. If the user adds a rule, an interface is presented allowing the user to select an existing rule from the rules library or create a new rule. If a new rule is created, it is added to the rules library.

Abstract: As plays, stages and other playbook elements are processed or completed in the sales playbook, fields of the customer relationship management system are updated by the playbook system according to predefined update rules. Thus, updating of the customer relationship management system is no longer done separately and manually from activities driven by the sales playbook, and the consistency of data in the two systems is improved. In turn, because the sales playbook is driven by data in the customer relationship management system, activity in the sales playbook can dynamically drive further actions in the sales playbook.