Request approvals

Requests go through approval under clear rules. The employee sees the status, the manager makes the decision and the assignee receives the task.

Who it is for

  • A team where purchases, expenses or other requests are approved over chat or email.

What the solution includes

  • Request creation with amount calculation
  • Manager queue with return and rejection
  • Assignee queue
  • Decision history

We adapt the design to your brand. The example illustrates a workflow, rather than a fixed visual style for your project.

Internal approval workflows are universal. The first package names Russian tools (Bitrix24, Yandex Tracker) as source examples; tool availability must be checked for each client, and other tools are not promised at this price.

Examples use fictional data. Integrations, payments and AI actions shown as simulations require separate implementation and testing.

Try the interactive example →

Development options

Pricing on request. We confirm the scope, schedule, currency and payment terms before starting.

Approvals on an off-the-shelf tool

Setup of the selected off-the-shelf service for one approval route.

Quote on request

1–2 weeks, subject to scope confirmation

  • One route of up to two stages, three roles and up to two subjects
  • Off-the-shelf service where no CRM exists yet: a suitable Bitrix24 or Yandex Tracker plan; alternative: a form, a spreadsheet and a Telegram bot
  • Up to 10 fields, decision by amount, reason for return/rejection and history using the platform's tools
  • Notifications in one channel; the responsible person places the purchase only after a decision
  • Up to 10 test requests, permission testing and instructions

Not included

  • Licences and subscriptions are paid separately. One implementation option, not all three at once.
  • Access levels, the log and blocked transitions are verified on the chosen plan.
  • Form + spreadsheet + bot suits a simple process; it does not replace a secure procurement system and does not block payments made outside the tool.
  • No custom app, custom design, 1C, EDI/electronic transport waybills, payments, electronic signature or migration of an old database.
  • If the off-the-shelf tool cannot provide the required permissions and blocked transitions, we choose another tool or estimate custom development separately.
Discuss this option →

One route in a CRM

One process runs in your existing system.

Quote on request

1–2 weeks, subject to scope confirmation

  • One request type
  • Up to 10 fields
  • Author, approver, assignee
  • One route with 2 stages after the author
  • Return/rejection/completion
  • Built-in permissions, history and notifications
  • Scenario testing
  • Training of up to 60 minutes

Not included

  • Purchase of the CRM and licences
  • Custom interface
  • Multiple routes
  • Data exchange with 1C

Ongoing costs

  • CRM/BPM on a plan with the required features
  • Apps if needed
Discuss this option →

Rules-based routes

Requests are routed by amount or type.

Quote on request

2–3 weeks, subject to scope confirmation

  • One request type with up to 15 fields
  • Up to 3 routes and 5 roles
  • Route selection by 2 conditions
  • Built-in substitution/escalation where the platform supports it
  • Delay report
  • Testing of permissions and history
  • Instructions and training

Not included

  • Custom process engine
  • Multiple accounting systems
  • EDI
  • A large number of different processes

Ongoing costs

  • CRM/BPM plan and supported apps
Discuss this option →

Standalone service

One bounded process runs independently of the CRM.

Quote on request

6–8 weeks, subject to scope confirmation

  • One request type with up to 12 fields
  • One route of 2 stages after the author
  • Up to 4 roles
  • Sign-in via an existing authentication provider
  • Queues and request cards
  • Decision history
  • Email notifications
  • User and reference list administration
  • Testing of access and repeated actions

Not included

  • Does not automatically include the three routes of the Rules-based routes package
  • Process builder
  • EDI and electronic signature
  • CRM/1C integrations
  • Inventory management

Ongoing costs

  • Hosting, authentication and email
Discuss this option →

Possible next steps

  • Multiple routes
  • Amount thresholds and delegation
  • Accounting system integration