Verdict
The visual brief is sound. The positioning has one flaw: the hero sells breadth, the rest of the brief sells provenance.
Where the references and the brief disagree
| # | The brief says | The references show | Call |
|---|---|---|---|
| 01 | Lean strongly white; gradients "extremely pale", "physical light, not gradient mesh" | Moodboard is cream-grounded; its loudest colour is saturated orange; its colour tiles are gradient blobs | White page. Colour comes from photographs of light, never CSS blobs |
| 02 | "Not another chatbot" | The moodboard's product panel is a chat (dark bubble, "Ask a follow up…") | No bubbles. A query that resolves into an answer with numbered citations and a dated trail |
| 03 | Intelligent without looking "AI" | The ✳ spark beside "Trace"; knowledge-graph hairballs; pink-lilac glass light (Apple Intelligence) | Own mark (dot → ring). Maps with 10–20 named nodes. Pink/Lilac out of gradients |
| 04 | No page built from rounded SaaS cards | Moodboard notifications and most reference sites are card stacks | Cards only as product objects on photographs; the page is type, rules, images, diagrams |
| 05 | Glass: semi-transparent white, sparing | Two inspiration images use dark smoked glass | White bezel on product UI; real blur on two elements per page at most |
| 06 | People throughout, observed | Three of six reference sites have no people | People in every photographic moment; never faces to camera |
| 07 | Scientific notation | Moodboard coordinates (41.4126° N) mean nothing | Every number is data: dates, 14:32, counts, IDs |
| 08 | "Start tracing" / "Try Trace" / "Sign in" | Moodboard button: "Get early access" | One verb: "Start tracing →" everywhere |
| 09 | One visual world | Three images (AgentMail, Vorflux) are dark, orange, ASCII collage | Not a direction. Dotted traces and date stamps survive |
| 10 | Crucible as a reference | Its hero is the brief's hero (glass prompt over a soft flower photo) | Differ by what happens: the query resolves into a dated trail, with people |
Contradictions inside the brief
- White vs Paper. "Lean strongly white", yet Paper is listed first and the gradients end in Paper; at 1.08:1 the two read as dirty white. White is the ground.
- Apple clarity vs ~25 ingredients. Max two per section.
- Traces "selectively" vs a trace in 9 of 11 sections. One system trace per section; human marks in two places.
- "Minimal hero" (§29) vs a "first major wow moment" with photo, glass and animation (§18). Each direction chooses which way it opens.
- The serif. §10 wants "delicate, imperfect"; STK Bureau Serif is "a serif that has been through Sans school. Warm but precise." We follow the font; imperfection lives in the marker strokes.
- People "occasional" vs "throughout", both in §12. Throughout.
- "CONTEXT / 05" matches no section number; it most likely comes from the moodboard's "5" — five kinds of context.
- Project Knowledge and oversized numbers have no slot. Their numbers (214 sources · 9 interviews · 31 meetings · 6 decisions) go where the page needs a big number.
- Three capabilities restate §21 and §23. Kept, as the brief insists, but compact.
- Memory over time is claimed ("a note from three months ago") but every dated source is Sep 08–24. The Jun 24 note now appears in Connection Found.
- The same answer is written two ways ("influenced" / "later shaped"; "/" vs "·"). A provenance product can't misquote itself: one canonical string per source.
- The 14:32 quote reads like an AI summary. It becomes Trace's statement; the customer's own words are the highlighted source.
Does it read as a real technology company?
A head of product or strategy lead at a 50–500-person company would look for these first, and not find them:
- Who it is for — product, research and strategy teams.
- How it connects — read-only, inheriting source permissions. Can a question surface a private DM?
- Data handling — hosting region (the demo is an EU launch), training, SOC 2, SSO.
- Monitoring — "People" nodes plus the verb "tracing" read as employee monitoring; in Germany and the Netherlands works councils approve such tools.
- Setup time — ironic, since the demo story is about customers stalling on implementation time.
Built in: tiny annotations on the integrations diagram (Read-only connectors · Respects source permissions · EU or US hosting · Never used for training · SOC 2 Type II), the demo labelled as a customer workspace (Larkfield · EU Launch), Project Knowledge numbers, a real footer.
UX risks and the rule each direction follows
| # | Risk | Rule |
|---|---|---|
| 01 | Context map unreadable on a phone and opaque to screen readers | Ordered list of the same nodes on mobile; map data always in the DOM |
| 02 | Hover-only reveals on touch and keyboard | Every hover has a tap and focus equivalent |
| 03 | Glass over photo and video hurts legibility | Text on ≥85 % white; refraction only as enhancement; video paused off-screen |
| 04 | Autoplaying typed answers | Play on visibility, finish in ≤2.5 s, no endless loops, replayable; reduced motion shows the final state |
| 05 | Pastel signals as strokes (Butter 1.41:1 on white) | Signals are fills; strokes use ink tones (≥4.7:1) |
| 06 | Fake forms collecting real emails | Pre-filled demo, nothing sent or stored, clear success state |
| 07 | Scroll-jacking | Native scroll only; pinned stages are sticky, never hijacked |
| 08 | Page length | ≤ ~10,000 px on desktop |
Copy: what changes and what doesn't
Kept verbatim
Every headline, statement, eyebrow and CTA in brief §18–28.
Changed for consistency
One name and date format per source (Customer Interview 07 · Sep 12); one primary verb ("Start tracing →"); the phantom "Meeting / Sep 18" becomes the Sep 15 positioning workshop; the 14:32 quote as the customer's own words.
Added, small and flagged
Data-handling annotations, Project Knowledge numbers, the Jun 24 note, a real footer.
Recommendation for the client — not built
Lead with provenance: "Follow the thinking." as the hero, "Think with everything you know." as the sub-line or the finale.
Typography
STK Bureau Serif (Smuss Type Kiosk) and Suisse Int'l are commercial; trial files can't ship on a public URL. Each direction uses a free, self-hosted pairing, so the five also compare type.
| V | Grotesk | Serif | Why |
|---|---|---|---|
| 1 | Switzer | Roboto Serif Light | Nearest to Suisse; the closest skeleton to Bureau Serif |
| 2 | Host Grotesk | Sentient Light | Warmer, Neue Montreal-like; a softer serif for a photographic direction |
| 3 | Mona Sans + DM Mono | Piazzolla Light | Width axis for notation; the "imperfect" serif |
| 4 | Switzer | Literata Light | Neutral map labels; the warmest serif for statements |
| 5 | Inter | Roboto Serif Light | Product-grade UI face; serif only in the finale |
Five directions
The brief fixes the order, copy, palette and photo language, so the five differ in how you move through the same story. All share one demo story — Larkfield's EU launch — and one product UI kit.
Trail
One line, followed from the first question to the last CTA. It draws itself as you scroll and ends by drawing the dotted E.
scroll-drawn pathOpen V1 →
Light Table
One product panel stays; the world behind it changes. Glass as the layer between the person and their information.
pinned morphing panelOpen V2 →
Field Notebook
A dated research notebook: a date rail, footnotes that open their sources, and a few human marks.
date rail + footnotesRetired after review
Atlas
The context map is the page. Scroll moves a camera across one chart of time and kinds of context.
scroll cameraRetired after review
Workspace
The homepage behaves like the product: three questions drive every demo on the page.
visitor-driven threadsOpen V5 →
Considered and dropped: a dark, orange, dot-matrix direction built on the AgentMail/Vorflux images. It contradicts "lean strongly white"; its dotted trace lives on in the finale.