Multi-Tenant Customer Support & Service Management ERP (Web + Mobile)
Budget: ₹75,000 – ₹150,000 INR
I need a working MVP ERP platform that allows organisations to manage sales quotations, installation requests, service complaints, engineer assignments, and preventive maintenance operations from one centralised system.
The system should be built as a multi-tenant SaaS platform, where each company can access its own environment through a dedicated subdomain.
Example:
companyA.platform.com
companyB.platform.com
companyC.platform.com
Each tenant must have isolated users and data, while the platform owner manages tenants centrally.
The system should have a modern and minimal UI, clean dashboards, and be mobile-friendly so both administrators and field engineers can use it easily.
A mobile app for engineers will allow field teams to receive requests, update complaint status, and submit service reports directly from customer locations.
Core Flow
1. Sales users create customer quotations and sales orders.
2. Once orders are confirmed, the system automatically generates installation requests.
3. Service backend assigns engineers to installation or service requests.
4. Engineers handle installations or complaints using the mobile application.
5. Engineers update service status and submit call closure reports.
6. Managers review service closure and track reports and PM schedules.
These workflows follow the sales → installation → service → reporting lifecycle.
Technology Preference
Implementation should use modern scalable technologies, such as:
Backend
• Laravel / Node.js / NestJS / Django
Frontend
• React / Next.js / Vue
Mobile Apps
• Flutter or React Native (single codebase preferred)
Database
• PostgreSQL or MySQL
Infrastructure
• Cloud hosting (AWS / DigitalOcean / similar)
• Docker-based deployment preferred
Project Scope (Phase-1 MVP)
Sales Module
• Create and manage sales quotations
• Update quotation status (Under Process / Order Received / Order Lost)
• View quotation history
• Generate quotation PDF
• Customer database management
The system should allow adding products, quantity, price, tax, and automatically calculate totals.
Installation Requests
Once an order is confirmed:
• Generate installation request automatically
• View installation request history
• Track installation status
• Assign installation to service team
Installation requests should include customer details, product information, and warranty details.
Service Backend
Service team should be able to:
• View all installation requests
• Approve or reject service requests
• Assign engineers to installations
• Track service progress
Managers should have a centralized service backend dashboard.
Complaint Management
Customers or service team can log complaints using:
• Product serial number
• Order number
• Customer name
Features:
• Log new service complaint
• Assign complaint to engineer
• Reassign complaints
• Track complaint status
Complaint types may include:
• Breakdown
• Preventive maintenance
• Reinstallation
• Other service calls
Engineer Mobile Application
Engineers should be able to use a mobile app to:
• Login securely
• View assigned installations or complaints
• Update service status
• Submit service reports
• Capture service details during visits
Engineers should also be able to submit call closure information after completing work.
Preventive Maintenance (PM Schedule)
The system should support:
• PM schedule management
• Download PM schedule reports
• Track planned maintenance visits
PM calendars should be generated based on installation data and service commitments.
Reports
Admin users should be able to download reports such as:
• Sales reports
• Installation reports
• Complaint history
• Engineer call reports
• Response time / TAT reports
Reports should allow filtering by:
• Date range
• Product serial number
• Customer
• Service category
User Roles
High-level roles for the system:
• Super Admin – manages tenants and platform configuration
• Sales Users – manage quotations and customer orders
• Service Team / Managers – assign engineers and monitor service requests
• Engineers – manage installations and service calls through mobile app
SaaS Tenant Billing & Payment Gateway
Since this is a multi-tenant SaaS platform, tenants should be able to subscribe and pay for using the system.
Required functionality:
• Tenant subscription plans (Basic / Standard / Enterprise – flexible structure)
• Payment gateway integration for subscription billing
• Automatic tenant activation after successful payment
• Subscription renewal reminders
• Tenant suspension if subscription expires
Payment Gateway Preferred:
• Razorpay
or
• Stripe
Features required:
• Secure subscription payments
• Invoice generation for tenants
• Payment status tracking
• Webhook-based subscription updates
Deliverables
• Fully functional multi-tenant ERP web platform
• Mobile application for engineers
• Backend API system
• Database schema and architecture
• Deployment on my cloud server with SSL
• Basic documentation and environment setup
• One short hand-off session explaining system usage
Goal
The goal is to launch a working MVP customer support and service management ERP platform that connects sales, installation, service operations, and field engineers in one system.
If you already have ERP or SaaS boilerplates that can accelerate development while maintaining quality, that is welcome.
My priority is fast MVP delivery with a scalable architecture so the system can grow into a full production platform.
The system should be built as a multi-tenant SaaS platform, where each company can access its own environment through a dedicated subdomain.
Example:
companyA.platform.com
companyB.platform.com
companyC.platform.com
Each tenant must have isolated users and data, while the platform owner manages tenants centrally.
The system should have a modern and minimal UI, clean dashboards, and be mobile-friendly so both administrators and field engineers can use it easily.
A mobile app for engineers will allow field teams to receive requests, update complaint status, and submit service reports directly from customer locations.
Core Flow
1. Sales users create customer quotations and sales orders.
2. Once orders are confirmed, the system automatically generates installation requests.
3. Service backend assigns engineers to installation or service requests.
4. Engineers handle installations or complaints using the mobile application.
5. Engineers update service status and submit call closure reports.
6. Managers review service closure and track reports and PM schedules.
These workflows follow the sales → installation → service → reporting lifecycle.
Technology Preference
Implementation should use modern scalable technologies, such as:
Backend
• Laravel / Node.js / NestJS / Django
Frontend
• React / Next.js / Vue
Mobile Apps
• Flutter or React Native (single codebase preferred)
Database
• PostgreSQL or MySQL
Infrastructure
• Cloud hosting (AWS / DigitalOcean / similar)
• Docker-based deployment preferred
Project Scope (Phase-1 MVP)
Sales Module
• Create and manage sales quotations
• Update quotation status (Under Process / Order Received / Order Lost)
• View quotation history
• Generate quotation PDF
• Customer database management
The system should allow adding products, quantity, price, tax, and automatically calculate totals.
Installation Requests
Once an order is confirmed:
• Generate installation request automatically
• View installation request history
• Track installation status
• Assign installation to service team
Installation requests should include customer details, product information, and warranty details.
Service Backend
Service team should be able to:
• View all installation requests
• Approve or reject service requests
• Assign engineers to installations
• Track service progress
Managers should have a centralized service backend dashboard.
Complaint Management
Customers or service team can log complaints using:
• Product serial number
• Order number
• Customer name
Features:
• Log new service complaint
• Assign complaint to engineer
• Reassign complaints
• Track complaint status
Complaint types may include:
• Breakdown
• Preventive maintenance
• Reinstallation
• Other service calls
Engineer Mobile Application
Engineers should be able to use a mobile app to:
• Login securely
• View assigned installations or complaints
• Update service status
• Submit service reports
• Capture service details during visits
Engineers should also be able to submit call closure information after completing work.
Preventive Maintenance (PM Schedule)
The system should support:
• PM schedule management
• Download PM schedule reports
• Track planned maintenance visits
PM calendars should be generated based on installation data and service commitments.
Reports
Admin users should be able to download reports such as:
• Sales reports
• Installation reports
• Complaint history
• Engineer call reports
• Response time / TAT reports
Reports should allow filtering by:
• Date range
• Product serial number
• Customer
• Service category
User Roles
High-level roles for the system:
• Super Admin – manages tenants and platform configuration
• Sales Users – manage quotations and customer orders
• Service Team / Managers – assign engineers and monitor service requests
• Engineers – manage installations and service calls through mobile app
SaaS Tenant Billing & Payment Gateway
Since this is a multi-tenant SaaS platform, tenants should be able to subscribe and pay for using the system.
Required functionality:
• Tenant subscription plans (Basic / Standard / Enterprise – flexible structure)
• Payment gateway integration for subscription billing
• Automatic tenant activation after successful payment
• Subscription renewal reminders
• Tenant suspension if subscription expires
Payment Gateway Preferred:
• Razorpay
or
• Stripe
Features required:
• Secure subscription payments
• Invoice generation for tenants
• Payment status tracking
• Webhook-based subscription updates
Deliverables
• Fully functional multi-tenant ERP web platform
• Mobile application for engineers
• Backend API system
• Database schema and architecture
• Deployment on my cloud server with SSL
• Basic documentation and environment setup
• One short hand-off session explaining system usage
Goal
The goal is to launch a working MVP customer support and service management ERP platform that connects sales, installation, service operations, and field engineers in one system.
If you already have ERP or SaaS boilerplates that can accelerate development while maintaining quality, that is welcome.
My priority is fast MVP delivery with a scalable architecture so the system can grow into a full production platform.