The problem, the decisions, and what we actually built.

The problem

Most independent restaurants are found on a phone, at 7pm, by someone deciding where to eat in the next twenty minutes. That person wants four things: the menu, whether you are open, where you are, and how to book. Typical restaurant sites bury all four behind a slow homepage, a PDF menu that will not open on mobile, and a contact form nobody checks.

The solution

A mobile-first site where the menu, hours, location, and booking are reachable in one tap from anywhere on the page. The menu is real HTML — readable, searchable, and indexable by Google — not a scanned PDF. Booking goes to WhatsApp, because that is the channel a restaurant actually answers.

What we built

• Single-page structure so nothing needs a second page load
• Full menu with categories, dietary markers, and prices as structured content
• Reservation form that composes a pre-filled WhatsApp message
• Live open/closed indicator computed from opening hours
• Gallery, location map link, and click-to-call in the sticky mobile bar
• Restaurant schema.org markup for rich results in Google

Intended outcome

• Designed so a hungry visitor can see the menu within one tap of landing
• Designed to turn a phone visit into a WhatsApp booking without a form reply cycle
• Built to be indexable by dish name, so menu items can surface in local search

Written as design intent. This is a concept project, so there are no live traffic or conversion figures to report — and we will not invent any.

The problem

Property buyers filter before they browse. They know their budget, their bedroom count, and their two or three preferred areas. An agency site that shows twenty properties in a fixed grid forces the buyer to do the filtering by hand — so they leave and go back to the portal, where the agency is one of forty competing listings.

The solution

A listings experience with instant client-side filtering across type, location, budget, and bedrooms, plus a detail page per property with the information a serious buyer needs before enquiring. Every property has its own enquiry form that carries the property reference with it, so the agent knows what the enquiry is about before opening it.

What we built

• Filterable listings grid with instant, no-reload results
• Per-property detail pages with specification, amenities, and location context
• Enquiry form pre-tagged with the property reference
• Agent profile with direct call and WhatsApp
• Shortlist counter and empty-state handling
• RealEstateListing schema.org markup

Intended outcome

• Designed to keep buyers on the agency site instead of returning to a portal
• Designed so every enquiry arrives already attached to a specific property
• Built to make a twenty-property catalogue navigable in seconds on a phone

Written as design intent. This is a concept project, so there are no live traffic or conversion figures to report — and we will not invent any.

The problem

Professional practices lose time on enquiries that were never a fit, and lose clients who could not tell whether the firm handles their specific situation. A generic "we offer accounting services" page answers neither question, so every enquiry starts from zero on a phone call.

The solution

A site organised around the client’s situation rather than the firm’s service list, with a short qualifying enquiry flow that captures entity type, turnover band, and the service needed before the first call. The consultation request arrives with enough context that the first conversation can be about the work.

What we built

• Services structured by client situation, with clear scope per service
• Compliance calendar showing key filing dates
• Multi-step consultation request that qualifies as it collects
• Team credentials and professional registration details
• FAQ addressing the questions that otherwise consume the first call
• ProfessionalService schema.org markup

Intended outcome

• Designed so an enquiry arrives with entity type, size, and need already known
• Designed to let a prospect self-identify in under thirty seconds
• Built to reduce the number of unqualified first calls

Written as design intent. This is a concept project, so there are no live traffic or conversion figures to report — and we will not invent any.