What is included in your custom website development services?
The agreed scope can cover page strategy, copy development, original visual design, responsive front-end development, forms, integrations and launch checks. We also define how the team will edit content and what is included in handover. Page types, migration work and third-party services are specified before the build, so the deliverables are concrete.
Which technologies do you use to build websites?
We work with PHP, the MERN stack (MongoDB, Express, React and Node.js), Python and other technologies. We choose the approach around the content, interactions, integrations, hosting and editing workflow. A straightforward business site and an interactive web application can call for different solutions; we explain the recommendation and its maintenance needs before building.
Should we redesign our website or improve the existing one?
Start with the problems you need to solve. If the platform and structure are sound, better copy, navigation or a repaired enquiry journey may be sufficient. A rebuild is more useful when the site cannot accommodate the content, design, editing or integration requirements without disproportionate work. We review what can be retained before recommending replacement.
Do you write the website content as well as design it?
Yes, copy development can be included in the website scope. We work from your services, customer questions, project material and business knowledge, then shape the page structure and wording alongside the design. Your team approves factual claims and provides permission to use supplied material. We identify missing evidence instead of inventing testimonials, results or credentials.
Why choose a hand-coded website instead of a page builder?
A hand-coded website gives us direct control over the templates, responsive behaviour, assets and integrations. That is useful when your services need distinct page designs or the enquiry process needs specific business logic. It is not automatically the cheapest or best option. A standard platform may suit a simple website; we compare the editing requirements, constraints and operating costs before recommending a custom build.
Can our team update the website without a developer?
We define the editing requirements before choosing the implementation. A frequently updated site may need structured content fields, a CMS, previews and user permissions. A site that changes rarely may use a simpler arrangement. The proposal identifies what your team can change directly and which changes require development. Editing guidance is part of the agreed handover.
Can you preserve our existing URLs during a redesign?
We inventory important addresses and retain them where they still fit the new structure. Where an address changes, we map it to an appropriate destination and implement the agreed redirects. We also check internal links, canonical URLs and the sitemap. This supports continuity for users and search engines, but a redesign cannot guarantee unchanged rankings or traffic.
Will the website be optimised for search engines and AI search?
The build includes the agreed technical foundation: crawlable pages, descriptive titles, canonical URLs, sitemaps and appropriate structured data. We organise substantive content around the offer and the questions buyers ask. These measures support discovery and understanding; they do not guarantee rankings or inclusion in AI answers. Ongoing search research, content development and measurement can be scoped separately.
How do you make the website load faster?
We inspect the actual pages and control what they load: correctly sized images, suitable image formats, font delivery and scripts that serve a clear purpose. We test representative pages under recorded conditions and review the effect of external widgets and tracking. We do not promise a universal loading time or perfect score, because hosting, networks, devices and third-party services affect the result.
Can the site connect to our CRM or booking system?
Yes, where the target system supports the required integration. We assess its API or embed options, authentication and data requirements before committing to the connection. The scope defines what is sent, what the visitor sees and what should happen when delivery fails. Required subscriptions and third-party limitations are identified separately.
How much does a website cost, and how long does it take?
Cost and timing depend on the distinct page types, content readiness, migration, editing features and integrations. We define those requirements before providing a proposal and schedule. Every project has a fixed price, agreed in writing before we start. The number we quote is the number you pay. Hosting, licences and ongoing services are identified separately. Review availability and access to existing systems are included in the delivery assumptions.
Does a custom-coded website still need maintenance?
Yes. Hosting, application runtimes, libraries and external integrations still need attention. Content, backups and forms also need an owner. We document those responsibilities at handover and distinguish defect fixes from ongoing maintenance or new features. 30 days of fixes after launch are included. Training is quoted separately, and ongoing support is on a monthly retainer.
Who owns the website and its accounts?
Your accounts, domains and code repository are in your name from day one, and the code is yours as you pay for it. Handover includes the agreed repository, hosting and service access, deployment notes and editing instructions. Third-party products retain their own licences and terms; any recurring services are identified separately.