Client Website Delivery (Sheffield)

A site, handed over

The brief was a working website for a real client, and the work ran the whole length of it. Requirements sessions came first, then a site structure and a delivery plan drawn from what the client actually said. Prototypes went out for feedback and came back changed. It was delivered in October 2025, to d-a-r-t.co.uk, a Sheffield home appliance store.

Requirements, then prototypes

The tech list for this project names a process, not a framework. Web development, UI/UX, prototyping, client requirements, iteration, deployment, domain transfer, Git and Figma. That is the honest shape of the job. The hard part of a client build is rarely the build. It is turning what someone says in a meeting into a structure they recognise when they see it, and then changing it when they do not.

The tech list for this project names a process, not a framework.

The domain transfer

The last mile was a handover, and a handover involves someone else. The domain sat with the client's previous web provider, so the migration had to be coordinated with them rather than done alone. The stated aim was a reliable release with minimal disruption. The build itself was made for usability, clarity and maintainability, so the client could keep updating the site after the handover.

The studio behind it

This came out of UCD, the small web studio I founded and ran with my housemate, delivering websites and SEO to local Sheffield businesses while we were still at university. We carried the whole lifecycle on those jobs: client discovery, design, the full-stack build, deployment, and the maintenance afterwards. The studio ran for 2025 and is closed.