Land Group: Frappe HRMS and CRM on a single platform, so people and pipeline share one database
India
Land Group tracked its workforce in one place and its customer pipeline in another, and every handoff between them was manual. ATS Global Techsoft put Frappe HRMS and a Frappe CRM on one platform, so the employee record and the customer record sit in the same system with one permission model over both.
The challenge
Two systems, one business, and a manual join between them
Land Group's people operations and its customer pipeline were tracked separately. A new hire joining a sales team had to be created twice; an enquiry moving to a new owner meant updating a record in one system and telling someone in the other. Each handoff was small, and each one was a chance for the two to disagree.
The cost showed up in reporting. Any question that crossed the boundary — how a team's pipeline looked against who was actually available to work it — meant exporting from both sides and reconciling by hand before anyone could act on the answer. By the time the numbers agreed they described the previous week.
Our approach
One platform for the employee record and the customer record
Delivered by our Backend Engineering practice.
ATS Global Techsoft implemented Frappe HRMS and a Frappe CRM on a single platform. HRMS covers the employee lifecycle end to end: onboarding with documents held against the employee record, attendance, leave policies with approval workflows, and payroll. The CRM covers lead capture, ownership and assignment, the stages of the pipeline, follow-up activity and conversion.
Putting them on one database is the whole point of the design. A salesperson is one record, not two, so their pipeline, their activity and their availability are read together rather than reconciled. Dashboards span both sides. Role-based permissions run down to the field, which is what makes the shared platform acceptable in the first place — salary data and pipeline data are in the same system but not in front of the same people.
- Frappe HRMS: onboarding, attendance, leave workflows, payroll
- Frappe CRM: lead capture, ownership, pipeline stages, follow-up activity
- One employee record across HR and sales
- Dashboards spanning people and pipeline
- Field-level role-based permissions over both domains
- Documents held against the employee record
Architecture
Frappe Framework, Frappe HRMS, Frappe CRM, Python, MariaDB
Both applications run on Frappe Framework against one MariaDB database, with one user directory and one role model. That is the structural decision the rest follows from: because HRMS and CRM are Frappe applications rather than separate products with an integration between them, there is no synchronisation job to fail and no reconciliation window during which the two disagree.
Configuration was done as configuration rather than code wherever the standard doctypes already modelled the domain — leave types, approval chains, pipeline stages and assignment rules are all settings, which keeps the deployment upgrade-safe. Where the business had a rule that Frappe does not model out of the box, it was added as an upgrade-safe extension rather than a fork, following the same approach as our other custom Frappe work.
Building blocks
- Frappe Framework · MariaDB · Python
- Frappe HRMS and Frappe CRM on one database
- One user directory, one role model across both
- Standard doctypes configured rather than forked
- Upgrade-safe extensions where the domain needed them
- No synchronisation job between HR and sales
Technology stack
What changed
People and pipeline read from the same system
Employee and customer records sit on one platform, which removes the manual reconciliation between HR and sales tools and the disagreements it used to paper over. Lead capture, ownership and pipeline stages are tracked in one place with an auditable history, and onboarding, attendance, leave and payroll follow one defined workflow instead of per-team practice.
Managers read sales activity and team availability from the same dashboards rather than two exports, and role-based permissions keep salary and pipeline data visible only to the people entitled to see it. For the same platform extended into full ERP, see Prem Plumbings; for HRMS on its own, see Zara Interiors.
Key results
Employee and customer records sit on one platform, removing the manual reconciliation between HR and sales tools
Lead capture, ownership and pipeline stages are tracked in a single system with an auditable history
Onboarding, attendance, leave and payroll follow one defined workflow instead of per-team practice
Managers read sales activity and team availability from the same dashboards
Role-based permissions keep salary and pipeline data visible only to the people entitled to see it
Let’s work together
Ready to build something great?
Tell us about your project. We respond within one business day and can provide a customised quote for your requirements.