How to choose a CRM for a bank?

Question

CRM

Siebel? Megaplan? AmoCRM? Something else?

Answer 1

Bitrix24

Answer 2

well, at least you need to interview employees who worked with what and who likes what and choose a modification for the bank, plus estimate how much time and money it will take to finish it for your specifics

Answer 3

If the question is about the process ("how"), and not the result ("what"), then you can adhere to the following algorithm:
1. Determine the need for the system for your company
- Determine the main customers of the system within the company (who is interested in the system)
- Determine their goals (what business advantage they want to get by implementing the system), based on the goals, make a list of tasks that must be solved in order to achieve the goals
- Make a list of the necessary system functions (by tasks), bring them into a single table, coordinate with business owners -processes.
- If possible, set the weights for the rows of the table (on them, in the future, calculate the total score for the solution and compare it)
2. Conduct market research (look at both public and niche - for banks)
- Make a list of all interested systems
- Fill in the table for each solution, see a demo, if any
- Select systems in the short list
3. Conduct a tender
- For systems from shortlist to select implementers (through a vendor or directly)
- Get proposals for terms / cost
- Select a system and a contractor
What could be included in the summary list of requirements
Functions:
- Common to all CRMs:
- Maintaining a client base (legal entities, individuals) ,
-- Records of contacts with them - calls, mail, meetings,
-- Records of transactions
-- User management (setting up roles, access rights for transactions, records, fields)
- Unique for the bank:
- Maintaining a database of banking products (deposits, cards, loans)
- Credit pipeline with customer assessment
- Integration with external systems (boxed and custom protocols)
Interface (like / dislike, convenient / not convenient)
Server type (own / in the cloud)
Support, SLA (response time, problem resolution time)
Documentation and training
Cost:
- Ownership (regular payments for licenses and support)
- Implementations (implementation project)
- Associated costs (additional software licenses - OS, SQL server, etc.)
- Improvements
Implementation deadlines