Can I make CRM like Salesforce using Laravel and adminlte?

Yes, you can. I recently build one using bootstrap and Laravel 5.6

Okay thanks. Can I see that? Maybe an online demo

Can, but only via teamviewer :D

Okay no problem. Can you share your id and password. So I can remote it

~REMOVED~

Do you have skype?

@MOSES - username is same for skype

I want to do it like this. Before I do this project, I want to ask your opinion. make a CRM system with a forecast of conversion of potential customers and inventory. It looks just like the SalesForce version but using the laravel and adminLTE bootstraps. Or I’d better go to machine learning services

The short answer is Yes. It's definitely possible. Actually my team built a CRM for company internal usage last year. The reason to launch this project is that our company want to replace salesforce to reduce costs, and to add some industry specific features.

Now it has features like:

• Dashboards / Reports
• Leas/Accounts/Opportunities conversion
• Tasks
• Row/column level data access permission + role based permissions
• Heavy customization of Page layout / List View
• Global search and List View type of filters
• Very basic workflow / triggers / automation

Our main tech stack is Laravel + React.js + MySQL + Redis + Elasticsearch. And we put some background tasks on AWS Lambda.

However, It's just a very lightweight version of Salesforce, since there are lot of features are cut and changed to a easy implementation.

Also for reference, there are some PHP based commercial CRM systems, such as SuiteCRM. So I bet Laravel is quite capable to build this type of application.

LaraAdmin is an open-source Laravel admin panel. You can develop a CRM system using Laravel with its best backend features.

Laravel multi tenant settings in middleware are super easy to do. That's about 12 code lines. Now you have to tie each element to a particular customer so that you have your DB tables ready for this. There are now several approaches to customizations by customer and 'modules.' In the first place, writing in Hμ/Controllers is super easy and I go there, but I have begun to write a lot of my Laravel code on the packages. To be certain, private packages. They are hosted and installed as other packages, on my own git repo.

It simplifies the distribution of 'features' between clients and also provides a single code base per feature for everybody to receive fixes and updates. If you insist on multi-tenant applications, the greatest problem is that each customer's db/table structure must be the same.

This might be a restrictive factor. I plan to deploy a similar CRM project for a (CRM consultants) using a docker for separate apps, but each customer will receive their very own application instance rather than a multi tenant system. As regards the push of code corrections across customer base bases, different patches can be generated by Unix patch.