A WEBSITE THAT CLOSES, NOT ONE THAT LOOKS BUSY.

Custom is the default here because it is faster, there is less to break and nothing to keep updating. WordPress makes sense when your team already runs it, when a plugin does something genuinely specialised, or when whoever takes over after us needs to know the platform. If a contract or a team ties you to it, that is a real constraint and we build for it rather than argue.

For a simple brochure they are fine and cheaper, and we will say so if that is what you need. Where they run out is anything structural: a large episode or article library, a CMS shaped around your actual content types, page speed on a media-heavy site, or SEO work beyond filling in a title field. You also cannot move a Squarespace site anywhere. Ours is your code, on your hosting.

One page if you sell one thing and the whole argument runs in a single scroll. A full site once you have several offers, a library worth browsing, or pages that need to rank for different things, because one page can only ever target one query properly. If you are unsure, start with the one pager: it is cheaper, it ships faster, and it can grow.

It will if nobody plans for it, and that is the most expensive mistake in a rebuild. Every URL on the old site is mapped to a page on the new one before launch, the ones with no equivalent are pointed somewhere honest rather than at the homepage, and the schema, sitemap and canonicals are rebuilt rather than inherited. Done properly a rebuild usually helps, because speed and structure are ranking factors.

Yes. Content, images, posts and the URL structure all come across, and we take the old site page by page rather than trusting an importer. We do not need your old logins to read a public site, though if there is anything behind one you will need to hand it over.

A ten-minute questionnaire and a folder of whatever you already have: logo, photographs, any copy, testimonials, links. Do not organise it. The first working version lands 48 to 72 hours after both arrive, so the pace is set by how fast that folder fills rather than by us.

We structure them and draft them, you correct them. Nobody outside your business can write your offer better than you can, and nobody inside it enjoys staring at a blank page, so you get a draft already in the right shape and in your voice and you fix what is wrong.

As many as your agreement covers, and the number is in it before you sign. In practice it rarely matters: you are reacting to a working site from day three rather than to a mockup, so the changes are small and specific instead of a debate about direction.

Yes, that is what the CMS is for, and it is built around your actual pages rather than a generic set of fields. You get a recorded walkthrough at launch so you can watch it twice. If you would rather not touch it, ongoing care is its own arrangement and not something bundled in and never used.

Yes, on final payment, and it is written into the agreement. The design, the front-end and back-end code, the content structure and the configuration are all assigned to you. No licence you keep paying for, and nothing held back as leverage.

It is built for the phone first and tested on a small one, not scaled down from a desktop layout at the end. Most of your traffic arrives on mobile and most template sites treat it as an afterthought, which is where the four-second load times come from.