Unofficial client concept · Live lead 01

# Azzurro has a new colleague.

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.

Live business in Zürich German owner experience Owner-approved publishing No lock-in
Why Azzurro

## A real business makes the product question concrete.

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.

4.3★Google rating across 1,410 reviews in the lead dataset
Top 3 the restaurant’s stated Swiss pizzeria ranking
100 static-fit score from Harriet’s lead qualification
658 ms homepage response measured by the lead finder

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.

Design position

## Still Azzurro.
Now easier to run.

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.

01

### Speak like an owner

Terrace notices, event dates, photos and menus—not commits, builds and branches.

02

### Show, then explain

A visual result comes before implementation details or technical logs.

03

### Nothing goes live alone

Harriet prepares. The owner previews and explicitly publishes.

04

### Every action is reversible

Plain-language history makes restoration feel safe and ordinary.

The golden path

## From a passing thought to a safe live change.

01 Ask Text, voice, photo or document
02 Confirm Harriet restates the outcome
03 Work Visible progress, no technical noise
04 Review Visual preview and change summary
05 Publish Explicit owner approval
06 Restore Any earlier revision, one tap
Current site → Harriet

## Start with what the owner already recognizes.

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 goal is not to erase the existing brand. It is to make that brand easier for its owner to operate.
00 · The handoff

## Their identity, already inside.

The first screen uses Azzurro’s real logo, photography, domain, and German copy. The owner should recognize the business before learning anything about Harriet.

!This assumes Harriet invitations are sent only after an AI-generated migration has passed human review.
01 · Ask naturally

## “We reopen today at 18:00.”

The live website already carries a time-sensitive August 15 reopening message. Harriet turns that real operational moment into a concise, reviewable mobile workflow.

1 Voice is visually first-class because owners are likely to use Harriet while moving between daily tasks.
02 · Work visibly

## Confidence without a terminal.

Owners see outcome-oriented steps: what Harriet found, changed and checked. They can leave the app and return when the preview is ready.

2 Progress is intentionally honest but non-technical. Exact time promises should only appear when the backend can support them reliably.
03 · Review & publish

## Actual brand. Explicit decision.

The preview combines the proposed notice with Azzurro’s real interior photography and identity. The owner sees the customer-facing result before deliberately publishing.

3“Nothing is live until you approve it” should become a repeated product promise, not fine print.
04 · Remember & improve

## Restaurant history, not Git history.

Reopening notices, menu cards, pizza photography, and reservation updates become understandable business history.

4 Proactive suggestions can demonstrate recurring value, but they never publish themselves.
Trust architecture

## The interface reflects the operating model.

Harriet’s technical differentiators—isolated agents, Git history, customer-owned hosting and portable source—become understandable customer promises.

H

### Private worker

Each customer’s agent and website run in an isolated workspace.

✓

### Approval gate

Production changes require a deliberate action from an authorized owner.

↶

### Full history

Every change is stored and an earlier revision can be restored.

↗

### Always yours

Source and hosting belong to the customer and survive Harriet.

MVP information architecture

## Three places, one job.

Avoid the temptation to mirror every backend object. The first app can remain extremely small.

01 Home Website status, primary request composer, and common tasks.
02 Requests Conversations, active work, previews and decisions awaiting the owner.
03 History Published revisions, previews and restoration controls.
+Website Care Reachable from Home; health and optional optimization suggestions.
What this concept should test

## The screens are a hypothesis, not a specification.

01

Will owners trust a conversational request without seeing technical details?

02

Is a visual preview plus plain-language summary enough confidence to publish?

03

Do voice and quick requests reduce anxiety for people unfamiliar with AI?

04

Does website health create recurring value beyond occasional content updates?

05

Can customers understand revision restoration without Git vocabulary?

06

Which fixed interface terms need different phrasing in Bulgarian and German?