Legacy audit: find the cause, not treat the symptom
When the project already works but breaks, there is no documentation, and rewriting everything from scratch is risky — I first find the cause, then propose a safe plan.
When you need it
What's included
How I work
- 1Minimal access
- 2Analysis of code and processes
- 3Recording risks and entry points
- 4Problem map and priorities
- 5Plan of safe fixes
How I assess project risk
- There are logs
- There is a test environment
- Entry points are clear
- There is code access
- No documentation
- Few logs
- Some processes on old cron/agents
- There are manual workarounds
- Production without backups
- No logs
- Hidden business logic
- Code changed by many people
- Unclear which data is critical
What the client gets
- A clear problem map
- Priorities and a plan
- Timeline estimate
- Recommendations on logs and architecture
- Understanding of what can be left as is
Risks and limits
- I do not touch production blindly
- I make a backup when there is a risk of data loss
- A full architecture rework — as a separate estimate
Approximate work formats
If the project is old, without logs or documentation, with unknown integrations or production risks — an audit comes first. Otherwise any exact estimate is just guessing.
What I will need to work
- Minimal access to the system: Bitrix24 / repository / staging
- Access to logs if the task is about errors
- Description of the business scenario and expected result
- For integrations: API docs, test keys, payload examples
How I handle access
- I do not ask for excessive rights
- Tokens and keys are never sent to public chats
- For production changes — a separate user and a backup when there is risk
- After completion access can be revoked
Related cases
Audit and stabilization of a legacy project
The team got a clear problem map and could fix the project in stages, without a risky rewrite from scratch.
Learn more →CRM and lead/visit duplicates
Managers stopped reconciling visits manually, the database was cleaned of duplicates.
Learn more →FAQ
Can it be reworked without a full rewrite?
Yes, if the architecture allows. I first record risks and entry points.
What is needed for the audit?
Access to the code/test environment, a problem description and logs if available.
Will you name the fix price right away?
After the audit: without understanding the project's state an exact price is impossible.
Not sure where to start?
Just describe the problem. I will study the current solution, assess the risks and propose implementation options.