Conversation recap email format
This communication should demonstrate that you have heard the prospect’s concerns and are prepared to answer with a solution or strategy that addresses those concerns in an efficient, cost-effective manner. Additionally, this email can act as an excellent reference throughout the initial validation and qualification stage of opportunity identification for all sellers.
Solution identification validation
Situation: Dave Ethier, lead enterprise architect (consultant) for ProAg, a subsidiary of CUNA Mutual of Wisconsin. Evaluating potential. Net business rules system. Dave is a team member of a large team of IT and business subject matter experts that are evaluating a business rule management system to be a key component. The BRMS solution will interact with ProAg's new rewritten core applications to manage the organization's risk and compliance rules, among others. The team has established parameters for POCs. Additional teams include the CIO, director of IT, group application manager, manager of policies and procedures, IT project manager and additional contractors and staff with specific subject matter expertise in crop insurance.
Project: Yes (application modernization)
Dave's contact information:
Project objective: Establish a central rule repository, create a system that supports reuse of rules, incorporate a faster method of executing rules coupled with reducing regulatory and compliance risk and improving business usability
Application: Core application rewrite for rating, underwriting, claims, etc.
Users: Mainly business users; however, they'll work collaboratively with IT
Pain point: Updating core systems and government rules that change often, causing them to frequently rewrite (code) new rules
Goals: Reduce IT workload as to coding rules; improve business users' ability to create, manage and maintain rules; reduce risk and potential for noncompliance issues
Technology: Microsoft environment: C and .net
Other solutions: Yes, but not specified
Important questions relate to: Typical rule set-up implementation; development production environment; rule execution process; integration with enterprise environment; business functionality
POC specific areas of focus: Minimum environment for POC and long-term POC environment including development, QA, user acceptance testing, production with high visibility into disaster recovery; evaluation software availability and expected hardware and software environment necessary to conduct a POC
Sequence of events:
- Schedule a minimum two- to four-hour discussion and demonstration as soon as next week
- Decision and direction from POC phase completed by mid-November
- Purchase decision to be made no later than end of November