Start with an audit
Not sure what exactly is broken? Describe the situation — I will find the cause, assess the risks and propose a safe plan. A convenient paid entry into a complex task.
What's included
- Project structure overview
- Logging and integrations check
- Search for duplicates and critical risks
- Problem map and priorities
- Fix plan and timeline estimate
Formats
How the audit works
-
1
Request and access
You describe what is broken. I reply with the minimum access I need — usually Bitrix24, the repository or staging. I do not ask for more than that, and I do not touch production data without agreeing it first.
-
2
Going through the project
I look at the code structure, change history, integration settings and logs. I specifically check what happens at the moment of failure, not just how the system looks from the outside.
-
3
Problem map
I record what is broken now, what will break as load grows, and what should be left alone. Every item gets a severity, not a blanket "needs a rewrite".
-
4
Plan and estimate
I set priorities, propose an order of work and estimate hours per item. You can see what pays off immediately and what can safely wait.
-
5
Walkthrough
We go through the document in writing or on a call. I answer questions and explain decisions without jargon where jargon adds nothing.
What you get
Problem map
Where the fault is, why it happens and what it costs if left as is.
Fix plan
A prioritised list of work with an hour estimate for each item.
Risk assessment
Which areas need care and what is dangerous to change on a live system.
What you can do yourselves
The items your own team can close without involving me.
What happens next
An audit does not commit you to working with me. The plan is written so any team can pick it up — including your in-house one. If we do continue together, the work runs on the usual terms: hourly or as a package.