Process modelling
We map the as-is process, remove redundant steps and design the target model before automating.
Process automation
We turn manual processes into managed digital scenarios — with roles, rules, SLA and analytics.
Scope
What is included
Routes & approvals
We set up routes, roles and stages: who drafts, who approves, who signs and tracks the deadline.
Rules, exceptions & SLA
Business rules, exception handling and deadlines (SLA) run the same way every time.
Integrations & data
The process pulls data from registries and systems with no double entry or manual spreadsheets.
Monitoring & analytics
The status of each step, bottlenecks and execution metrics are visible on a dashboard, not in email.
Low-code scenarios
A change of regulation is a setting on the platform, not a new build and release every time.
Why automation
The process depends on people remembering itSteps, exceptions, deadlines and owners live in messages or people’s heads, so the result is hard to reproduce consistently.
Statuses are collected manuallyTo understand where a task is, people call, search emails, open spreadsheets or wait for a weekly report.
Rules are applied unevenlySimilar cases move differently depending on department, performer, urgency or informal agreements.
Data diverges between systemsThe process runs across several systems without aligned directories, statuses, events and responsibility.
Stages and outcomes
As-is description
We capture the current process, roles, documents, systems, manual operations and points where control is lost. Output — an as-is process map with bottlenecks.
Target model
We design the to-be scenario: route, roles, rules, data, exceptions, SLA and metrics. Output — a to-be process map and control points.
Delivery model
We define what is covered by a UnityBase product, what by Scriptum and what needs a custom module. Output — a platform decision and scope of work.
Scenario build
We configure forms, registers, routes, tasks, rules, notifications and cabinets. Output — a working digital scenario with logs and access rights.
Integrations and data
We connect APIs, directories, document management, digital signatures, registers, accounting and HR systems. Output — an integrated environment with no duplicate data entry.
Pilot and evolution
We launch a pilot, train users and measure the effect. Output — metrics, regulations, trained users and a support model.
Biggest impact
Administrative processes
Requests, approvals, assignments, execution control, service scenarios and internal regulations.
Document-oriented processes
Drafting, approval, signing, archiving and external document exchange through Megapolis.DocNet.
Finance, procurement, contracts
Budget requests, contracts, invoices, acts, limits control, approvals and accounting integration.
HR and personnel scenarios
HR documents, vacations, orders, approvals, organisational structure, payroll and HR processes.
Requests and services
Incoming requests, accounts, queues, SLA, routing, notifications and response quality control.
Process analytics
Dashboards for managers: deadlines, workload, bottlenecks, rework, errors and execution quality.
why us
Why IQusion
Typical contractor
RiskAutomating chaosA broken process is simply digitised — and breaks even faster.
Rigid “concrete”Any change of regulation requires a rewrite and a new release.
No visibilityIt’s unclear where the process is stuck and who owns a step.
No metricsProcess efficiency cannot be measured or improved.
IQusion
RecommendedModel firstWe describe and optimise the process before automating, not “as is”.
Flexible routesA change of regulation is a configuration, not a new build every time.
Process transparencyStatus, owner and bottlenecks are visible at every step.
Data-driven controlExecution metrics give grounds for optimisation sprints.
FAQ
Frequently asked questions
No. First we describe and optimise the process, remove redundant steps — and only then automate. Automating chaos only speeds chaos up.
Routes and rules live in configuration: a typical regulation change is a setting, not a new build and release.
Every step has a status, owner and execution time; bottlenecks show on a dashboard, not in email threads.
Yes. We recommend a pilot on one representative process so you see the result before scaling across the agency.
experience
Scenarios from our practice
Anonymised examples: what held the customer back, what we changed and the outcome. We do not tie them to specific clients due to NDA.
Processes lived in heads
Problem
Business processes weren't formalised, ran differently each time, without control.
What we did
Modelled the processes and set up routes, approvals and rules.
Result
Processes run uniformly and under control.
Approvals without deadlines
Problem
Approvals dragged on and nobody saw where they got stuck.
What we did
Added SLAs, deadline control and exception handling to the processes.
Result
Deadlines are under control and bottlenecks are visible at once.
Changes needed releases
Problem
Any process change required a long development cycle.
What we did
Moved the processes to low-code scenarios with visual configuration.
Result
Changes are made fast, without heavy releases.
Related news
See all →
Process Automation
15.06.2026 · 6 min
Process Automation
14.05.2026 · 4 min
Process Automation
09.04.2026 · 6 min
Let’s discuss the task
Describe the task — we’ll propose an approach, integrations and timing. Need technical support?
Contact us →