Xandrov StudioAtlas of shipped systems
← The territory/ V. Brand & Web/ № 19 — Kiwi Spa
Dossier № 19 / 19 — Brand & Web — Speculative pitch · Labeled as such

Kiwi Spa — Website Redesign

The proposal was the product.

File
№ 19 / 19
Territory
Brand & Web
Classification
Speculative pitch · Labeled as such
Status
Speculative concept, clickable
§ 01 Context

Kiwi Spa is a luxury day spa. A speculative, unsolicited pitch delivered a complete website redesign to the owner — labeled plainly as speculative, everywhere it appears. Cold proposals are dismissed easily because they cost the sender nothing and carry no consequence of rejection. The alternative: build a working prototype from information already public — published prices, hours, location, brand story — and demonstrate capability through the product itself. The coded concept becomes evidence of both seriousness and skill.

§ 02 The problem

Cold-outreach proposals are easy to ignore. A written deck costs nothing to dismiss. But a coded website working in the browser, built from public facts alone, poses a different question: how serious is the sender? How capable? The challenge: prove both without crossing into dishonesty — no fabricated testimonials, no fake before-and-afters, no invented metrics. Every design choice must trace back to facts already in the public record. The result is the evidence. A clickable concept that works.

§ 03 The approach

The pitch went through three full iterations, converging on version 3. The design system uses Cormorant Garamond for display type and Jost for interface; both choices reflect the spa's brand story and luxury positioning. A persistent mobile booking bar occupies the thumb zone — the area a one-handed user can actually reach on a phone screen. The service menu is price-laddered: a two-path decision funnel separates ready-to-buy customers from first-timers uncertain about day-spa services. Local-SEO structure includes DaySpa JSON-LD schema, routing traffic to the correct business entity.

A build-spec document serves as the single source of truth: brand facts, verbatim header and footer markup, approved imagery, copy voice rules. This keeps a multi-page hand-built site consistent across iterations and phases. A separate written strategy document explains every design decision — the reasoning, not just the artifact. Both documents — the spec and the strategy — are authored before a single line of HTML ships.

Cold-outreach proposals are easy to ignore. A coded website is harder to dismiss.

§ 04 Decisions that mattered
D1
No fabricated evidence
Stock photography only, explicitly marked for replacement, with no fake before-and-afters. Every image flags its placeholder status.
D2
Build spec as source of truth
A single master document governs brand facts, layout markup, approved imagery, and copy voice rules across every page. Consistency is designed in, not hoped for.
D3
Labeled speculative everywhere
The pitch is plainly stated as unsolicited, speculative work — not a paid engagement. Status honesty is the point of the exercise.
D4
Hand-built HTML, no framework
Written in plain HTML, CSS, and JavaScript with no build tool or framework. The code itself is the portfolio.
D5
Persistent mobile booking bar
A booking interface anchors to the thumb zone — the area a one-handed user can reach on mobile. The call-to-action stays reachable as the user scrolls.
§ 05 Where it stands

The version-3 concept is published as design and conversion-strategy collateral, clickable and live. This is speculative pitch work, not a paid client engagement — that status is stated plainly. The work demonstrates a studio's capability: converting unsolicited research into a coded, honest, working prototype; building a complete site from public information without fabrication; and writing the reasoning alongside the code.

HTML / CSS / JSNo frameworkJSON-LD schemaConversion strategy
§ 06 — Sanitization record

No credentials, client responses, or prospect list are published. No metrics — no traffic, conversion, or engagement data — because this is a prototype, not a live deployment. Spa contact details are withheld; the published version uses a placeholder email. Fabricated evidence (before-and-after comparisons, testimonials, user counts) was never created in the first place.

Have a system like this worth building?

Fixed scope, quoted after one working session, first output inside two weeks. Read by a person within one working day.