Problem
A technology-support business needs more than service pages: customers need a structured way to request work and follow it, while staff and technicians need controlled workflows for intake, assignment, repair, quotation and updates.
Scope
The platform combines server-rendered public service and pricing pages with customer, staff and technician portals backed by a Node API and PostgreSQL data model.
Solution
Geek247 connects its service catalogue and booking requests to customer job histories and operational tools. Appointment requests remain subject to confirmation, estimates are not final repair quotes, and provider billing or email behavior depends on separately verified configuration.
Stack
- React and TypeScript
- Node.js and Express REST API
- PostgreSQL and Prisma
- Progressive web app
Platform features built
- Public catalogue, category and service pages, pricing, support plans, repair information and service-area guidance.
- Customer accounts with saved devices and locations, booking requests, job updates, repair progress, messages and protected attachments.
- Staff tools for search, assignment, status, priorities, repair intake, customer/internal messages and completion notes.
- Quotes with itemised amounts, VAT, deposits, expiry and customer approval; invoices with balances and payment histories.
- Technician assignment and work views, plus admin controls for services, pricing, availability, plans and staff accounts.
Implementation
- Replaced the legacy editorial website with a responsive, server-rendered public site and connected account application.
- Implemented customer-scoped records and role-restricted customer, staff and technician interfaces.
- Documented payment, email, scanning, legal and operational activation requirements separately from the delivered software scope.
No verified quantitative result is published for this case study.