Skip to content
McGinnPublishing
03Contact

Start with the hardest part.

Tell us what is not working, what it is costing you, and what you have already tried. We reply within one working day, and the reply comes from whoever would actually run the project.

Project enquiry

The more specific the problem, the more useful our first reply will be.

Optional, but it helps us come prepared.

One working day to reply, from someone who would work on the project.

The questions we get before the first call.

Answered here so you do not have to spend a call asking them.

01Do we actually need to move off WordPress?
Often, no — and we will say so. Plenty of sites are a plugin problem or a hosting problem, and that is a week of work rather than a year. If we think a replatform is the wrong call, the first thing you get is a short document explaining why.
02Will our editors need to learn something new?
No. WordPress stays. The block editor, the media library and revision history all keep working exactly as they do now. What changes is that the front end is ours, so a layout change is a release rather than a plugin update.
03How long does a migration take?
A catalogue of a few thousand items with a clean URL structure is six to eight weeks end to end. Forty thousand titles with eleven years of redirects is more like twenty. We will not quote a number until we have crawled your actual content.
04Do you work on fixed price or time and materials?
Fixed price per phase, with a change-control process that puts anything outside the agreed scope in writing before it starts. We do not bill hourly for a fixed piece of work.
05What happens after launch?
Either we hand over — documentation, runbooks and training for your team — or we run it under a managed retainer with a contracted response window and named engineers. About half of clients do both.