01
System map
CMS/framework, database, order flow, admin area, payment systems, email, CRM, analytics, cron jobs and external APIs.
Kintsugi Kode by Hlinor
Legacy system audit in 72 hours.
We analyze your old website, CRM or backend and deliver a clear system map, risk report, technical debt review and modernization plan — before you commit to fixes, migration or a rewrite.
Read-only first audit. We do not change the live system during discovery.
Your system works — but every change feels dangerous.
That is usually not a code problem only. It is a visibility problem. The business depends on a system that lacks documentation, ownership and a safe modernization path.
Common triggers
- The original developer left.
- The CMS, CRM or backend is old and undocumented.
- Payments, forms, analytics or integrations are fragile.
- You want to migrate, but do not know what may break.
- Agencies or developers refuse to touch the project without discovery.
What you get
A practical audit package for owners, managers and technical teams. Not a vague opinion. Not a blind rewrite proposal.
02
Risk register
Security, backup, dependency, hosting, access, stability and maintenance risks ranked by business impact.
03
Technical debt review
Where the system is hard to maintain: custom code, outdated versions, duplicated logic, fragile integrations and missing documentation.
04
Quick wins
Concrete improvements that can reduce risk quickly: backups, logs, monitoring, cleanup, tracking, access control and documentation.
05
Modernization plan
A 30/60/90-day roadmap: stabilize first, document the core, then migrate or refactor only where it makes sense.
06
Owner summary
A non-technical summary that explains what is safe, what is risky and what should be done first.
Best fit
- Old e-commerce websites
- MODX, Bitrix, WooCommerce, OpenCart and custom PHP stores
- Small manufacturing companies with old websites and CRM workflows
- Agencies inheriting client projects from another developer
- Companies preparing for migration to a modern stack
Not a fit
- Full penetration testing or legal compliance certification
- Emergency production changes without discovery
- Projects where no safe read-only access or archive can be provided
- Requests to bypass access controls or review third-party code without permission
How the 72-hour audit works
The first version is deliberately simple: structured discovery, AI-assisted analysis and human-reviewed reporting.
Intake and access scope
You describe the system, the business problem and what you can safely share: archive, repository, screenshots, hosting details or documentation.
System discovery
We identify the stack, structure, modules, data flow, integrations, entry points, scripts and operational dependencies.
Risk and debt analysis
We review outdated components, fragile integrations, missing controls, undocumented logic and high-impact failure points.
Report and roadmap
You receive a system map, risk register, technical debt notes, quick wins and a practical modernization plan.
Case study
MODX e-commerce audit: 3 critical risks closed in one day.
The store worked and generated revenue. The audit found unsupported PHP, public server logs, broken cron jobs and exposed CMS files.
Before you rewrite it, understand it.
Send a short description of your old website, CRM or backend. We will review whether Kintsugi Kode is the right first step.