Back

BusinessPad

Making years of business logic easier to navigate.

A no-code ERP for managing interconnected operations across procurement, logistics, finance, projects and operations.

Company
AVK Consulting
Role
Senior Product Designer
Timeline
2023–2025
Type
Enterprise ERP · Desktop
BusinessPad August expense budget with the active process stage, counterparties, a goods table and filters for payment, status and products
A process instance with operational data, related records and filters in the same workspace.

01 What is BusinessPad

An ERP where companies build their own processes.

BusinessPad is a no-code ERP. Instead of fixed modules, a company describes how its work runs, and the system turns that into screens, tasks and data.

It is used across procurement, logistics, finance, projects and operations, often with several departments working inside the same process.

  1. 01

    Processes

    Procurement, payments or hiring are set up as business processes: stages, roles and the data each stage collects.

  2. 02

    Instances

    Each real request, like an August expense budget, runs as an instance of a process and moves from stage to stage.

  3. 03

    Tasks and people

    Work is assigned to people as tasks, with chats, notifications and documents around it.

02 How it works

A process is drawn, not coded.

Process owners lay out stages across swimlanes for each role, connect them, and configure each stage: who is responsible, how long it takes, which tasks and fields it has.

BusinessPad process canvas for «Согласование коммерческого договора»: swimlanes for department, lawyer and director, four stages with transitions, and a settings panel for the selected stage
  1. 01

    One process, four views

    Canvas, settings, roles, variables and fields.

  2. 02

    Swimlanes by role

    Department, lawyer, director.

  3. 03

    Stage

    Selected stage with a gateway.

  4. 04

    Stage settings

    Responsible, duration, tasks, fields and variables.

  5. 05

    Building blocks

    Processes, gateways, loops, events.

03 The challenge

Complex because the work is complex.

Processes run across departments, with many steps, approvals and large datasets. An action in one place can affect another part of the business.

Removing functionality would have made the product less useful. The goal was to make its complexity understandable.

04 My role

Senior Product Designer at AVK Consulting.

  • Mapping workflows with analysts and the product team before designing screens
  • Redesigning dense working screens: process instances, registries, tasks
  • Information hierarchy for tables, statuses, filters, forms and documents
  • Platform features such as reference data, chats, process variables, notifications and saved list views
  • Turning recurring solutions into reusable components in the BusinessPad design system
  • Mobile flows for the work people need away from a desk
BusinessPad tasks: Active, Drafts and Completed tabs, task cards for the designers group with status, deadline, people, documents and tags, and a week calendar
Tasks as a working list: status, people and timing visible without opening every record.

05 Approach

A few rules used across the product.

  1. 01

    Keep density, add structure

    Experienced users need the data. Grouping, spacing and hierarchy make it scannable.

  2. 02

    Panels beside the list

    Viewing, editing and settings open in a side panel, so context stays in view.

  3. 03

    One pattern, many places

    Lists, forms and empty states behave the same across the product.

  4. 04

    Design for none, one and many

    Every list and panel is checked with no items, one item and many.

06 System

Recurring solutions became components.

Tables, filters, forms, statuses, empty states and actions kept coming back. They were extracted into reusable components, which became the BusinessPad design system.

See the design system →

07 Selected UX cases

Closer looks at individual features.