CRM: custom solution or adaptation of a finished product?

Question

CRM

Hello!
Please share your thoughts or experience.

Companies with complex business processes have come to implement CRM. In addition to very long transactions, with 10 decision makers and LVRs, there are also complex tasks with BI, which are divided into product groups and regional offices and similar goodies.

I can not understand which CRM to choose.

1) If you take a ready-made solution (for example, Amo or B24) and adapt it, you will have to write a bunch of forms, modules, components, write exchanges with different systems, and so on. As a result, at best, half of the functionality (and far from the main one) will remain from the base product.
Due to the large number of BI tasks, I'm afraid that over time I will have to leave the forms in CRM, and write a separate service for analytics that will pull data from 1C, CRM, and other sources and display them with convenient filters.
You can assemble a couple of people in the state, or a combination of staff-contractor, or contractor (with the possibility of rotation if he can’t cope).
There is experience in this path, but not on such a scale (too much BI).

2) Write a completely custom CRM. Build back and front from scratch. Here it scares that you will need to look for a contractor and fall into 100% dependence on him.
You can’t assemble a team in the state, because it will either not be cost-effective in the end or very slow.

Tell me, please, what do you think about this.

Answer 1

1) I won’t tell you about amoCRM, but in B24, writing a bunch of everything of your own and “at best, half of the base product will remain” is not the right idea, although many come to this opinion. you need a developer who knows how to use the basic functionality to achieve the desired goals.
2) many come to the idea of ​​writing their own CRM, but in the end it turns out to be a waste of time and money.
Now I'll describe the difference:
using B24 it is possible to use the functionality that is already there, if it meets the requirements. At the same time, the functionality is constantly evolving. In addition, when making a recorder, some functions will have to be written for months, although it may take only a couple of days to write the same functions in B24, because. the core contains everything necessary to assemble its logical structure.
From experience: the customer asked to take a recorder (also CRM) for development. Taking into account the big plans for development, in which I saw at least half a life of writing code, I suggested taking a ready-made solution, to which the answer was "we have already tried, we have a different logic of work." In general, the story developed for a long time, but in the end it turned out that it was enough to write one module in B24 and correctly configure everything else, and now all the necessary functionality is there with the necessary work logic.

Answer 2

Companies with complex business processes have come to implement CRM.

Modeling!!!!
You need to spend time:
1. Description of processes
2. Selection of 2-3 items for the description. crm-ki, by trying the Lightly version of the processes
3. Hard-version of the test of adding the process to the selected system

(for example Amo or B24)

are united, here Habré has one representative of crm, even in general, and nothing like that)

Answer 3

You need to look at what is already on the market and understand what functionality you need. If nothing is ready, which is unlikely, then you will have to contact the developers. I don't see any problem here, since taking a ready-made solution, you still depend on developers or integrators. You can change the latter, but if it is the developer who decides to make drastic changes, you can completely come to the second option.