CASE STUDY
Building a Pan-India Sales Pipeline on Frappe CRM.
How Sanskar Technolab modernized lead-to-deal management, territory governance, and sales forecasting for Orient Electric - without forking the platform.
Client Overview
Orient Electric is a major Indian manufacturer of electrical products spanning Fans (Ventilation, Decor, BLDC), Switchgear (Euro Tech MCB, Canvas O DB, Cat-6 networking), Appliances (Air Coolers, Mixer Grinders, Toasters), Lighting, and Smart Accessories. The company sells into a complex B2B and B2G landscape - builders, government tenders, commercial properties, and channel partners - through a geographically distributed sales team operating across every state.
Before this engagement, sales pipeline tracking was fragmented across spreadsheets and informal handoffs. Territory ownership, forecast accuracy, and visibility into the order book versus actual billing were all difficult to govern at scale.
New Delhi,India.
Industry
Electrical Equipment Manufacturer
Apps implemented
ERPNext
Frappe CRM
Frappe Insights
modules implemented
CRM
Insights
The Challenge
Orient Electric's leadership defined six concrete requirements the existing tooling could not meet:
Fragmented Lead Pipeline
Leads from 15 acquisition channels - website, WhatsApp, exhibitions, cold calls, references - needed a single qualification workflow. Reps were re-keying information across tools, and qualification status was inconsistent.
District-Level Territory Governance
Sales spans India. The team needed a three-level hierarchy (India → State → District) and the ability to filter every dashboard, deal list, and report by any level. Roughly 790 districts had to be addressable.
Intelligent Product Catalog
A 150-product catalog needed a two-level structure where choosing a category instantly narrows the sub-category dropdown - preventing data-entry errors that corrupt downstream reporting.
Role-Based Visibility
A territory manager handling West India must not see East-zone deals, while national admins need the full picture. Sales-person attribution had to follow deal ownership automatically - no manual mapping.
Forecast & Billing Visibility
Monthly reviews ask: how much was the order book last month, how much has actually been billed, and what is projected for the current month, M+1, and M+2? Numbers had to be live, filterable, and trustworthy.
Upgrade-Safe Customization
On managed Frappe Cloud, custom apps were not an option. Every business rule, validation, and cascading behavior had to live in Frappe's scripting layers - and stay compatible with future CRM releases.
The Solution
Sanskar Technolab delivered a configured Frappe CRM v2 deployment with custom fields, server-side automation, and form-script-driven dynamic behavior - all without writing a custom Frappe app. Below is how each business problem was solved.
Lead and Deal Management
A complete lead lifecycle was configured: New → Contacted → Nurture → Qualified → Converted, with structured Unqualified and Junk states. Qualified leads convert to Deals progressing through a 7-stage pipeline - Qualification (10%) → Demo (25%) → Proposal (50%) → Negotiation (75%) → Ready to Close (90%) → Won (100%) / Lost (0%) - each with probability mapping for weighted forecasting.
Custom fields on the Deal doctype include Deal Type (B2B/B2G), Degree (Hot/Warm/Cold), Project Type, Project Name, City, Size, Number of Units, Total Project Potential, Billed Value, and the forecast fields Current Month, M+1, and M+2 - capturing both opportunity value and actual billing in one record.
Territory Hierarchy
A three-level structure (India → State → District) was built on the standard Frappe Territory doctype. 790 district records were configured and seeded. A custom Parent Territory field on each Deal and Lead auto-populates from the territory's parent, enabling state-level rollups without re-keying. Every dashboard chart and saved view supports filtering on either level.
Cascading Product Catalog
A two-level CRM Product hierarchy was built (150 SKUs across Fans, Switchgear, Appliances, Smart Accessories, Lighting). On both Lead and Deal forms, selecting a Product Category triggers a live-loaded CRM Form Script that instantly filters the Sub-Category field to children of that category only. Clearing the category clears the sub-category - preventing orphaned data. The form-script approach was selected specifically because the Frappe CRM frontend is a Vue 3 SPA, where classic Frappe client scripts do not apply.
Automated Sales-Person Mapping
Three server scripts were developed to keep attribution self-healing:
-
CRM Deal - Before Save: when deal_owner changes, the script looks up the linked Employee and populates custom_sales_person and custom_employee. Smart change detection avoids unnecessary writes.
-
CRM Lead - Before Save: identical logic for leads, ensuring lead ownership and sales-person reporting stay in lock-step.
-
Employee - After Save: validates no circular reporting, syncs Sales Person on/off based on the "Is Sales Person" checkbox, updates the hierarchy tree when managers change, and creates DocShare entries so each sales person sees exactly the leads and deals they own.
Role-Based Visibility
DocShare entries created by the Employee server script ensure each sales person sees only their assigned records. Named saved views - one per territory manager - let leadership open West, South, Northeast, or any custom slice in a single click without re-navigation. Quick filters are pre-configured per doctype for fast list navigation.
Manager Dashboard
A consolidated dashboard delivers 14 components: KPI cards (Active Customers, Annual Sales, Open Opportunities, New Leads in last 30 days), pipeline funnel by stage, sales trends, territory breakdown, sales-person performance, and product-category analysis. Dashboard-level filters cover Territory, Project City, Project Type, and Expected Closure Date - so the same canvas serves the national VP, a zonal head, and a district rep with no separate dashboards to maintain.
Sales Forecast & Billing Projection
Three custom currency fields on the Deal - Current Month, M+1, M+2 - capture monthly billing projections that reps update during reviews. The Insights layer surfaces these as number cards and grouped bar charts (by salesperson and by territory), plus an accountability table flagging deals where projection values are stale - making it immediately visible which reps have not updated forecasts before a review meeting.
Lost-Reason Catalog & Win/Loss Analysis
19 structured lost reasons (Budget Constraints, Competition, Make Not Approved, Long Sales Cycle, Pricing, Unresponsive Prospect, and more) replace free-text "why we lost" notes - enabling clean win/loss analysis by territory, product, and rep.
Number Better Speak For Themselves!
790Territory Records
150Catalogued Products
7Pipeline Stages
Implementation Approach
Four iterative phases, with continuous client involvement and demos before each go-live.
Phase 1:
Discovery & Baseline Data
Working sessions with the CRM Administrator and Sales leadership translated the existing spreadsheet workflow into a Frappe doctype model: territory tree (790 districts), product taxonomy (150 SKUs), lead sources, lost reasons, and the full set of custom fields.
Phase 2:
Configuration & Scripting
Custom fields added via the Frappe UI (no schema migrations needed). Server scripts for the sales-person and employee sync flows built and tested against staging data. Vue-based CRM Form Scripts developed for cascading product filters - selected specifically because the Frappe CRM frontend is a Vue 3 SPA where classic client scripts do not apply.
Phase 3:
Dashboard & Reporting
The Manager Dashboard was built iteratively with the Sales Admin team - starting with KPI cards they reference in weekly reviews, then adding the pipeline funnel, territory breakdown, and salesperson performance. Frappe Insights powered the billing projection visualizations and the accountability table flagging stale forecasts.
Phase 4:
Data Migration & Handover
Historical leads and deals imported. Edge cases addressed transparently - ~40 deals flagged with blank territories for manual correction, duplicate lost reasons consolidated. A comprehensive handover document (architecture, fields, scripts, dashboards, roles, recommendations) was produced for the in-house CRM team.
Outcomes
The deployment delivered measurable improvements across visibility, governance, and team productivity.
One Source of Truth
Leads, deals, accounts, contacts, and billing forecasts all live in a single Frappe CRM workspace - replacing scattered spreadsheets.
District-Level Governance
790 territories let leadership analyze the pipeline at national, state, or district granularity in the same dashboard - no data exports required.
Self-Healing Sales Attribution
Every deal and lead is tagged with the right sales person, employee, and parent territory the moment it is saved - eliminating manual mapping and reporting drift.
Cleaner Data Entry
Cascading product filters mean reps can only select valid sub-categories for the chosen category - preventing the data-quality issues that break downstream reporting.
Faster, Honest Reviews
Named saved views per territory manager open straight into the right pipeline slice; the accountability alert table makes it instantly clear which reps have not updated their M/M+1/M+2 projections.
Order Book vs. Billing
Leadership can now compare won-order value against billed value at any time - the central metric of sales-execution health.
Upgrade-Safe Customization
Because every customization lives in scripts and configuration rather than a forked app, the deployment stays compatible with future Frappe CRM upgrades on the managed cloud.
Documented Handover
A complete reference document - system architecture, custom fields, scripts, dashboard configuration, user roles, recommendations - gives the in-house CRM team full ownership from day one.
At a Glance
A production CRM managing ~1,657 leads, ~1,438 deals, and a 790-node territory tree spanning every district of India - with a live Manager Dashboard, automated sales-person mapping, and clean handover documentation.
Ready to Transform Your Operations With a Powerful Sanskar ERP?
Related Case Studies
SAP to ERPNext Migration
ERPNext
Manufacturing
Food
Migrating From SAP To ERPNext For Our Client: A Success Story!
Sanskar Technolab is the leading ERPNext partner, providing a diverse range of services to our clients. This time, we have provided end-to-end and seamless SAP to ERPNext migration services.
10 min read
Garment Manufacturing
ERPNext
Manufacturing
Textile
Jagdamba Textile is saving 45 ManPower hours daily with our ERPNext Implementation.
Our client is willing to streamline their textile manufacturing and operations by leveraging the best-in-class ERP and wanted boost in employee productivity. We've understood their business needs and offered end-to-end ERPNext implementation solutions.
8 min read
Oracle to ERPNext Migration
ERPNext
Manufacturing
Migrated from a 20-year-old Oracle platform to an All-New ERPNext platform!
Sanskar Technolab is an official ERPNext Partner, and this time, one of our clients who is tired of handling their outdated system on Oracle has reached out to us for seamless migration to ERPNext and even implementation.
11 min read