When a Freelancer Holds Your Website Back: How to Recover a Stalled Launch
A business needed a new website for its planned brand launch. The freelancer working on it was slow to reply, and the work produced so far was poor quality. Weeks passed, the launch date slipped, and the team was stuck. They also wanted to overhaul their existing site, but could not until this was resolved.
A stalled website launch is stressful and costly. Here is how to regain control and move forward without making things worse.
Assess what you actually have
Start by reviewing the work so far. What exists: designs, pages, code, content? What is usable, and what needs to start again? An honest review shows whether to rescue or restart, and gives you facts for any conversation.
Stalled website launch: secure your access
Find out who controls the key items: the domain, hosting, design files and any logins. Make sure your business owns them, or arrange a transfer. Keep this factual and polite. Ownership protects you whatever you decide.
Talk to the freelancer clearly
Approach the conversation calmly. State what you need, by when, and what happens if it is not delivered. Agree a short, written plan, or a clean handover. Many problems come from unclear expectations, and a clear message can fix them or make the next step obvious.
Decide between rescue and restart
If the foundations are reasonable, a new team can improve them. If the design and code are poor, it may be quicker to restart with a clear brief. Compare the cost and time of each option. Do not carry poor work forward just because money was spent.
Set a clear brief and timeline
Write a short brief: goals, audience, pages, tone and deadline. Agree milestones, such as design, content and testing. Assign one person to approve each stage. Our article on a six-week clinic website build shows what a healthy timeline looks like.
Protect the launch date
If a date matters, such as a public announcement, consider a smaller first release: a simple, well-made site covering the essentials. Add more later. A clear, small launch beats a delayed, half-finished one.
Avoid the same trap again
Choose suppliers on responsiveness and evidence, not just price. Ask for examples, and speak to past clients. Agree how updates, feedback and support will work. Keep your own accounts and files. Our article on developer dependency explains ownership.
Keep your team informed
A stalled project is stressful. Tell everyone what is happening, what the new plan is and when they will hear next. Clear communication reduces anxiety and stops rumours. It also helps people stay patient while you fix the problem.
Learn for next time
Once the project is back on track, note what went wrong: unclear brief, no milestones, weak communication or a poor match. Write down what you would change. The lessons will make your next project faster and smoother.
Do not lose the momentum
When a project stalls, motivation drops. Keep a visible plan with small, near-term wins, such as a finished homepage or a first set of pages. Progress you can see rebuilds confidence and keeps stakeholders on side while the rest is completed.
Set a decision date
Give yourself a firm date to decide whether to continue with the current supplier. A deadline stops drift and gives you time to switch if needed.
Keep copies of everything
Save all files, designs and content in your own storage. If work stops, you can hand it to someone else without starting over.
Check contracts and ownership
Read what you agreed about ownership, payment and notice. Clear terms help you act calmly if you need to move on.
Communicate with your audience carefully
If a launch date slips, avoid over-promising in public. Share a simple holding message and update it when you are ready. Honest, calm communication protects your reputation while the work catches up.
Build in quality checks
Before anything goes live, check pages on a phone, test forms and read the content for errors. A short checklist at each stage catches problems early. Quality control is far cheaper than repairing a poor launch.
Rebuild trust with the team
A stalled project can leave people frustrated. Explain the new plan clearly and show early progress. Small visible wins help everyone regain confidence, and they keep energy high until the launch.
Agree how you will work together next time
Once the project is back on track, write down how you will work with your supplier: how often you meet, how feedback is shared, who approves and how changes are handled. A short working agreement prevents a repeat of the same problems, and makes both sides more comfortable.
It also helps to schedule a review after launch, so lessons are captured while they are fresh.
Choose a partner who values communication
When you select a new supplier, watch how they communicate before you sign. Do they reply promptly, explain clearly and admit uncertainty? Early behaviour is a good guide to how a project will go. Ask for a named contact and agreed response times.
Recovery checklist
- Review what exists.
- Secure your accounts and files.
- Talk to the freelancer, in writing.
- Decide whether to rescue or restart.
- Agree a brief, milestones and one approver.
- Consider a smaller first launch.
Our companion article on B2B to B2C covers the brand side. If you would like help, we are glad at Pulse Digital Health to talk.
Frequently asked questions
What should I do if my freelancer is not responding?
Review what exists, secure your accounts and send a clear written request with a deadline. Prepare an alternative plan. Send a clear written request with a deadline, and keep a copy of every message. A written request is clear and provable, and it gives you a record if you need to change supplier.
Who should own my website files and domain?
Your business. Suppliers should be given access, not ownership. Keep copies of everything, including designs, content and logins, in your own storage. Your own copies protect your work, so a stalled supplier can never hold your designs and content hostage.
Should I rescue or restart a poor website?
Compare the cost and time of each. If foundations are weak, restarting with a clear brief can be quicker. Compare the cost and time of each option honestly, including the cost of further delay. An honest comparison includes the cost of further delay, which is often larger than people expect.
How can I protect a launch date?
Consider a smaller first release covering the essentials, and add more later. Agree a smaller first release covering the essentials, and add more once it is stable. A smaller release still helps patients, and it lets you show progress instead of waiting for a perfect launch.
How do I choose a reliable supplier?
Look at responsiveness, examples and references, and agree how updates and support will work. Ask for examples and references, and speak to at least one past client. References show how suppliers really behave under pressure, so speak to at least one past client if you can.
What should a website brief include?
Goals, audience, pages, tone, deadline and milestones, with one person to approve each stage. Write the brief down and agree one approver, so decisions are quick. One approver speeds decisions, because feedback arrives together and conflicts are settled before work begins.
