The challenge
Tikka Terminal is an Indian restaurant at Beim Bahnhof 2 in Neuenburg am Rhein, running four things at once: dine-in, takeaway, catering and an attached bowling alley. A restaurant site has a different job from a store — nobody checks out, and the entire site succeeds or fails on whether a hungry person on a phone can see the menu, book a table or place a phone order in under a minute. Two things made it harder here. The menu is not one menu: there is a weekday lunch card served 11:00–14:00 and a full dinner card from 17:00, and showing the wrong one at the wrong time of day is the fastest way to lose a booking. And the audience is split — German-speaking regulars from the town, and visitors who need English.
What we did
- Built the site around the two things that actually convert — 'Tisch reservieren' and 'Telefonisch bestellen' — kept in reach on every screen rather than parked on a contact page.
- Split the menu into its own destinations, Speisekarte and Mittagskarte, so the weekday lunch card is a page a regular can go straight to instead of hunting for it inside the full menu.
- Delivered the site bilingually, German first with an English toggle, so the local audience gets its own language and visitors are not locked out.
- Gave the bowling alley its own section rather than a line in the footer — it is a second reason to come and a second occasion to book, and burying it wastes it.
- Built the story and gallery sections to carry the 'Indien trifft Herzlichkeit' positioning, with room for real photography of the room, so the site sells the evening and not just the food.
- Structured it mobile-first, because a restaurant site is read almost entirely on a phone, usually by someone already deciding where to eat tonight.
The results
How we would approach yours
Every engagement starts the same way: a free audit of the store as it stands today — speed, technical SEO, checkout friction and paid efficiency — followed by a prioritised roadmap that puts effort against expected impact. You keep the findings whether or not we go further.
From there the work runs in weekly sprints against a live staging link, on fixed scope, with design, development and marketing in one team. That last part is why a conversion problem gets diagnosed once here rather than being passed between two agencies who each think it belongs to the other.