Creating a website with the functionality of a CRM system?

Question

Yii

The client needed an ordinary business card site, nothing is usual, everything is quite primitive, as they say, "you need to have it." But besides this, the main requirements were for the functionality of the site, from them I realized that the client wants a site - a crm system.
Those. there is a certain number of employees working on piecework pay and their work needs to be controlled. In general, the following functionality is needed:
- Each employee has a personal account (with tasks that are assigned to him);
- We need to control the implementation of the task at each stage (reports on the work done for the day or for some period);
- Report to the site owner for the day\week\month (rating of employees, etc.);
- Notifications for missed deadlines.
Something like this. The question, in fact, is how it is possible to organize such functionality?
PS Please do not offer Bitrix and ready-made CRM systems. I would like to look towards the Yii framework. Is it possible to deploy this on it and how difficult will it be to do it?
PPS I will be grateful for detailed answers =)

Answer 1

For the client, install Sugar CRM (now Suite CRM) on a separate computer. If it is something that suits it in terms of functionality, then you can think further what to do. Write it yourself or ready to finish.

Answer 2

Well, if you have six months or a year to make a CRM prototype, then go ahead with the song.
The prototype will be released because you will only be sawing the core with the main functionality.
And then someone will start using it, and it will turn out that many subtleties are not done the way your client’s business process is built.
And it will also be constantly missing something, etc.
And this is because no one will write the TK to you, and even if they do, it’s hard to remember everything.
This is my real experience.
I have been writing CRM (lptracker) alone for the last 3 years.
From scratch, so to speak.

Answer 3

We deployed a similar system with a share of additional functionality on Rails.

Answer 4

Maybe it's the same framework.
If the above requirements are all, then it is quite simple and completely depends on your level.
But something tells me that later there will be additional "Wishlist",
which, if the project is not properly organized and thought through, will become hemorrhoids.
Therefore, in my opinion, there is no need to abandon ready-made solutions (if you are not confident in your abilities and there will be time to complete them in the future), if there is not enough experience, but it would be enough - you would not have asked about it, but would have already written =)

Answer 5

Everything is possible. Just keep in mind that you don’t have a TK yet and won’t have it until the very end.
Therefore, do not be afraid to collect prototypes from shit and sticks - if only the client can run this prototype in a real office and decide what he really wants (usually not what you decided to do according to his preliminary description). Well, the appetite will come while eating, if the project really works - then it can be enriched and polished for years.
Well, a framework (any) will give three pluses here:
1. fewer holes due to the correct approaches to architecture and data imposed by the framework;
2. more sane code, for the same reason - it will be easier to remake and maintain it;
3. at least in the most basic things like authorization and ACL, you can take it ready-made, and not cycle.