Web Design in London: Day Rate or Fixed Price Phases, and How Each One Fails

A London web build is sold one of two ways, and the model you pick decides who carries the risk when the scope moves. On a day rate, in sprints, you buy time at a grade and the requirements can change as you learn. At a fixed price across phases, you buy a defined deliverable and the studio defends the boundary around it. Both are honest ways to sell a website and they fail in opposite directions: day rate work drifts, fixed price work hardens at the edges until every change is a variation. Choose on how settled your requirements actually are. Then write the handover list into the contract, because hosting, licences, admin access and the domain are what decide whether you can take the site somewhere else later.

How the two models fail, and the control that stops each one

	Day rate, in sprints	Fixed price, in phases
What you are buying	Time at a grade, with the work directed as it goes	A written deliverable for an agreed sum
Who carries scope risk	You do	They do, so they price it in
How it goes wrong	Drift. The weeks accumulate, the site is nearly finished for a long time, and nobody can say what is left	Variations. A thin specification turns every sensible improvement into a change order
The control that fixes it	A cap per phase, a definition of done per sprint, a weekly note of what was finished, and the right to stop after any sprint	A specification detailed enough to be the contract, a named variation day rate, and revision rounds numbered
When it is the right choice	Requirements still forming, or an existing site being improved	A defined marketing site, or a replatform with known content

The specification is where fixed price projects are won or lost. It needs to name templates rather than page counts, every integration, how much content is being migrated and by whom, which browsers and devices are in scope, and who writes the copy. A proposal that says ten pages has told you nothing, because one template used ten times and ten bespoke layouts are months apart in effort.

Three species of supplier wearing the same name

London has an unusual number of firms describing themselves the same way while running completely different businesses. The decks look alike. The companies do not.

• The design agency. Brand, interface design, art direction, sometimes the copy. Strong on how the thing looks and feels, and it builds through partners or contractors.
• The build shop. Implementation. It takes designs and makes them work, on WordPress, Shopify, a headless stack or bespoke. Judge it on code quality, performance, testing and the handover, and expect it to want designs that are finished.
• The product team in agency clothing. A small engineering led team used to running software with a backlog, selling sprints. Right when you are building a tool or a portal with logged in users, frustrating when all you needed was a marketing site for a fixed fee.

One question separates them on a first call: who personally writes the front end code, are they employed here, and can I meet them.

The handover list is the real negotiation

Everything a studio could hold on your behalf is something you would have to ask for back later. Put the list in the agreement at the start, when it costs nothing, rather than at the end when the answer has a price.

• The domain in a registrar account in your own name, with your own billing, and control of the DNS.
• The hosting account in your name, or a written statement of what you rent from the studio and what happens to the site if you stop renting it.
• Source files, design files and the code repository, with your own account holding owner permissions rather than guest access.
• Every licence in your own name, not the studio's. Plugin, theme, font and stock imagery licences carry a term and sometimes a traffic or domain condition, and a licence held by an agency you have left is a site that breaks quietly.
• Top level admin accounts on the content management system and the payment provider, not an editor seat.
• Analytics and tag manager properties owned by your organisation, with the studio added as a user.
• A deployment note: where the site lives, how a change gets published, and where the backups are.

Accessibility is a duty on a UK trading site, not a feature line

Under the Equality Act 2010 a service provider has a duty to make reasonable adjustments so that disabled people are not put at a substantial disadvantage, and a website through which you sell or provide a service is part of that service. Public sector bodies carry their own accessibility regulations on top of this and have to publish an accessibility statement. The standard specified in contracts is WCAG, usually to level AA. Name it in the specification at the start, because building it in adds modestly to design and front end time while retrofitting it later means rework.

Ask for these by name: every function reachable by keyboard, text contrast that passes, form fields with real labels and errors that say what to fix, meaningful alternative text, captions on video, a visible focus state, and headings in a sensible order. Ask for a screen reader test run by a person as well as an automated score, because the automated tools catch mechanical faults and miss the ones that stop somebody completing a purchase.

The UK obligations that belong in the build, not in the panic after launch

• Trading disclosures. A UK limited company has to show its registered company name, its company number, its place of registration and its registered office address on its website. A trading name in the logo is not enough.
• VAT. Show your VAT number if you are registered, and show prices to consumers inclusive of VAT.
• Cookies and tracking. PECR requires consent before non essential cookies are set, so the banner has to hold the scripts back until somebody agrees rather than record a choice after the fact. Your privacy notice sits under UK GDPR, and so does any form collecting personal data.
• Selling to consumers online. A shop has to give the required pre contract information, a cancellation route and a returns process, and delivery terms and charges before checkout.

None of this is expensive in the specification. All of it is expensive as a change request two days before launch.

What London buyers ask before signing a web build

Day rate or fixed price for a first website?

Fixed price, almost always, when it is your first proper site and you can describe what you need. You get a number you can budget and a boundary you can hold somebody to. Move to a day rate afterwards for the continuous improvement work, where the next task is decided by what the data shows rather than by a document written months earlier.

What should a London proposal contain before I sign anything?

The templates, the integrations, the content migration and who does it, the accessibility standard, the browser and device list, the hosting arrangement, the revision rounds by number, the variation day rate, payment stages tied to deliverables rather than dates, and the handover list. With those present you can compare two studios. Without them you are comparing cover pages.

Is WordPress still the right platform?

It is a good default for a content led marketing site where your own team will publish, and it is why so many London studios lead with it. The test is who maintains the site in a year. If that is a marketing person, a well built WordPress or a hosted platform beats a bespoke stack that needs a developer for every edit. If you have engineers, the calculation changes.

Does an ecommerce build change the model?

It tightens it. A shop adds payment, tax, delivery rules, stock, product data and an order flow, each an integration with its own edge cases. Fixed price works for a shop only when the specification is detailed, so expect a paid discovery phase first, delivered as a document you own whether or not you continue.

Who patches the site after launch?

Name the person in the contract. Platform and plugin updates, security patches, backups, uptime monitoring and a response time for something broken. Either buy that from the studio as a monthly arrangement with the tasks listed, or take it in house with the deployment note in hand. The arrangement that fails is the one nobody was asked about.

A studio's best work is the part a model cannot see

Web design is sold in pictures. A portfolio grid, a screenshot, a client logo, a showreel. That is the right way to sell it to a person and the worst way to be read by an assistant, which works from text. So when a buyer asks ChatGPT or Gemini to suggest a web design studio in London, the ones that come back are the studios who wrote out how they work: who they build for, what a phase contains, which platforms they use and what the client owns at the end. Some of the finest design work in this city is close to invisible to the thing now making the shortlist. Any studio can test this for itself: ask an assistant for a web build in its own city, then look at whose pages the reply actually used. AI Knows Us at aiknowsus.com turns that test into a measurement you can repeat.