Spend less time fixing your WordPress site.

No. WordPress runs a very large share of the web and does it well, and a maintained site with a sensible plugin set is a perfectly reasonable place for a business to be. A rebuild is worth considering when the ongoing effort of keeping the current site working has become the problem, or when the site has grown more complicated than the business needs. Sometimes the honest recommendation is to improve what you have, and we will tell you when that is the case.

That is an outcome of the assessment, not a decision we make in advance. For a marketing site that mainly needs to load quickly and be straightforward to edit, a largely static build with a managed content editor suits a lot of service businesses. A site with memberships, a store, or substantial custom functionality points in a different direction. We will explain the options and the tradeoffs before anything is committed.

Yes, and how you edit is part of the scope rather than an afterthought. We establish who updates the site, how often, and which parts they need control over, then choose an editing setup that matches. If your team is comfortable with the current editor, that is a legitimate input into the decision.

Yes, if that is what you want. Carrying the existing design across is usually the quicker path and is a common choice when the look is working and the maintenance is not. Equally, a rebuild is a natural moment to revisit the design if you were planning to anyway. Either approach is a scope decision, not a technical constraint.

Existing URLs are preserved where that is practical, and where an address has to change it is mapped to its new destination with an appropriate redirect. Relevant metadata and indexing controls carry across as part of the work. What nobody can honestly promise is a migration with no temporary movement in search visibility: search engines need to recrawl and reprocess the site, so some fluctuation during that period is normal. The work is in making it short and recoverable rather than pretending it does not happen.

These need a closer look before anyone should commit to an approach. Stores and membership sites carry customer accounts, order or subscription history, payment integrations, and access rules, and the cost of getting any of those wrong is much higher than for a marketing page. We assess them individually, and in some cases the recommendation will be to keep and improve the existing platform.

It depends on the size of the site, how much functionality has to come with it, and how much of the content is being carried across as-is versus reworked. We quote against an agreed scope after the assessment rather than from a price list, so the number reflects your site rather than an average one.

The assessment sets the timeline, because the honest answer depends on page count, integrations, and how much content needs attention on the way across. You will have a schedule alongside the scope and the quote, before the build starts.

Yes. Every website does: dependencies get updates, integrations change their APIs, hosting needs attention, and content needs someone to own it. The goal of a rebuild is to make that work smaller and more predictable, not to remove it. Any site described as maintenance-free is simply one where the maintenance is not being done.