"case_study": "ergonplus"
One platform, any vertical: multi-tenant field-service SaaS
Task and workforce management generalized across industries — auto repair, accounting, construction — shipped as a web dashboard, an API, and a native mobile app.
"role"
Full-stack development — Next.js dashboard, Express + Prisma API, React Native app
"stack": [7]
- Next.js
- React Native
- Express.js
- Prisma
- PostgreSQL
- Socket.IO
- Firebase
The problem
Field-service businesses differ in vocabulary but not in shape: work comes in, someone does it, someone approves the cost, someone gets paid. Most software picks one vertical and hard-codes it. ErgonPlus inverts that — one platform where an auto-repair shop, an accounting firm, and a construction crew each configure their own workspace.
Its sibling product ErgonPro is a hotel-maintenance system with fourteen specialized roles. ErgonPlus is the generalization of that lesson: instead of fourteen hard-coded roles, three generic ones — admin, staff, client — plus templates that carry the vertical-specific logic.
What was built
- Multi-tenant workspaces: an instance type (the vertical) contains sub-instance workspaces that members join via invite codes or QR scan.
- Templated task workflows — each template defines required fields, documents, and workflow states, with line items that go through cost approval.
- Payroll entries linked one-to-one to completed tasks, so paying staff falls out of the work itself.
- Fleet management (vehicles attach to tasks), shared calendars, file management, and configurable custom sections per workspace.
- Real-time chat and notifications over Socket.IO, push via Firebase, in English and Greek.
Architecture decisions
- Tenancy lives in the data model, not in deployment: every query is scoped by workspace membership, which keeps operations simple — one database, one API.
- Task templates are data, not code. Adding a new vertical means seeding a template, not shipping a release.
- The web dashboard, mobile app, and API share one Prisma/PostgreSQL schema, so a task accepted on mobile is instantly consistent with the web dashboard and the payroll ledger.
- QR invite-code onboarding removes the account-setup friction that kills adoption with non-technical field staff.