What to write CRM on?

Question

CRM

Hi friends!
I'm studying this issue, I'm interested in the opinion of the community.
It is supposed to create a modular system, a set of modules is selected for tasks, telephony, mail. In general, a standard set. We study ready-made solutions, but our case, when the specificity is very large, is at the heart of the logic.
Interested in:

• entry level. Specialists should not be worth their weight in gold.
  
• Desktop !important (offline required), smartphone and web (optional)
  
• Cross-platform is not required (but welcome), we focus on Windows
  
• Desktop !important, because the database should not be local and not dependent on the Internet
  

In general, you need to climb on the Christmas tree and not get scratched.

Answer 1

Write on what you know best. This is the first and only thing to consider.
We open hh.ru in your region and look for a resume with the keywords C#, Java, PHP, etc. Based on the number of potential candidates and their requests, we understand whether they will be worth their weight in gold or not.
I don’t understand what the problem is to make the application in the browser, i.e. so that your CRM opens through any browser. Megaplan, Amo, etc. work according to this principle. Yes, almost any modern CRM. Take the same path as an option for the base.
Anatoly below in the comments to my answer you write that most people advise you to use the cloud implementation. Let me share my thoughts on this matter.
When developing any desktop application, sooner or later you will face the problem of its correct operation on different machines. For example, you have created a program for Windows. On one machine with Win 7 it works fine, but on Win 7 SP 1 it already gives some kind of error. Another example, 5 machines have the same OS. On 4 of them, your program works fine, but on the 5th, some window is not displayed ... Why is that? You have to sit down and figure it out, digging specifically into the settings of this machine, figuring out what is wrong there, what is not there or is worth it ....
With all this, I want to bring you to one single idea: there is a very big difference between an application that should work on one machine and, an application that must run on tens/hundreds/thousands of workstations.
Writing and maintaining an application according to the second option is much more difficult and more expensive both in terms of time and money. The solution here is just the cloud, and it’s not at all necessary for you to buy a server somewhere in the data center, etc. In the local network of your organization, install the most common system unit on which Debian + Apache + MySQL will stand. Everything, for CRM up to 50 people, this configuration will be more than enough for you. Any of your CRM, be it self-written or purchased, should now work only on one machine, and all the rest are thin clients that interact with it using only a browser. This configuration is easier and cheaper to maintain from all points of view known to me.

Answer 2

I would advise building CRM on the basis of existing solutions. For example, in the PHP world there is OroCRM, open source, sane architecture, built on the basis of symfony, thereby simplifying the search for developers.

Answer 3

See what the requirements are. If this is a web version, then what is wrong with PHP in conjunction with the database?

Answer 4

1C

Answer 5

We need to start doing what we have at hand, what we need right now
Abandon the strict offline requirement An
office without an Internet is fine, but there will also be no telephony, which in modern realities = no work and everyone goes home
If the office is ok without telephony (sic), then let there be an intranet, and in it a site on LinNginxPostgresPHP

Answer 6

Lazarus only!

Answer 7

Write for the web if you want cheap - PHP.
I recommend the Laravel framework.
In it, if necessary, you can combine the local and server database driver. After each action, put a "tick" in the database, after which the application will suck data from the server database into the local one.
Lost network? It doesn't matter, we make changes in the local. Appeared? Comparison, modification.
Although this function is quite complicated, but in any case, you will encounter this difficulty not only in PHP / Laravel. Synchronization between users (locale / server) is needed, there is no getting away from it.