Put the essentials on the page
Keep current hours, address and menu links easy to find on a small screen. Agree who updates seasonal menus and temporary closures.
Someone looking at a Soho venue on their phone may be choosing where to go tonight. We design websites that put the menu, opening times and booking route within easy reach, while giving your photography room to show what the place feels like.


Photo: Leandro Neumann Ciuffo
Soho (1877979497).jpg (Source) · CC BY 2.0
Reduced-resolution copy; cropped to fit the card. Available under the stated licence.
These are the questions we would work through for this Soho brief. The final scope depends on your current site and how the business operates.
Keep current hours, address and menu links easy to find on a small screen. Agree who updates seasonal menus and temporary closures.
Follow the journey into your reservation provider. Visitors should know whether they have made a confirmed booking or only sent a request.
Explain capacity and available formats using figures your team has approved. Ask for the date and outline of the event once the initial enquiry reaches you.
Soho sits in central London and brings together dining, shopping and entertainment. For an independent venue here, the website has a practical job alongside its visual identity: help someone decide whether the experience suits their plans. We would separate everyday bookings from private hire, make menus readable without a download and explain any booking conditions before the visitor leaves for another platform. The brief starts with your actual operation, not assumptions about what every Soho business needs.
Bring your current menus, booking provider details and photographs you have permission to use. Include the questions staff repeatedly answer before a booking.
Try finding a menu and making a test reservation from a phone. Then check a private-hire enquiry reaches the right person without appearing to confirm availability.
Our Grill & Thrill case study describes a native ordering app connected to kitchen operations. It is genuine Xapner hospitality work, not a Soho venue website or a table-booking case study.
For a restaurant website, keep reservations, takeaway orders and private-hire enquiries distinct. A menu update should have a named owner and a check against any downloadable copy or third-party ordering platform.
A few details worth settling before design or development begins.
Usually we can link to it or assess its supported integration. We check mobile behaviour and account access before recommending extra software.
You can offer a downloadable copy, but a readable webpage makes the essentials easier to use on a phone. Keep both versions consistent if you publish both.
Use the short form below, email or WhatsApp to describe the work. We review the brief remotely and agree deliverables, responsibilities and costs before starting. Any third-party subscriptions or ongoing support need to be included in that discussion.