What Harriet could feel like for an Italian restaurant: replace a holiday closure notice with today’s reopening, review it against the real Azzurro brand, and publish from an iPhone.
Ristorante Azzurro is an active Italian restaurant in Zürich with a live German site, reservation flow, PDF menu, restaurant and garden photography, and time-sensitive notices such as its current reopening after annual holidays.
Unofficial exploratory concept based on publicly visible content from ristoranteazzurro.ch and internal lead data captured in August 2026. Azzurro has not endorsed or approved this presentation. Proposed migration results and app health scores are illustrative.
Harriet should preserve Azzurro’s Italian red–green identity, food and garden photography, German voice, menu, and reservation flow. 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 Azzurro 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 Azzurro’s real logo, photography, domain, and German copy. The owner should recognize the business before learning anything about Harriet.
The live website already carries a time-sensitive August 15 reopening message. Harriet turns that real operational moment into a concise, reviewable mobile workflow.
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 Azzurro’s real interior photography and identity. The owner sees the customer-facing result before deliberately publishing.
Reopening notices, menu cards, pizza photography, and reservation 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?