Skip to content
AVERIQ
LanguageRUEN
Discuss a project

Reconstructed from the working system

City sites

A person chooses a city and leaves a request, without entering the internal account.

Websites · UI/UX · 2026

The public screens are reconstructed. Live orders, company amounts, and internal access are not shown.

Task

Make a clear site for the service across different cities, without a set of separate one-page sites that are not linked.

Starting problem

The same offer is needed in several cities, but the request has to land in its own city and in that city's way of working.

What was examined

On the site it is enough to explain the service, show the city, and accept a request. The account, the cash desk, and the board stay inside the CRM.

How it is built

The public pages are separate from the accounts. A request from the form creates a card in the system of the chosen city.

What the interface shows

  • The city is chosen in the open. It is not hidden in the footer.
  • There is one next step: leave a request for a measure.
  • Internal roles are not shown on the site.

Open the demonstration

What the sample shows

The public site opens at the company's address. The layout on this page is drawn in the portfolio's graphics. It does not copy the live pages pixel for pixel.

Modules of the same platform

  • Request board

    A request lives on the board, not in the correspondence between the measurer and the manager.

  • Cash desk and payments

    Payment, the cash desk, and debt look at one request, not at three different spreadsheets.

  • 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.