1. Users
1.1. Developers / Config
1.1.1. Web Designers
1.1.2. System analysts
1.1.3. Developers
1.1.4. System admin
1.2. Home Office
1.3. Agency
1.3.1. Agent
1.3.2. Manager
1.3.3. Assistant
1.4. Customers
1.4.1. Policy Owner
1.4.2. Insured(s)
1.4.3. Beneficiaries
1.5. Group Admin / Plan admin
2. Target Markets
2.1. Only Insurance Carriers
2.2. Product Line support
2.2.1. Life insurance
2.2.2. Annuity
2.2.3. Health
2.2.4. P&C
2.3. Regions
2.3.1. Canada
2.3.1.1. ALL CANADIAN Carriers
2.3.2. USA
2.3.2.1. Focus on OIPA customers
2.3.3. Carribean
2.4. Distribution Echosystem
2.4.1. Predominant Carrier Sales Force
3. Competition
3.1. Custom DEV / Internal IT
3.2. CRMs
3.2.1. SalesForce
3.2.2. SugarCRM
3.2.3. Dynamics
3.3. Industry Portals
3.3.1. Pega System
3.3.2. Sureify
3.4. Generic Portal Platforms
3.4.1. Sharepoint
3.4.2. Oracle WebCenter Portal
3.4.2.1. Oracle WebCenter Portal | Oracle Technology Network | Oracle
4. Problem to solve
4.1. For the carrier
4.1.1. Reduce operational costs
4.1.1.1. Reduce cost of policy changes
4.1.1.2. Reduce paper / mail
4.1.1.3. Reduce agent support
4.1.2. No access to their clients
4.1.3. Provide agents better toolset than competition
4.2. For the agent
4.2.1. No view on the current status of his policies without 3rd party tool
4.2.2. Bulky way to submit changes
4.3. For the customer
4.3.1. Stay in touch on the new business process
5. Key requirements
5.1. Split clearly the front-end and back-end
5.1.1. So that a carrier can use implement it's own UI
5.1.2. To build Agent mobile apps
5.1.3. To more easily upgrade the UI Technology
5.1.4. To feed industry portals (Kronos)
5.2. Front-end
5.2.1. COnfigurable ?
5.2.2. Responsive
5.3. Back-end
5.3.1. Standard industry specific methods / contracts
5.3.2. Build-in OIPA connectors
5.3.3. Can be deployed indepently