Questions we get asked most.

A small site is typically four to six weeks; a larger custom build with integrations is usually eight to twelve. The single biggest variable is content. Projects wait on copy and photography far more often than on development.

Yes. Most of our work is done remotely and several of our clients operate internationally. We’re happy to meet in person when it’s useful, but it’s rarely necessary.

No. Page builders make the first week faster and every week after that slower. They add significant weight, hurt Core Web Vitals and make sites harder to change. We write themes by hand.

Yes. We build editable content structures and train you on them at handover. What you won’t be able to do is accidentally break the layout, which is deliberate.

You do. That covers the design, the code, the domain and the hosting account. We hand over full access and documentation at launch. There’s no lock-in of any kind.

Often, yes. We start with an audit of the existing build, hosting and access. Occasionally we find a site is cheaper to rebuild than to inherit, and we’ll tell you if that’s the case.

We do technical SEO, covering site structure, speed, crawlability, structured data and the server-rendered content that AI search engines need. We don’t sell ongoing link-building or content-marketing retainers.

Every project includes a post-launch support window. After that you can move to a care plan, take it in-house, or hand it to another developer. all three are fine with us.

Yes, typically a deposit to begin, with the remainder split across design sign-off and launch. Exact terms are set out in the proposal.

Design stages include revision rounds, and we agree structure before any visual work so surprises are rare. If a direction genuinely isn’t working, we’ll explore another rather than push the first one through.