Portals & accounts: self-service instead of calls

Tick what you recognise

Five statements — and an honest verdict: do you need this service and which package to start with.

A client account with roles — switch the role

One portal, different roles: the client sees orders, the dealer sees prices and stock, the operator sees the request queue. Permissions are designed before code.

Not “a service” but concrete artefacts

What you hold at the end — we remove the fear of “paid and got nothing”.

Pick a package — the scope highlights

Greyed out — what is not in the package. Ranges are medians of our projects.

• Design — roles, scenarios, reference data, status models
• Catalogue & register — filters, moderation, change history
• Client accounts — client, partner, operator, administrator
• Documents — generation, signing, e-docs
• Gov integrations — Gosuslugi, SMEV, regional services
• Load — caching, queues, peak scenarios
• Admin panel — management without a developer
• Launch — register migration, operator training

Move the sliders — the range updates instantly

A benchmark based on medians of our projects. The exact estimate comes after the solution map.

Switch the scenario — we compare the alternatives

Sometimes the better deal is not ours — and we say so first.

What we do and what you get every week

Hover a point. Only artefacts, no “work in progress”.

What usually goes together