Code outside the company's control and dependence on one person
Cravtt Property took over the project after parting ways with the previous contractor. The starting point carried serious operational risk.
Code outside the client's control
Part of the source code was not in repositories on the company's account — it existed only outside its infrastructure. A real risk of losing all that work for good.
Knowledge held by one person
With no documentation, no new developer could run the project on their own. A classic key-person risk — all the knowledge concentrated outside the organization.
Unknown project state
There was no reliable answer to the basic questions: how complete, how secure and how stable the project really was. Decisions were being made without data.
From scattered code to an organized, documented project
We split the work into four stages — from recovering the code to a report with a recommendation.
Code recovery & consolidation
We collected the complete source code from scattered sources and moved it into repositories on the client's account: backend, frontend and documentation, each separately.
Documentation & run setup
We added run instructions to every repository so any developer can spin up the whole project quickly. We ran the project locally and confirmed it works.
Technical audit
We analyzed security, stability and code quality, identifying the key risk categories — from input validation to monitoring and incident procedures.
Business audit & recommendation
We mapped the project's actual state against the specification and delivered a report with a clear, cost-estimated recommendation for next steps.
The main risk categories
The audit revealed systemic gaps typical of projects built without oversight or standards. We present them at the category level.
Security gaps
No input validation and no protection against the most common attacks, plus no procedures for a data breach (GDPR).
No observability
No tooling to monitor and control the application in production, and no procedures for outages or downtime.
Technical debt
Significant technical debt and instability, raising business risk and the cost of further development.
No documentation or reproducibility
No project documentation and no repeatable way to run it — onboarding anyone new was costly and risky.
Full control and a fact-based decision
Full control of the code
All source code now lives in repositories on the company's account. No more dependence on a single person or risk of losing the work.
A reproducible environment
Thanks to the documentation, any developer can run the project quickly — onboarding is no longer a bottleneck.
An objective picture
The client received a reliable, fact-based assessment of the project's technical and business state.
A data-driven decision
A clear, cost-estimated recommendation let them plan the product's future deliberately.
Instead of operating in the dark, the client gained an organized codebase in their own repositories and a reliable, fact-based picture of its state — the foundation for a deliberate decision about the product's future.
How we can help in a similar situation
Technology Audit
A full assessment of technical state, security and processes — with priorities and an action plan.
Technical Debt Reduction
Organizing the project and paying down technical debt so further development is faster and cheaper.
Technical Support
Stabilizing and maintaining the project after takeover — monitoring, procedures and ongoing support.
“For the first time we have full control of our own software and a clear picture of the real state of our project. That let us make a deliberate decision about its future.”Cravtt Property team
Inherited a project you don't control?
We'll recover and organize the code, document the project, and show you its real state. Let's start with a free consultation.
Book a diagnostic call