Website & Web Application Development

The development scope includes review and launch checks for the functionality we deliver: agreed user journeys, supported browsers and devices, keyboard access and performance against the project budget. You do not need to purchase independent QA just to have that work checked. A broader test programme, testing of an existing product, maintained regression automation or an OWASP security assessment is an additional engagement, with its own coverage and deliverables identified in the proposal.

Our development service focuses on custom applications, typically with Next.js. A builder or existing CMS can be a better fit for frequent editing by a non-technical team. We agree the editing workflow before choosing the approach. Custom development offers control over functionality and design, but hosting, licences and maintenance still need to be scoped. Performance is measured against the project requirements rather than assumed from the framework.

Yes. We can implement designs supplied by your team or agency, or handle design ourselves. Either way, brand consistency is treated as a requirement, not a preference. If you bring finished designs, we will review them for the things that tend to be decided in code rather than in the design file — behaviour at intermediate screen widths, focus and error states, what happens when a field of text is three times longer than the placeholder. Raising those early is faster than discovering them during build. If you bring guidelines rather than designs, we work within them and hand back the component set as a documented extension of the system.

Every project includes a support window for fixes and adjustments. After that, you can maintain the site in-house using our documentation, or keep us on for ongoing work — retainer or ad-hoc, your call. The handover is built to make in-house maintenance realistic rather than nominal: the repository, the deployment configuration, the content model and documentation written for whoever inherits it. Nothing runs on infrastructure only we can access, and there is no proprietary layer that needs us to stay involved. If you later decide to move the work elsewhere, the next team receives a normal codebase rather than a puzzle.