Choose the guest journey before the visual treatment
Start by separating three jobs: finding a venue, deciding whether it fits the occasion, and making a booking. A guest arranging a private dinner needs capacity, layouts, accessibility details and an inquiry response; someone booking a room needs dates, occupancy, room differences and a dependable reservation engine. Those are different products, even if both proposals promise a beautiful hospitality website. Visit London's official visitor guide separates attractions, food, accommodation, transport and accessibility. That is useful evidence of the different questions a visitor brings, rather than a template you need to copy.
Write one primary action for each page. Then ask the designer to show how the atmosphere, menu or room photography helps that decision. A film can establish the character of the place, but it should not hide the address, opening hours or booking action. Require one working mobile journey in the proposal review, from arrival to the booking system, with the guest's selected venue preserved.
Quote the booking integration as a complete handoff
A button linking to another website, an embedded booking widget and a custom availability interface have different costs and responsibilities. Ask which one is included. Identify who owns the reservation account, pays transaction or subscription charges, changes availability and handles cancellations. Ask whether the provider can preserve the selected property, language, date and party size; verify supported behavior with your actual booking vendor before promising it.
Test unavailable dates, a full sitting, an expired session and a failed payment in the vendor's test environment where available. The website should explain what happens next and offer a useful recovery route. A confirmation screen must mean that the reservation system accepted the booking, not simply that somebody clicked. For private events, a received inquiry is the correct outcome until staff confirm the date. Track these as different events. This distinction prevents a report full of booking-button clicks from being mistaken for confirmed revenue.
Give every real venue an editable operational record
For a group with several London venues, define shared brand components and separate venue records. Each record should own its address, contact details, opening exceptions, menu, booking destination, images and access information. Let the operator update an exceptional closing time once instead of editing a footer, a menu PDF and three language pages independently. Do not generate a page for every London neighborhood if the business has no distinct service or location to explain there.
Visit London's accessibility resources point visitors toward detailed venue and transport information. Translate that into accurate first-party content: which entrance to use, whether there are steps, whom to contact and what the venue has actually confirmed. Avoid a vague accessible badge. During procurement, ask a member of the venue team to update one menu item and one opening exception in the proposed CMS. If they need a developer for each routine change, include that continuing dependency in the price comparison.
Buy photography, language and performance as one scope
A visual concept based on dramatic room photography will disappoint if the quote contains no shoot, art direction, licensing or image selection. Name the owner of each asset and request crops for mobile as well as desktop. Specify which images must load immediately and which can wait until the guest reaches the gallery. A gallery should reveal the place; it should not require downloading every full-resolution photograph before the booking link works.
If Spanish is part of the audience plan, count the translated menus, room descriptions, form errors and reservation messages. The external booking experience may support a different set of languages from the main website. Record that limitation openly and decide who reviews it. Google's language-version guidance explains reciprocal links between equivalent translated pages. Ask for those links in the delivered HTML, alongside a visible language switch that keeps the visitor on the corresponding venue or room. Translation volume and later menu changes belong in the operating budget.
Use this sample brief to make proposals comparable
Consider an illustrative London hospitality group with two venues, one shared brand, English and Spanish content, and an existing reservation supplier. Its brief asks for a group homepage, two venue pages, menus, private-event information and a contact route. It also includes a photography plan, editable opening exceptions, accessible forms and migration of the URLs that already receive inquiries. This is an invented scope for comparing proposals, not a Dardo client case or a local market price.
Have each finalist price the same work in the same currency and state whether applicable taxes are included. Separate design and implementation from copy, translation, photography, booking subscriptions and support. Require the first-year total and the next-year recurring total. A cheaper quote may be entirely suitable if your team supplies content and uses an existing booking product; a larger fee needs a clear additional deliverable. Compare who is responsible for the launch and for restoring service if a booking integration breaks.
| Workstream | Proof before acceptance |
|---|---|
| Venue records | Staff update an opening exception in both languages |
| Reservations | The selected venue reaches the booking system correctly |
| Private events | A received inquiry remains distinct from a confirmed booking |
Decide what needs a local team, then test the result
An on-site shoot, venue survey or workshop may benefit from a local specialist. Art direction, website production and CMS training can also be delivered remotely when ownership and review times are explicit. Ask every bidder where its team actually works and which on-site activities are included. A London-focused page does not prove a London office. Dardo publishes this guide as a web-design studio; it does not claim a London address through this article.
Before sign-off, complete the guest journey on a phone and with a keyboard. Confirm the correct venue, language and date arrive at the booking system, and verify the resulting record there. Let staff perform the promised content edits and check the translated page afterward. Review confirmed bookings, received event inquiries and qualified opportunities separately after launch. That gives the design a business test while preserving the atmosphere you hired the studio to create.
Plan a project with Dardo
Plan a project for the United Kingdom
Choose a review date and a time in Bogotá to see the corresponding local time. This is a planning aid, we’ll confirm availability when we reply.
Europe/London — Representative time zone; some countries have more than one. Check the actual city and agree on a working window. Dates include seasonal clock changes through your browser’s time-zone data.
Budget currency to discuss: GBP. The project calculator lets you enter your own rate. It does not convert exchange rates.
Let’s make it happen.
Send your result and project details directly to Dardo. We’ll review them and reply to your email. Review the included details below before sending.
Prefer email? hello@dardo.studio
Sources & further reading
Sources behind this guide, with further detail from the original publishers.
- Visit London: official visitor guide
- Visit London: accessible London
- Google Search Central: localized page versions
- W3C: accessible forms tutorial