Change your web developer
Your developer stopped responding. Your agency didn't deliver. Let's sort this out.
Before I propose anything, I audit what you have and tell you honestly what's wrong, what's worth keeping, and what it would cost to fix. No surprises, no commitment before you know what you get.
My story
Your developer has gone quiet. Or the agency delivered something that doesn't work the way it was supposed to. Or you've just found out that you don't actually own anything. The code is on their servers, the domain is in their name, and changing providers means starting over and losing whatever was built along the way.
This happens more often than it should. There's a solution.
The first thing I do before proposing anything is understand what you have. An honest audit: what's working, what isn't, what can be kept, and what would be faster to rebuild. Sometimes the existing code is a solid base. Sometimes it's so compromised that rebuilding from scratch is cheaper than trying to patch it. The audit tells you which situation you're in, before you make any decision or sign anything.
The question that comes up in every one of these conversations: “How do I know you won't disappear too?” It's a fair question. The answer is track record, not promises. I've had clients in ongoing partnerships for more than two years. I respond to messages. When something goes wrong, I say what happened and what will be done about it. That's not a guarantee, but it's more than a statement of intent.
What changes structurally when we work together: everything moves into your name from day one. The domain, the hosting, the code, the CMS. Your accounts, your access, controlled by you. If you ever need to work with a different developer, they open the repository and keep going. No dependency on me, no proprietary systems, no retained information.
For clients coming from a blocked situation (a site that doesn't work, access withheld, or promises not delivered), the process starts with that audit, not a contract. I understand what there is to fix first. Then we talk about what makes sense to do.
I've worked through this situation with clients who arrived after difficult agency experiences. I know what to look for when I review a project that went wrong. The patterns are recognisable. And I know what to do next.
A practical note: changing your developer isn't necessarily more expensive than staying stuck with one who isn't working out. Every week with a site that doesn't function properly is a week of missed opportunities. The cost of not solving the problem is real, even if it doesn't show up on an invoice.
2+
years of ongoing partnerships
100%
yours from day one
0€
initial audit
120 hours
over 10 months
Case Study
Cocoon Cooks
A platform rebuilt from scratch. A designer’s vision implemented exactly. A team that runs it without a developer.
Read the full case study8–9 bilingual pages
PT + EN
Case Study
Cabanas da Viscondessa
A historic quinta in the Azores got a website guests could actually book through.
Read the full case studyThe process starts with a free audit. No commitment, no proposal, no contract. Just an honest assessment of what you have and what it would cost to fix.
If it makes sense to move forward: recovery and rebuild projects follow the same pricing structure as new projects, adjusted to the actual scope after the audit. Projects like this typically fit the Essentials or Marketing tier. The Services page has current pricing for each level.
You can also start with the audit only, with no obligation to continue. Some clients prefer to have the audit in hand before making any decision.
Frequently asked questions
It depends on what's there. Sometimes the existing code is a solid foundation that saves time and money. Sometimes it's so compromised that rebuilding is faster and cheaper than trying to recover it. The audit answers that question concretely, before any proposal or quote exists.
It depends on what's there. I've worked with a wide range of codebases. Some were well-structured and just needed continuity. Some weren't maintainable. The initial audit evaluates exactly that. If the existing code has value, we use it. If it doesn't, I'll tell you that clearly before we proceed.
I don't have a guarantee that eliminates that risk entirely. No one does. What I have is a track record: partners who have worked with me for more than two years, clients who reach out when they have a question and get a response, projects delivered on the agreed timeline. And a structure that doesn't create dependency on me: when the project ends, everything is yours. If you need a different developer, they can continue without needing to speak to me.
The domain, hosting, and CMS account transfers can happen within days, depending on what access is available. If the previous provider is withholding access, there are paths to resolve that, though they take longer. In cases where the code isn't available at all, the audit assesses what can be recovered and what needs to be rebuilt. There's no universal answer. The audit gives you a specific answer for your situation.
That's an urgent situation and we treat it as one. Depending on the severity, a temporary site may be needed while the recovery or rebuild project is underway. That's part of the initial audit: understanding the urgency level and what can be done in the short term.
Stuck? Start with a free audit.
Tell me what's happening. I'll review what you have and give you an honest assessment of what's wrong and what it would cost to fix. No commitment, no automatic proposal.