How to Take Over an Unfinished Web Project
Quick answer: Yes, many unfinished web projects can be taken over by a new developer, but the first step is getting access to everything and having the work reviewed before anyone promises a price. A review decides whether the project can be saved, and no honest developer can tell you that without looking. My paid review costs $100 to $300, and it usually takes 2 to 5 days.
If your developer disappeared, quit or handed you something half-finished, you are probably worried, short of time and unsure whether any of the money you spent is recoverable. This is a common situation, and it is usually more fixable than it feels. I'm Anas, a full-stack Next.js developer. I build custom websites, web apps, SaaS products and premium templates, and I take over projects started by others.
First, Secure What You Own
Before anything else, find out what you actually have access to. These are the five things to check, each explained simply.
- Domain name. Your web address, such as yourbusiness.com. It is registered with a company, and the account should be in your name. How to check: look up the domain on a public "whois" lookup site and see whose name or email is listed, or search your email for renewal notices.
- Hosting. The service that keeps your site online. How to check: find who sends the invoices or renewal emails, and whether you can log in.
- Code repository. A place, usually GitHub or similar, where the site's code is stored with its history. How to check: ask whether you have an account with access to it, or whether it is under the developer's personal account.
- Database. Where the site stores its data, such as users, orders and content. How to check: find out where it lives and who holds the login.
- Admin logins. The username and password for the site's own admin area, and for any tools it connects to, like email or payment accounts.
Write down what you can reach and what you cannot. Do not worry if the list of "cannot" is long. It tells a new developer exactly where to start. If you are still in the early stage of a silent developer, what to do when a developer goes silent walks through the first steps.
What Does a Takeover Review Check?
A takeover review is a careful look at what exists, before any promises. The goal is to answer five questions in plain words:
- Does it run? Can the site or app be started and used at all?
- Is the code readable? Could another developer understand and continue it, or is it a tangle?
- What is finished? Which features work as agreed?
- What is missing? What was promised but never built?
- What is risky? Security gaps, accounts nobody controls and parts that could break.
What I check first when I take over a project: code access, hosting, the database, what works and what is broken.
The result is a short written summary, so you know where things stand before you decide anything. A review is not a commitment. It is the information you need to make a decision.
Fix It or Rebuild It?
This is the question everyone asks, and the honest answer is that it depends on what the review finds.
Fixing is usually the better choice when:
- The site mostly works and the missing parts are clear
- The code is understandable, even if it is unfinished
- The design and structure match what you need
- The deadline is close, because fixing is usually faster
A rebuild may be the better choice when:
- The code cannot be read or understood by another developer
- The foundation is unsafe or built on tools that are no longer maintained
- Fixing would cost close to the price of starting again
- What you need has changed so much that the old plan no longer fits
When I would recommend a rebuild instead: when the code cannot be understood, when the foundation is unsafe, or when fixing would cost about as much as starting again. I will tell you so honestly, even though a rebuild is the larger job, because patching a weak foundation tends to cost more in the end.
If it turns out that you have to start again, the useful part is that you now know what you want, and the work already done, such as designs, text and content, can usually be reused.
What Does It Cost to Take Over a Project?
I quote a takeover in two steps: a paid review first, then a fixed quote based on what the review finds. The review costs $100 to $300. After that, I quote per project, because the real price depends on things I cannot know in advance.
What changes the price:
- Size of the project. A five-page site and a web app with accounts and payments are very different.
- State of the code. Clean, organized code is faster to continue than a tangle.
- Missing documents. Without notes on how things were set up, a developer has to work it out.
- Deadline. A tight deadline usually means more work at once.
- Access. Missing logins add time while accounts are recovered.
Typical timeline: a review takes 2 to 5 days, and fixes take 1 to 8 weeks, depending on the size and condition of the project.
For an idea of what building from scratch costs, web app development cost gives the range for a new business app.
How to Avoid This Happening Again
Whatever happens with this project, a few habits make the next one safer:
- Agree the scope in writing. A list of what will be built, and what will not. I explain what a good agreement should contain in web development contract terms.
- Pay in milestones. Tie each payment to something you can see and approve, not to time passing.
- Own your accounts from day one. Register the domain and hosting in your own name, and give your developer access. I cover this in website ownership and access planning.
- Ask for regular updates. A short note every week shows progress, and silence becomes visible early.
- Keep the code in a place you control. A repository under your account, with your developer as a collaborator.
Red Flags When Choosing the Next Developer
After a bad experience, it is natural to be cautious. These are signs to slow down with any developer:
- No live examples of working projects
- Vague answers about what will be delivered
- No written agreement
- A request for full payment upfront
- Reluctance to give you access to your own accounts
I list more in scam web developer red flags. Most developers are honest. These checks make the good ones easy to spot.
Who This Is For
This is for a business owner or founder whose website or web app was left unfinished, abandoned or delivered half-done, who has a deadline and does not know whether the work can be saved.
Who This Is Not For
If you have not started a project yet, you need a new build, not a takeover. This is also not for you if you have a working site and only want a small change, which does not require a review. And if the previous developer is still available and willing to finish, talking to them first may be quicker.
What to Send Me Before Asking for a Review
- What the project is. A website, a store, a web app, and what it should do.
- What was done. What works, and what you were promised that is missing.
- What access you have. The list from the first section.
- Your deadline, and why it matters.
- Your budget range.
- Any contract or messages with the previous developer, if you have them. They show what was agreed.
Frequently Asked Questions
Can any unfinished project be taken over?
Many can, but not all, and a review decides. I will not promise to save a project before I have seen it. If it cannot be saved, I will tell you that, and what to do instead.
What if I do not have the code?
That is more common than you might think. Sometimes the site can be copied from where it is hosted, sometimes the code can be recovered from the previous developer. A review shows what is possible. In the worst case, the design and content can still be reused for a rebuild.
Will you criticize the previous developer?
No. Projects stop for many reasons, and it is not useful to assign blame. My job is to find out where things stand and what to do next.
How long until my project is moving again?
After access is sorted, a review takes 2 to 5 days. Then you will have a clear plan and a quote, so you know the next steps.
What to Send Me
If you need someone to take over an unfinished web project, send me what the project is, what was done, what access you have, your deadline and your budget range. I will tell you honestly what I think and whether a review is the right next step.
You can see what I take on at my services page, then send your details through pixelanas.com/contact.
Anas, full-stack Next.js developer building custom websites, web apps, SaaS products and premium templates.
