Corporate systems

CRM, ERP and internal systems. Customers, finances, requests and access in one place.

Discuss a system Modules

What we build the system from

The module scheme is an example. The set of modules and scenarios is assembled for the processes of a specific company.

Module 01

Customers

One customer card with the whole history: contacts, deals, contracts and communications in one place.

Customer cardHistorySegmentsSearch

Event log

TodayCustomer card created
TodayContract added
YesterdayManager assigned
A week agoFirst request

Module 02

Requests

Requests from every channel land in one queue; each has an owner and a status.

Request queueStatusesOwnersNotifications

Event log

10:24Request from the website form
10:31Owner assigned
12:05Status: in progress
16:40Request closed

Module 03

Finance

Invoices, payments and settlements linked to customers and deals, with export to accounting systems.

InvoicesPayments1C integrationYooKassa

Event log

TodayInvoice issued
TodayPayment via YooKassa
TodayExport to 1C
TomorrowReconciliation report

Module 04

Data and reports

Reports on key metrics are built from the live data of the system, with no manual spreadsheet work.

ReportsDashboardsExportReference data

Event log

MondayWeekly report
DailyDashboard update
On requestExport to Excel
MonthlyBranch summary

Module 05

Roles and access

Every employee sees and changes only what their work requires. Actions are recorded in a log.

RolesPermissionsBranchesAction log

Event log

09:00Administrator signed in
09:12Permissions granted to a manager
11:30Branch access
18:00Log entry

Module 06

Processes

The company's key processes become scenarios of the system: stages, checks and automatic actions.

StagesAutomationScheduleApprovals

Event log

Stage 1Request accepted
Stage 2Approval
Stage 3Automatic notification
Stage 4Done

When you need your own system

Processes have outgrown spreadsheets and off-the-shelf tools

Data is scattered

Customers, requests and finances live in different spreadsheets and services; the overall picture is assembled by hand.

Off-the-shelf doesn't fit

A ready-made CRM forces the business to adapt to it, and improvements hit the limits of the platform.

The system is outdated

The internal tool works but is hard to develop. We migrate to a modern stack without stopping the business.

Case

VirtuozyEducation

Three years developing the CRM of the Virtuozy music school chain

Every branch got a reactive real-time schedule and a set of useful business management modules.

Frontend stack migration to Vue.js
Modular system introduced
Reactive forms, recurring lessons

View case

Integrations

We connect the system to what already works

1CCRMYooKassaStripeDelivery servicesSMS gatewaysOther APIs

Stack

Technologies that can be developed long-term

Vue/NuxtReact/NextTypeScriptPython/Django/FastAPINestJSPostgreSQLRedisRabbitMQDockerNginxS3Grafana

F.A.Q

We already have a system, but the contractor disappeared. Will you take it over?

Yes. First we study the code and write down in a specification the rules the system follows today. Then we decide together what to improve and what to rewrite.

Can we start with a small part?

Yes, and most of the time that is the right way. We launch one scenario and expand once the first real users appear.

How much does it cost and how long does it take?

We give an estimate after the brief: the price and timeline depend on the number of roles, modules and integrations. The first stage is a clickable prototype — the scope is visible before development starts, and then we launch the system module by module.

5 more areasAll services

Let's discuss your project

We reply the same day. The first step is a 30-minute call or a brief in Telegram.

Discuss a project

push@wespot.ru @khudyakv