Full-Stack Developer Required to Build Multi-Tenant SaaS CRM & ERP Platform

**Project Type:** Development from Scratch
**Platform:** Web SaaS + Mobile PWA
**Engagement:** Fixed Price
**Budget:** Open to Proposals

### Project Overview

We are looking for an experienced full-stack developer or agency to design, develop, test, and deploy MYEVCRM, a complete cloud-based CRM, ERP, and business operations platform.

Initially, the software will support EV infrastructure companies managing EPC projects, charger installation, commissioning, AMC, field services, finance, procurement, inventory, workforce, and charger monitoring.

Our objective is to launch MYEVCRM commercially as a multi-tenant SaaS product with subscription plans, white-label branding, customizable modules, and secure independent client workspaces.

The software must be developed from scratch, with a modern, user-friendly interface and complete source-code ownership.

### 1. Multi-Tenant SaaS & White-Label

- Multiple independent companies with secure data isolation.
- SaaS Super Admin and Company Admin dashboards.
- Role-based permissions and multiple branches.
- Trial, monthly, and annual subscriptions.
- Module-based access and user licensing.
- Client-specific logos, themes, and login pages.
- Custom domains/subdomains.
- Configurable menus, forms, and dashboards.
- Branded documents and reports.
- Tenant onboarding, activation, suspension, and data export.

### 2. CRM & Sales Management

Lead management, customer records, sales pipeline, opportunities, follow-ups, quotations, proposals, contracts, sales orders, revenue forecasting, and sales dashboards. Leads must be convertible into projects or service contracts.

### 3. EV EPC Project Management

- Multi-client, multi-project, and multi-site management.
- Site surveys and readiness checklists.
- BOQ, costing, budgeting, and margin analysis.
- Vendor quotation comparison and work orders.
- Project schedules and milestones.
- Material planning and allocation.
- Installation and commissioning tracking.
- Daily Progress Reports (DPR).
- Site photos and quality inspections.
- Multi-level approvals.
- WCC, HOTO, and project closure.
- Project profitability and billing readiness.

### 4. AMC & Field Service Management

- Charger and equipment asset registration.
- Serial-number tracking and warranty management.
- AMC contracts and renewals.
- Preventive and breakdown maintenance.
- Service ticket management and assignment.
- SLA/TAT tracking and escalations.
- Technician scheduling and service checklists.
- Spare parts consumption.
- Fault history and Root Cause Analysis.
- Customer acknowledgement and ticket closure.
- AMC performance and profitability dashboards.

### 5. Workforce & Technician Management

The platform must manage four workforce categories:

1. Internal Team – Company employees.
2. Partner Internal Team – Partner company employees.
3. Freelance Technicians – Independent field technicians.
4. Local Vendors – Civil, electrical, and installation contractors.

Features include onboarding, skills, certifications, geographic coverage, availability, job allocation, attendance, GPS check-in where permitted, task progress, photo evidence, quality checks, performance ratings, rate cards, freelancer payments, vendor settlements, and category-specific permissions.

### 6. Procurement & Vendor Management

Vendor onboarding, RFQs, quotation comparison, purchase requisitions, POs, approval workflows, vendor rate cards, agreements, invoices, payment tracking, outstanding reports, and performance analysis.

### 7. Inventory & Asset Management

Material masters, warehouses, stock inward/outward, transfers, project allocation, technician stock, serial-number tracking, spare parts, defective materials, returns, reorder levels, stock valuation, and asset lifecycle management.

### 8. Finance & Commercial Management

Customer invoicing, vendor payables, receivables, payment tracking, GST invoice fields, project budgets, actual expenses, site-wise profitability, department P&L, gross margins, credit/debit notes, financial approvals, and outstanding dashboards.

### 9. EV Charger CMS Integration

This is an important module for charging infrastructure monitoring and profitability.

Required features:

- Charger registration and CMS integration.
- Live online/offline/charging/fault status.
- Charging session history.
- Electricity consumption in kWh.
- Charger utilization, uptime, and downtime.
- Charger fault monitoring and service ticket creation.
- Charging tariffs and revenue.
- Electricity purchase cost and operating expenses.
- Site-wise and charger-wise profitability.
- ROI and investment payback calculations.
- Client-specific monitoring dashboards.
- Daily, monthly, and yearly analytics.

