Support and scaling
We join existing products and work with someone else's code. We optimise performance and move legacy to a new stack.
What's included
[Scope of the service: which tasks we solve and what the work includes]
Cases
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.
Calculators and services for an insurance company
As part of support we improved the website and systems: the insured-event form and the policy issuing flow.
How we work
We were doing custom development long before neural networks, and the process took shape back then. AI helps us ship and maintain the product faster. Stability and security are still on us.
Brief and estimate
01We discuss the task and estimate it. Then we write a specification: features, technical decisions, roles, rules and edge cases. We develop against it (SDD) and accept the result against it too.
Clickable prototype
02We build a prototype from your design or with neural networks. The scenarios can be walked through by hand before the main development starts.
Development and integration
03After the prototype demo we adjust the specification. Simple code is written with Codex and Claude Code: routine work goes faster and the budget goes further. We know where AI can go wrong, so every change is checked by a developer in code review. We connect the product to your systems and external services: CRM, payments and others. Everything built during the stage is available in the demo environment at the project link.
Testing and release
04Once the functionality is ready, we cover it with tests and prepare the launch on a staging environment: a copy of the production environment where the product is checked in real conditions. After the final testing we move it to production and set up monitoring.
You always know what is going on
Reports
Every 1–2 weeks we send a report: what was done, what we take on next and where an overrun is possible if the tasks change. You learn about extra costs before they happen, not after.
Demo link
The current version of the product is always open. Come in at any moment, try everything and send the link to colleagues.
Direct line to the team
A shared chat with the developers, no chain of managers. Questions are answered by the people who write the code.
F.A.Q
Ask your questionWe 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, integrations and scenarios. To make the scope clear earlier, the first stage is a clickable prototype — you can walk through it before the main development and adjust the specification.
How does the work go?
Four stages: brief and estimate, clickable prototype, development with integrations, testing and release. At the first stage we write a specification — roles, rules and edge cases — and develop against it. Before launch we test in a staging environment and connect monitoring.
How do you use AI, and will quality suffer?
AI writes boilerplate code and speeds up routine work, but every change goes through code review and tests. We know where neural networks make mistakes, so business logic and integrations are checked by hand. The code lives in git and is backed up.
Do you integrate with 1C, payments and external services?
Yes. Customer accounts and CRMs are usually connected to 1C, payment acquiring, telephony and analytics: we sync data both ways and fix the exchange rules in the specification. An example is the Luzhniki Tennis Club account with 1C:Fitness, payments and membership.
What happens to the project after launch?
We stay on for support and development: we watch the monitoring, ship improvements and scale for growing load. The stack is proven and the code is documented — a new team can join the project easily if needed.
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