Your website is stuck. I'll take it from here.
Unfinished project, unfixed bugs, unavailable developer. Before starting from scratch, let's take stock together on a discovery call.
Do you recognise yourself?
Your developer is no longer available and your project has stalled
Your site was delivered but bugs persist and no one is fixing them
Your original contract didn't cover what comes next and you need your site to evolve
You've already invested time and money and don't want to start from scratch
One rule: I only commit if I can genuinely help.
I don't take on just any project blindly. Before any commitment, I take the time to assess the situation: the state of the code, the hosting, the available access. This step is essential to give you an honest answer about what's feasible, within what timeframe, and at what cost.
You explain your situation
During a 30-minute discovery call, you tell me about your project — what was planned, what was done, and what's causing the problem.
I evaluate the project
I analyse the existing code, available access, and the extent of the remaining work.
I tell you what I can do
I'll give you a clear action plan with a quote. Or I'll honestly tell you if it's outside my scope. Either way, you get an answer.
A developer used to taking over existing projects.
At Société Générale, I spent three years maintaining, improving, and migrating applications I hadn't built myself. Reading existing code, understanding technical decisions that aren't always documented, identifying what can be kept and what needs to be rebuilt — that's a skill in its own right.
Before you throw it all away, let's talk.
A 30-minute call is often enough to see the situation clearly.
I work with a limited number of clients at a time. Check my availability.
No commitment. I reserve the right to decline if the project is outside my scope.