Frequently asked questions
Website project questions, answered clearly.
The right answer depends on the brief. These FAQs explain the assumptions, limits and next information behind common decisions.
Ask a different questionAll questions
Project FAQs.
Do you only work with businesses in London?+
No. The company is positioned around London and can work with teams across the UK and internationally when the working model and project are a fit.
Do you design and develop websites?+
Yes. Strategy, content structure, UI and UX design, development and launch quality can be planned as one engagement or scoped around a specific gap.
How much does a website cost?+
Cost depends on strategy, content, number of distinct templates, integrations, migration, platform and the standard of testing. A responsible quote follows a clear brief and assumptions.
How long does a website project take?+
The timeline depends on scope, content readiness, approvals and external dependencies. The plan should use stages, owners and acceptance criteria rather than one unsupported date.
Which platform do you recommend?+
The simplest platform that fits the content, commerce, integrations, team and long-term ownership. Shopify, WordPress, WooCommerce and Next.js each suit different operating models.
Can you redesign an existing website without losing SEO?+
A migration plan can reduce avoidable risk by protecting valuable content, URLs, redirects, internal links, metadata and measurement. No provider can guarantee unchanged rankings.
Do you provide SEO?+
Website projects can include search intent mapping, crawl and indexation controls, metadata, structured data, redirects, sitemap, performance and launch validation. Ongoing content, digital PR and authority work require a separate programme.
Can you guarantee first place on Google?+
No. Search positions depend on competition, relevance, authority, links, brand demand, technical quality and ongoing performance. A guaranteed number one claim is not credible.
Will the website be accessible?+
The design and build target WCAG 2.2 AA practices, including keyboard use, focus, structure, contrast, forms and responsive behaviour. Formal conformance requires complete-page testing and should not be claimed without evidence.
Who owns the code, domain and accounts?+
Ownership, licences and access are documented in the proposal and handover. The client should control the domain and business-critical third-party accounts.
Can you work with our internal marketing or development team?+
Yes. Repository access, responsibilities, review points, deployment ownership and handover are agreed so work is not duplicated or left ambiguous.
What happens after launch?+
The launch includes verification and handover. Ongoing support can be scoped around monitoring, updates, performance, content changes and an agreed improvement backlog.