What Harriet could feel like for a hybrid hospitality business: one mobile worker understands restaurant hours, weekly menus, hotel rooms, photos, and multilingual guest information.
Kafischnaps combines a café, bar, restaurant, and five-room hotel in one Zürich neighbourhood business. Its live site spans weekly menus, restaurant hours, rooms, booking links, events, and German–English content.
Unofficial exploratory concept based on publicly visible content from kafischnaps.ch and internal lead data captured in August 2026. Kafischnaps has not endorsed or approved this presentation. Proposed migration results and app health scores are illustrative.
Harriet should preserve Kafischnaps’ bold identity, food and room photography, German voice, weekly menus, and booking links. The owner experiences a capable colleague—not a replacement brand or a technical dashboard.
Terrace notices, event dates, photos and menus—not commits, builds and branches.
A visual result comes before implementation details or technical logs.
Harriet prepares. The owner previews and explicitly publishes.
Plain-language history makes restoration feel safe and ordinary.
The left screen is the live Kafischnaps website captured while creating this concept. The right screen imagines the Harriet handoff using the same domain, visual identity, photography, and German voice.
The first screen uses Kafischnaps’s real logo, photography, domain, and German copy. The owner should recognize the business before learning anything about Harriet.
A Sunday-hours update becomes a short German request. Harriet understands which restaurant pages matter while leaving hotel and room information untouched.
Owners see outcome-oriented steps: what Harriet found, changed and checked. They can leave the app and return when the preview is ready.
The preview combines the proposed notice with Kafischnaps’s real interior photography and identity. The owner sees the customer-facing result before deliberately publishing.
Restaurant hours, weekly menus, room content, and gallery updates become understandable business history.
Harriet’s technical differentiators—isolated agents, Git history, customer-owned hosting and portable source—become understandable customer promises.
Each customer’s agent and website run in an isolated workspace.
Production changes require a deliberate action from an authorized owner.
Every change is stored and an earlier revision can be restored.
Source and hosting belong to the customer and survive Harriet.
Avoid the temptation to mirror every backend object. The first app can remain extremely small.
Will owners trust a conversational request without seeing technical details?
Is a visual preview plus plain-language summary enough confidence to publish?
Do voice and quick requests reduce anxiety for people unfamiliar with AI?
Does website health create recurring value beyond occasional content updates?
Can customers understand revision restoration without Git vocabulary?
Which fixed interface terms need different phrasing in Bulgarian and German?