Professional services platform
Project & Client Management
React + Express + MongoDB system for clients, projects, tasks, time logs, invoices, templates, and Excel/PDF exports.
Background & Context
Folder project-managment (spelling) hosts a full-stack Project Management System for agency-style teams: JWT auth with admin | manager | employee roles; CRUD for clients, projects, and tasks; time logging that rolls into task actualHours; invoicing for managers; reusable project templates on the API; MUI dashboard with Recharts; Excel exports (and PDF projects export on API). Optional Nodemailer notifications and Socket.IO project-room emits ship on the server.
Canonical sources are backend/src/** and frontend/src/**. Honesty on wiring: Socket.IO client helper exists but pages do not subscribe; TimeTracker and FileUpload components are unused by pages; “Use template” UI toasts without calling POST /api/projects/from-template; comments API has no UI; invoice line items schema exists but UI edits amount/dates only; invoice email templates are unused.
The Challenge
Services firms tracked clients, projects, and billable time across chat, sheets, and email—invoicing lagged delivery, and managers lacked a live utilization view. Without a coherent professional services platform foundation, Project & Client Management stakeholders faced fragmented tools, slow handoffs, and limited visibility—classic failure modes Tekvers designs against.
The Solution
Tekvers delivered a MERN-style (React CRA + Express + MongoDB) delivery-ops app covering client → project → task → time → invoice, with role-based API authorization, dashboard/calendar/reports, and file exports. Tekvers delivered a maintainable professional services platform system for Project & Client Management using MongoDB, Express, React, Node.js, with phased rollout, operator workflows, and documentation suited to long-term ownership.
Our Approach
Role-scoped delivery loop
Employees see assigned projects/tasks and own time logs; managers/admins create projects/tasks/invoices; admin deactivates users and deletes clients/projects.
Operational analytics
Dashboard charts for project/task status, priority, and hours; react-big-calendar for due dates; Reports summary cards + Excel export buttons via `/api/exports`.
Side effects where configured
Time-log mutations maintain `actualHours`; project/task emails fire when SMTP is configured; Socket emits on project mutations (UI not consuming yet).
What We Delivered
- JWT auth (register/login/me) and user management with soft-deactivate
- Clients, projects, tasks CRUD with statuses/priorities/hours
- Time logs API + Time Logs page (timer component present but unwired)
- Invoices module (admin/manager) with INV- numbering
- Project templates CRUD + from-template API (UI not calling instantiate)
- Dashboard, calendar, reports; Excel exports; PDF projects export on API
- Multer uploads API; comments API (no UI); Socket.IO server rooms
- Documented gaps: payments, OAuth, live timer/file upload in pages, Socket consumers
Outcomes & Impact
- End-to-end delivery ops from client through invoice on one stack
- Distinct personas with API-enforced permissions
- Charting and exports without a separate BI tool
Internal teams replace spreadsheet chaos with a role-aware ops console—while portfolio copy stays precise about which extras are API-only or unwired.
Technology Stack
Services Delivered
Related Case Studies
Guides & articles from this niche
Planning a similar platform? Share your scope and we will map architecture, delivery phases, and a realistic timeline.