# Project takeover > Our project takeover service starts with a one-week review of software another team left unfinished. We tell you in writing what works, what is missing, and whether to continue or rewrite. Then we finish the work against a definition of done. - URL: https://radkod.com/en/services/project-takeover - Publisher: RadKod - Written by: Abdullah Bozdag - Published: 2026-07-28 ## In short - A takeover starts with a one-week review and a written status report. - First we gather every account and login into your name. - The remaining work gets a one-page quote and a new definition of done. - We only recommend a rewrite when it is really needed. ## Who is project takeover for? Project takeover is for companies whose software was left unfinished by another team. Typical clients lost touch with their developer, parted ways with an agency, or have heard "almost done" every month. Old systems that work but nobody dares to touch belong here too. ## What do we do? We review for one week, then we finish the work. The review starts with access. We find out whose name the domain, server, code repository, store and payment accounts are in, and show you how to move them to yours. Read why in [who should own your domain](/en/blog/who-should-own-your-domain). Then we read the code, run the software on a [staging environment](/en/glossary/staging-environment) and list what works and what is missing. We check security, backups and outdated components. The cost that hurried code leaves behind is called [technical debt](/en/glossary/technical-debt). The written report recommends one of three paths: continue with the existing code, fix it first, or rewrite. We only suggest a rewrite when continuing would cost more. The remaining work gets a new [definition of done](/en/blog/definition-of-done). With us there is no 90 percent. It is done or it is not. If you are also collecting quotes from other teams, [how to compare software quotes](/en/blog/compare-software-quotes) lists what to check. ## What the review covers - **Accounts and access**: Who holds the domain, server, repository and third-party accounts. - **Code reading**: Structure, technologies and whether the code can be maintained. - **Works and missing list**: Each feature marked as working or missing on a test setup. - **Security and backups**: Known issues, outdated components and whether backups really run. - **Written report**: Continue, fix or rewrite, with the reasons. ## How a takeover runs 1. **You write, we reply within a business day** — Day 0 you describe the situation. Day 1 we reply. Day 2 we talk for 30 minutes about what access you have. 2. **One-week review** — We gather access, read the code and run the software. At the end of the week you get the written report. 3. **One-page quote and definition of done** — Based on the report, you get a quote for the remaining work. Work starts once the definition of done is signed. 4. **Finish and test** — We close the gaps, fix the bugs and tick off every item. 5. **Launch and handover** — We launch on the promised date and hand over setup notes and every login. ## What happens after it is finished? We fix bugs for free for 30 days. This time everything is in your name and the setup notes are in your hands, so you do not end up in the same place again. Monthly [maintenance and support](/en/services/maintenance-and-support) is optional. If you want to leave, one email is enough. ## Frequently asked questions ### How long is the review? One week, ending with a written status report. ### What if the old team will not give us access? We help you prepare requests to the providers for the domain and accounts. If the code is missing, the report says so. ### Do you always recommend a rewrite? No. If continuing is cheaper, we recommend that. A rewrite is the last option. ### Do we have to continue with you after the review? No. The report is yours. You can continue with another team. ### What if it is built with a technology you do not know? We say so on the first call. If we cannot do the work well, we do not take it on. ### Does the system keep running during the takeover? Yes. The review runs on a copy, without touching the live system. Fixes are tested on a staging environment first, then released. ### What should we prepare for a takeover? List every login you have: domain, server, code repository, store and payment accounts. Contracts, quotes and emails with the old team help too. We find what is missing together during the review. ### How is the price of the remaining work set? By the review report. The list of gaps and the chosen path become a one-page quote. We do not price the remaining work before the report is done. ### Whose name will the code and accounts be in? Yours. The first job of the review is moving accounts that are not in your name to you. When the work is finished, domain, server, repository and every account are yours, with setup notes in hand. ### Do you offer support after the work is finished? Yes. We fix bugs for free for 30 days after delivery. After that, monthly maintenance is optional.