Taking Over From a Previous Developer or Agency

One of the most common situations Karl encounters is a business whose ExpressionEngine or Craft CMS website has been left without proper developer support. The previous developer may have moved on, an agency relationship may have broken down, or a site built years ago has gradually been left without anyone who properly understands it. The result is a website that is difficult to change, potentially insecure, and with no clear path forward.

Karl Bowers has been inheriting ExpressionEngine and Craft CMS sites from other developers and agencies since 2007. Taking ownership of a complex codebase built by someone else is one of the things he does most regularly, and his approach is methodical rather than reactive.

What this service includes:

• Full codebase review to understand how the site has been built, what custom functionality exists, and where the risks are.
• Documentation of the existing system, so there is a clear record of how everything works before any changes are made.
• Identification of any immediate security or stability issues that need addressing as a priority.
• Ongoing development and support once Karl has properly learned the system, either on a retainer or project basis.
• Honest assessment of the site's current state, including any technical debt or areas that may cause problems in the future.

Common questions:

The previous developer left no documentation, is that a problem?

No. Most sites Karl inherits come with little or no documentation. Part of the initial process is working through the codebase to understand how it has been built and producing a working knowledge of the system from scratch.

How long does it take before you can start making changes?

It depends on the complexity of the site. Karl will give an honest assessment after the initial codebase review. For straightforward sites the process is quick, for heavily customised installations it takes longer to do properly.

What if the previous developer used non-standard or unusual approaches?

This is very common. Many bespoke ExpressionEngine and Craft CMS sites contain unconventional solutions built to solve specific problems. Karl approaches every codebase without assumptions, works out how each part functions, and documents it properly before making any changes.

Can you help if the previous developer is unresponsive or unreachable?

Yes. Karl can work from whatever access is available, including server files, database exports and the live site itself. In most cases it is possible to take ownership of a site without any handover from the original developer.

Will you need to rewrite the whole site?

Not necessarily. The goal of the initial handover process is to stabilise and understand the existing system, not to replace it. Rewrites are sometimes recommended for specific components, but Karl will always discuss this as part of an honest assessment rather than pushing for unnecessary work.

What if the site has security issues left by the previous developer?

Security issues are identified and prioritised as part of the codebase review. If there are immediate risks, Karl will address those first before moving on to other work. He will give a clear explanation of what has been found and what is being done about it.

Do you charge differently for inheriting a poorly-built site?

The initial review is priced on the basis of the time it takes to understand the codebase. More complex or poorly-structured sites take longer to review, so the cost reflects that. Karl will give an honest estimate upfront based on an initial look at the installation.

How do you handle the transition if the previous developer is still involved?

Karl is experienced in managing smooth handovers and is used to working professionally with outgoing developers or agencies. Where a handover is possible, he will make the most of it. Where it is not, he will work independently from whatever is available.