Workflow tools

Workflow tools are internal tools for your team, built on low-code platforms (Retool, Budibase, Appsmith): panels for working with data, forms, dashboards, workflows and action buttons. We connect your sources (a database, API, spreadsheets, services), assemble the screens, set up permissions and logic — but we do not write everything from scratch, we use the builder’s ready-made blocks, so it comes out faster and cheaper than custom. The point is to cover the team’s routine without long development: approvals, processing requests, exports, simple data operations. Unlike custom panels (see the “Internal admin panels (custom builds)” service), which are written for you from scratch and are needed when a builder hits a ceiling, low-code is about speed and budget on standard tasks. Importantly and honestly: low-code comes with clear limits. When you need complex logic, a special interface, high security requirements, a large volume of data, platform limits on load and API traffic, or integrations that are not available out of the box — the platform starts imposing constraints, and then it is more honest to move to custom; we will say so directly rather than stretching Retool over what it cannot handle. Also honestly about money and dependence: the platform itself costs separately (Retool, for example, has a per-user subscription), and your tool lives inside it — that is convenient but creates vendor lock-in: moving to your own solution later will not be free. We will discuss in advance where this is acceptable and where it is better to go custom right away. And about the amount of work without illusions: low-code is fast, but it is not a one-click solution: connecting the data, assembling the screens and permissions is still work, just shorter. Picture this: in a week or two the team gets a working panel for requests instead of months of development and Excel spreadsheets. The base price starts from 50,000 ₽: this is a guide for a couple of sources, 2-3 screens and basic roles; the more complex the logic, integrations and approvals, the higher the budget and timeline. It depends on the number of screens, data sources and logic.

• The team needs an internal tool quickly, while custom development is long and expensive.
• Routine (requests, approvals, exports) hangs on Excel and manual operations.
• Developers are busy with the product, and there are not enough hands for internal panels.
• You tried to build it yourself on a builder but got tangled in the data, permissions and logic.

• Choosing a platform for the task (Retool, Budibase, Appsmith or a similar one)
• Connecting sources: a database, API, spreadsheets, external services
• Screens, forms and dashboards for your processes
• Action buttons and simple workflows (statuses, approvals)
• Access permissions and roles for the team
• Basic checks and input validation
• Team training on working with the tool
• An honest assessment of where low-code is enough and where custom is needed

• A working tool in weeks, not months — quickly and inexpensively
• Routine moves out of Excel into a proper panel
• The team does not wait for developers for internal tasks
• It is clear how far low-code is enough and when to move to custom

• We work through the task and data, choose the platform, assess low-code vs custom
• We connect the sources, assemble the screens, permissions and actions
• We test, train the team, and launch

• How is this different from a custom panel?

  A custom panel (see the “Internal admin panels (custom builds)” service) is written for you from scratch — that is more expensive and longer, but without the builder’s limits. Low-code is assembled from ready-made blocks on a platform like Retool — faster and cheaper, but within what the platform can do. For standard tasks we take low-code, for complex ones — custom; we will honestly advise what suits you. A rule of thumb: if there is little data, the logic is simple and rarely changes — go low-code; if the volume is large, the chains are complex and change often — that is already a job for custom.

• What is this platform lock-in and subscription?

  The tool lives inside a platform (for example, Retool) that has its own subscription — usually per user, and that is a separate cost from our work. The plus is speed and convenience; the minus is dependence: moving the tool to your own solution later will not be free. We will honestly flag in advance where low-code is justified and where it is better to invest in custom right away.

• Low-code is just “build it with a mouse”, so why you?

  You can build it with a mouse, but in practice it is easy to get stuck: connecting data, permissions, logic, checks and tidy screens take experience, otherwise the tool comes out leaky or inconvenient. We do it quickly and correctly the first time, and show the team how to work with it right away.