Our Umbraco build has stalled.

You can feel a project die before anyone says it

The updates changed first. They used to arrive with screenshots and small victories; now they arrive late, and every one says the same thing in slightly different words. Blocked on. Waiting for. Hoping to. The launch date has moved three times, each move announced with less ceremony than the last, and somewhere along the way everyone stopped mentioning the date at all.

You have paid for most of a website. What you have is a staging link that half works, a backlog nobody believes, and a growing fluency in phrases like content freeze and scope realignment. The old site, the one this project was meant to replace, is still live and still embarrassing, and colleagues have started asking you about it again because they can sense the new one is not coming.

What makes a stalled build so corrosive is that nobody is lying to you. The developers genuinely believe it is nearly done, because the visible parts mostly exist. The agency genuinely intends to finish, because unfinished projects hurt them too. But intention is not velocity, and somewhere underneath the reassurances there is a real, specific reason the work stopped moving: a technical decision that made every subsequent task slower, a key person quietly reassigned to a louder client, a scope that grew without the budget growing with it, or an integration that turned out to be far harder than the estimate assumed. Stalls always have a cause. The reassurances are just the sound the cause makes while it hides.

And you are stuck in the worst seat, accountable for the outcome without any way to see into the machine. You cannot tell whether you are three weeks or eight months from launch, whether to push harder or start over, whether the money already spent is an asset or a write-off. Every option feels like a gamble because, without independent eyes on the code, it is.

What I do about it

The first thing I bring is sight. Give me access to the repository and the staging environment, and within days you get something you have not had for months: an independent, technically grounded account of where the project actually is. What is built and sound. What is built and rotten. What was never really started, whatever the status reports said. And most importantly, the specific cause of the stall, named plainly, because you cannot fix a project without knowing what stopped it. My answer to whether I take over unfinished builds describes how that assessment works; it is a small fixed piece of work, and you own the findings whatever you decide next.

Then there is a fork, and I will give you an honest recommendation at it. Sometimes the right move is for me to advise while your existing team finishes: the stall was a solvable technical blocker, and a few days of consultancy clears the way and hands the project back moving. Sometimes the right move is for me to finish it: the remaining work lands in my hands as ordinary Umbraco development, planned in weekly slices you can see, at a flat £500 a day with no rescue premium. What I will not do is reflexively condemn the previous team's work to make the takeover bigger; salvaging is almost always cheaper than restarting, and the assessment exists to prove which is which.

From there the finish is deliberately boring. Weekly visible progress against a list you can read. The awkward conversations had early, especially about any scope that has to be trimmed to make the launch real. Content migration and editor training treated as part of the project rather than an afterthought. A launch day with a rollback plan, followed by the quiet fortnight of small fixes every launch actually needs.

Two questions people in your position usually ask next: what this costs is on the freelance developer cost page, and it is almost always a fraction of what has already been spent standing still. And whether the site will then depend on me the way it depended on them: no, everything is documented and handed over as if I were the one leaving. When you are ready, describe the project and where it stopped through the contact page, and you will have a reply within a working day.