Support compatible OCPP 1.6J/2.0.1 where feasible. Historical CSV/Excel imports must also be supported. Live and imported data must be clearly differentiated.

### 10. Third-Party Integrations

Future integration support for Tally, SAP, Zoho, Salesforce, other CRM/ERP platforms, accounting applications, and charger CMS.

Support CSV, Excel, and XML import/export.

Free APIs may be used when reliable and commercially permitted. Paid APIs or recurring third-party services require prior approval. All dependencies must be documented.

### 11. Customization & Automation

- No-code form and custom field builder.
- Configurable checklists and statuses.
- Approval workflow builder.
- Multi-level approvals.
- SLA and escalation automation.
- Notifications and reminders.
- Custom report builder.
- Configurable dashboards and widgets.

### 12. Documents & Reporting

Centralized document management with upload, preview, download, version history, permissions, and audit logs.

Dashboards for management, sales, EPC, AMC, workforce, finance, procurement, inventory, charger monitoring, consumption, revenue, and ROI.

Reports must support filters and Excel/CSV/PDF export.

### 13. Mobile PWA & Offline Features

The application must work on desktops, tablets, and mobile devices.

Field engineers, freelancers, and vendors should be able to view jobs, update progress, complete checklists, upload photos, record materials, submit reports, and capture customer acknowledgements.

Selected field workflows must support offline data capture with secure synchronization and conflict handling.

### 14. UI/UX Requirements

Clean, modern, fast, and intuitive interface. Simple navigation, minimum clicks, easy forms, clear status indicators, responsive dashboards, and role-specific screens.

UI/UX wireframes must be approved before development.

### 15. Technology & Security

Open to suitable technology recommendations.

Preferred options: React/Next.js, Laravel/Django/Node.js, PostgreSQL, Git, and cloud/VPS hosting.

Mandatory security includes tenant data isolation, role-based access, secure authentication, server-side authorization, audit trails, encrypted communication, secure uploads, automated backups, recovery testing, and protection against common vulnerabilities.

### 16. Development Milestones

Phase 1: Requirements, architecture, database, and UI/UX.

Phase 2: Multi-tenant SaaS foundation and permissions.

Phase 3: CRM and EPC management.

Phase 4: AMC, workforce, and vendor modules.

Phase 5: Procurement, inventory, and finance.

Phase 6: White-label, subscriptions, and automation.

Phase 7: Charger CMS, monitoring, and ROI analytics.

Phase 8: Testing, deployment, and training.

Phase 9: Complete source-code handover.

Development must follow approved milestones with working demonstrations and acceptance testing.

### 17. Mandatory Source Code Ownership

**Complete source-code and IP handover is non-negotiable.**

Developer must provide:

- Complete frontend and backend source code.
- Database schema and migrations.
- Git repository and commit history.
- UI/UX design files.
- Deployment scripts and configurations.
- Integration code and documentation.
- Technical and user manuals.
- Testing and backup procedures.
- Hosting and administrator access.
- Third-party license details.

Git repository and hosting should be under our ownership from Day 1.

All newly developed project-specific IP must be transferred under the agreement. We must be free to modify, maintain, and commercialize the product independently.

Final payment will depend on successful deployment, testing, and complete handover.

### 18. Testing & Support

Functional, integration, security, performance, permission, and tenant-isolation testing are mandatory.

Include a post-launch bug-fixing warranty and separate maintenance/support quotation.

### 19. Proposal Requirements

Please provide:

1. Similar SaaS/CRM/ERP project examples.
2. Recommended technology stack.
3. Multi-tenancy and white-label approach.
4. Experience with CMS/OCPP integration.
5. Development team details.
6. Timeline and milestone plan.
7. Module-wise fixed-price quotation.
8. Hosting and recurring cost estimates.
9. Testing and maintenance proposal.
10. Confirmation of complete source-code/IP handover.

We need a reliable developer or agency capable of delivering a production-ready commercial SaaS product, not just a prototype.

The detailed technical blueprint will be shared with shortlisted developers.

**Start your proposal with "MYEVCRM SAAS" and provide relevant project examples.**