You have something that half works. Diagnosis first, then a decision.
Repair, rewrite or replace. I'll tell you which of the three is worth it before you pay for anything, including when the answer is to touch nothing.
Do you recognise yourself in any of these?
The contractor stopped replying
The project sits somewhere between finished and unfinished, you don't know where the access credentials are, and nobody knows what's left to do.
The site is slow and falls over on a phone
Things were added for years without a plan, so every addition slowed down the one before it.
The design is fine, but nothing happens
It looks good and nobody gets in touch. That gets fixed with structure and message, not a new design, and it's often cheaper than you think.
You don't know where the domain, hosting and code are
The first thing I do is make a list: what you own, what sits with someone else, and what needs to come back under your name.
What exactly you get.
Concrete, with no "and much more". If something on the list isn't for you, it leaves the scope and it leaves the price.
- Diagnosis of the current state with a written findings report
- A list of access credentials, domains and hosting in your name
- A recommendation, repair, rewrite or replace, with the reasoning
- Redesign of structure, content and interface
- Move to a maintainable platform if that's the conclusion
- Keeping your SEO strength through redirects, without a drop in traffic
The process for this service.
At every step you know what we're doing, why we're doing it and what comes next.
Intro call
30 min · no charge
We talk about what you're building, where you are now and where you're going. By the end you know whether this is work for me at all, and if it isn't, I'll tell you who to call.
Discovery and specification
We go deeper: users, processes, integrations and risks. The output is a written specification, a proposed architecture, a phase plan and a fixed proposal, along with the Project plan, the Contract and an NDA. That document is yours even if we don't work together after it.
Design and prototype
A clickable prototype before a single line of code is written. Changing your mind here costs an hour. Three weeks later it costs three weeks.
Building in weekly cycles
Every week you see the progress on a live version and tell me what's off. No three months of silence followed by a big reveal at the end.
Testing and launch
Functionality, speed, security, SEO and analytics. Handover includes every access credential, the documentation and a recorded walkthrough, so the site is yours and not mine.
After launch
We measure what works, fix what doesn't and keep building. A support package with a fixed number of hours, or work as needed, whichever suits you.
You don't have to take my word for it. Here's what is already live.
Investment
A redesign has no fixed entry price, because everything depends on what we find. The diagnosis is a separate, small engagement, and after it you know the exact price and hold a written report that is yours even if we don't work together after it.
The things people usually ask at the third meeting.
A common case, and a solvable one. The domain and hosting can almost always be returned to your name through company ownership, even without the previous contractor's cooperation. The code is harder, and sometimes the conclusion is to write it from scratch.
Yes, if it's in a state where working on it is worth it. If it isn't, I'll tell you and explain why, instead of billing hours patching something that will break again in six months.
It's billed hourly and usually fits into a few hours. You get a written report with a conclusion and an estimate. If we go on into a project, that amount is deducted.
Not if the redesign is done properly. Existing addresses are mapped to new ones through redirects, the structure is preserved, and measurement runs before and after. A drop in traffic after a redesign is a sign nobody did that work, not a consequence of the redesign itself.
Often yes, and that's the cheapest option. If the visual identity is good and the problem is structure and speed, there's no reason to throw away what already works.
Do you actually need something else?
If you have an idea worth doing properly, the first step is a 30 minute conversation.
No proposal and no pressure. You tell me what you're building, I ask the questions nobody has asked you yet, and by the end you know whether it's feasible, roughly what it costs and what the next step is. Whether or not we end up working together.
