I am Alexey Kuznetsov, Tkan Studio. On a brief I often hear: “we want an app, like the banks have.” Then it turns out: the client calls to ask “where is the order”, files bounce around WhatsApp, and a repeat booking starts from zero again. That is not a request for an app store. It is a request for a process with a login.
At Tkan Studio a client cabinet is a web app: who signs in, what they see, what they change. It extends the site and the service. Separately — landing, multipage and cabinet as three purchases: the breakdown is in order a website in 2026.
A cabinet does not replace the offer. If the page does not make clear what you sell, a login will not save it.
Too early: no process — no cabinet
It is too early if a form and a call are enough. One service; ads are not running yet or have just started. Status lives in the admin’s head. Files do not pile up. A return visit to the site is rare.
At this level digitalisation looks dull and correct: a page, an enquiry, a person on the other end. Budget cue — 29 / 49 / 99 thousand, not “a cabinet for growth”. Which package — three questions about how you sell today.
A bad reason to order a cabinet: “the competitor has a login.” The competitor may have a queue and roles. You may have a shared chat. Login on top of chaos becomes a pretty messenger with a password.
When it is time: returns, files, a queue without a call
It is time to talk about a cabinet when work stalls without a return login. Typical signals in a service business:
- Statuses. The client asks which stage: “diagnosis / parts / ready”, “quote approved / in progress”, “booking confirmed”.
- Files. Acts, quotes, before/after photos, certificates — the same files bounce in chat.
- Return visits. Booking, slots, history, a diary — without “leave your phone again”.
- A queue already exists. The lead has an owner and a next step. The cabinet sits on top, not instead.
If leads are still lost between people — first a site for processes from 179,000 ₽: pages, queue, roles. A cabinet usually comes after process readiness, not instead of it.
Decision tree in short
- Early. One offer, form, call. No returns. → 29 / 49 / 99.
- Not yet. Clients ask for status, but steps are unnamed or leads get lost. → process from 179, then cabinet.
- Time. Steps exist; you need statuses, files or slots without a call. → client cabinet by brief.
Service scope and login scenarios — on the applications / client cabinet page. The purchase shape “landing · multipage · cabinet” — again in order a website in 2026.
FAQ
Is a client cabinet an App Store app?
No. For us a cabinet is a web app: login, statuses, files, slots. An extension of the site and the process — not a separate product in an app store.
When is a cabinet too early?
When a form and a call are enough: the offer is raw, there are no statuses, no return visits. Page and enquiry first — packages 29 / 49 / 99.
What if clients already ask for status but there is no process?
Name the steps and build a queue first — a site for processes from 179,000 ₽. A cabinet on top of chaos becomes a pretty chat.
How much does a client cabinet cost?
Quote by brief: who logs in, what they see, what they change. The figures 29 / 49 / 99 / 179 cover the shopfront and process; a cabinet usually comes after process readiness.