Swalok Group CRM
Gives a multi-division enterprise one place to track clients, sales, tasks and performance.
Enterprise CRM for client management, sales tracking, task assignment and analytics across divisions — React + Node.js/Express + PostgreSQL.
- Industry
- Diversified Enterprise
- Role
- Full-Stack Engineer
- Type
- Internal Tool
- Year
- 2024
01
Overview
Swalok Group CRM streamlines client interactions and sales operations across multiple divisions. Built with React, Node.js, Express and PostgreSQL, it features a dashboard of sales trends and metrics, a monthly reset for accurate tracking, task assignment with progress, and Excel import for bulk data.
02
Business challenge
Swalok Group ran client relationships and sales across five-plus business divisions on spreadsheets and email. Nobody had a single view of who owned an account, what stage a deal was at, or how a division was performing month over month — and historical numbers kept bleeding into the current period.
03
Solution
Built a division-aware CRM on React + Node.js/Express + PostgreSQL: client records scoped per division, sales activity with task assignment and progress tracking, an admin dashboard of trends and metrics, and a monthly reset so each period reports cleanly. Excel import moved years of existing records in bulk rather than by hand.
What it does
04
Architecture
How it fits together
- 01React SPA for the client, sales and task workspaces, with an admin dashboard aggregating cross-division metrics
- 02Node.js / Express REST API over PostgreSQL, with division as a first-class scoping dimension on client and sales records
- 03Monthly rollover routine that closes the reporting period so month-on-month figures stay comparable
- 04Excel import/export for bulk onboarding of existing client data and for finance-side reporting
05
Engineering challenges
- Challenge
- Divisions tracked the same customer differently, so cross-division reporting double-counted.
- How it was solved
- Made division an explicit dimension on every client and sales record rather than a free-text field, so a shared customer rolls up once at group level while each division keeps its own pipeline view.
- Challenge
- Running totals never reset, so current-month performance was buried in cumulative figures.
- How it was solved
- Added a monthly reset that snapshots and closes the period, keeping historical data intact while giving each month a clean baseline.
06
Technology stack
- Frontend
- React.js
- Backend
- Node.jsExpress.js
- Data
- PostgreSQL
- Infrastructure
- REST APIsExcel Integration
07
Business impact
- 5+
- Divisions
- Real-time
- Insights
- Enhanced
- Collaboration
Client interactions, sales activity and task ownership moved off spreadsheets into one system, giving the group real-time visibility per division and a reporting period that finally matches how the business actually reviews performance.
08
Project status
What I took from it
- Multi-division scoping is far cheaper to model on day one than to retrofit once records already exist.
- A bulk import path is what decides whether an internal tool actually gets adopted — teams will not re-key years of data.
Next step
Need a similar solution for your business?
Tell me what you are trying to build or fix. I will come back with how I would approach it, what it realistically takes and where the risks are.
