Reconstructed from the working system
Request board
A request lives on the board, not in the correspondence between the measurer and the manager.
CRM / ERP · Web applications · 2026
The public screens are reconstructed. Live orders, company amounts, and internal access are not shown.
Task
Build one place for the requests of a stretch-ceiling company, from the first call through the measure and the installation.
Starting problem
Requests, callbacks, and site visits were spread across people and cities. A city with in-house staff and a partner city handle money and responsibility differently, and one shared spreadsheet could not hold that.
What was examined
Roles, a city, a work status, and a separate money threshold are needed. The public card shows what the screen contains. It does not show client data.
How it is built
The working system is built with Next.js, Prisma, and PostgreSQL. This screen is a public reconstruction in the browser. It is not connected to that database. The columns repeat the board's stages.
What the interface shows
- The columns are named as jobs, not as an abstract sales pipeline.
- The city is visible in the header, so two systems are not mixed.
- Counters do not replace the list. A card can be opened from a column.
What the sample shows
The system is used in the company's work. What is shown here is the composition of the screen, drawn in this site's graphics, without amounts, without client names, and without internal access.
Modules of the same platform
- Cash desk and payments
Payment, the cash desk, and debt look at one request, not at three different spreadsheets.
- City sites
A person chooses a city and leaves a request, without entering the internal account.
- Field measure
On site, a person closes the job on the phone. The office sees the same status.
- Order account
The client needs the status of the order, not the company's whole board.
- Shift calendar
The shift is visible as a day: who is going out, who is calling back, and what is already closed.