Internal admin panels (custom builds)

Internal admin panels (custom builds) are internal tools for your team’s tasks: a panel where staff see and edit the data they need — orders, requests, clients, products, content — with access permissions, search, filters and one-click actions. We build it for your processes: which screens, which fields, which buttons and checks, integration with your database, API and services. The point is for routine operations to be done quickly and without errors, rather than through Excel exports, requests to a developer or edits straight in the database (which is dangerous). Unlike ready-made low-code builders (see the “Workflow tools implementation” service), on which a panel is assembled quickly and cheaply, custom development is needed when a standard builder hits a ceiling: complex logic, special security requirements, integrations that are not available out of the box, multiple data sources and a complex workflow between services, or a large volume of data. Importantly and honestly: if the task is simple (a few tables, basic CRUD), custom is overpaying — it is faster and cheaper to assemble it on Retool or a similar builder, and we will suggest that ourselves. Custom is justified where a builder cannot cope. Also honestly: this is an internal tool, not a public product — we optimize for function and reliability rather than marketing polish, for your own people; we deliberately save your budget on that. And about support: a custom panel is your code, which someone has to maintain and develop; we hand over documentation and can provide support, but it is worth keeping in mind from the start. Picture this: a manager processes a request in a couple of clicks in their panel — with all the checks, without the risk of breaking the database and without an email to a developer. The base price starts from 90,000 ₽; it depends on the number of screens, the logic and the integrations.

• The team edits data directly in the database or in the code — risky and not available to everyone.
• The engine’s default admin panel is inconvenient and not tailored to your processes.
• Routine goes through Excel exports and manual requests to a developer.
• There are no proper access permissions — either everything is allowed to everyone, or nothing to anyone.

• Screens for your entities: orders, clients, requests, products, content
• Viewing, search, filters, sorting and bulk actions
• Creating and editing with checks and validation
• Access permissions and roles (who sees and can change what)
• Integration with your database, API and external services
• One-click actions for your processes (statuses, mailings, export)
• An action log (who changed what and when)
• Documentation and handover for support

• Routine is done quickly and in a couple of clicks — without exports and emails to a developer
• Fewer errors and risks — checks instead of edits straight in the database
• Everyone sees and can do exactly what they need — proper permissions
• A tool for your processes, not processes for someone else’s admin panel

• We work through your processes and data, design the screens and permissions
• We assemble the panel, integrations, checks and actions
• We test on real tasks, hand over with documentation, and launch

• Why custom if there is Retool and other builders?

  Often there is no reason — and we will be the first to say so. For simple tasks a low-code builder (see the “Workflow tools implementation” service) is faster and cheaper. Custom is justified when a builder hits a ceiling: complex logic, strict security requirements, non-standard integrations or a large volume of data. First we will honestly assess whether a ready-made tool is enough.

• How much does it cost and why?

  As a guide: 3 screens, basic CRUD and one integration — from 90,000 ₽, about 3 weeks; the more complex the logic and integrations, the higher the budget and timeline. This is an internal tool, so we do not spend the budget on marketing design and animations — we make it convenient and reliable, and we deliberately do not build in extra beauty that does not speed up the work.

• Who will support the panel afterwards?

  It is your code, and its support is a separate question that is better settled at once. We hand over documentation and a clear structure, and can take on the support ourselves or hand it to your developers. The main thing is not to leave the tool without an owner, otherwise it will become outdated over time.