Project overview
A telecom manufacturing operation needed software that understood items, orders and customers — not another generic CRM with a phone plugin.
Business challenge
VoIP engineers who only ship PBXs look narrow. This project is the counter-example: business software with the same discipline as a control plane.
Solution architecture
NestJS services and PostgreSQL for the domain. Redis for session and hot reads. Next.js for operations screens. APIs so warehouse, sales and finance do not share a spreadsheet.
Bounded services around inventory, orders, parties and reports. UI never writes around the API.
Technology stack
Key features
Inventory & products
Stock and catalogue as data, not tabs.
Orders
Status that finance and ops can both trust.
Customers / accounts
One party model.
Reports
Operational views without a BI project.
My role
Implementation
Resume-documented stack (Next.js, NestJS, Redis, PostgreSQL). Client identity omitted.
Results / capabilities
- Web ERP instead of desktop + sheets
- API-stable domain
- Same engineering bar as the PBX work
Building something in this class?
Share the workflow, current stack and constraints. The first reply is an architecture-minded review.
Discuss Your Project