Platform · Phase 0 mockups

Static HTML. White-label: the brand is a single --accent token in assets/tokens.css. All copy in English, new domain vocabulary, no legacy brand.

Login — pick a direction decide first
Style A · Slate neutral
Centered card, one accent. Safest white-label.
Style B · Warm editorial
Paper, serif headline, underline fields.
Style C · Dark-first
Dark canvas, glass card, accent glow.
App screens — Style A · Slate neutral draft
Dashboard
KPIs + recent activity + open vacancies
Talent — list
Seniority, skills, rate, availability, rating
Talent — detail
Profile, skills, experience, submissions, notes
Vacancies — list
Organization, seniority, remote, priority, status, due
Vacancy — detail
Requirement + pipeline kanban (10 stages)
App screens — Style B · Warm editorial draft
Dashboard
KPIs + recent activity + open vacancies
Talent — list
Seniority, skills, rate, availability, rating
Talent — detail
Profile, skills, experience, submissions, notes
Vacancies — list
Organization, seniority, remote, priority, status, due
Vacancy — detail
Requirement + pipeline kanban (10 stages)

Same HTML + assets/app.css for both — only the <body> theme class differs (.theme-slate.theme-editorial). Each screen has an A/B/W toggle (bottom-right).

App screens — Warm · people-first new direction
Dashboard
KPIs + recent activity + open vacancies
Talent — roster
Grouped by human availability, faces first
Talent — profile
Person-centred, “where they stand” timeline
Vacancies — searches
Human framing + pipeline meter
Vacancy — detail
Brief + pipeline as a 10-stage journey

A genuinely different layout, not a reskin: top-bar nav (no cold left rail), a roster grouped by availability instead of a table, warmth from one --accent + a single light-wash — on crisp white, not beige.

Client Portal — sign in C chosen
C · Editorial ✓
No card. A spread: big serif sentence beside underline fields. This is the one.
A · Split
Deep petrol panel + white form. Kept as the record.
B · Quiet
Centred column, colour on a hairline. Kept as the record.
Client Portal — screens draft
Dashboard
What waits on the client, where each search stands, what is coming up
Richieste — list
Grouped by who holds the ball: waiting on you, running, paused, closed
Richiesta — detail
The search, its shortlist, the conversation
Nuova richiesta
The form a client opens a search with

Shell in assets/portal-app.css: the login's masthead-and-rule carried into the app, sections opened by a caps line instead of boxed in cards, and rows rather than a card grid — a card grid makes eight searches look like eight products on a shelf and forces them all to one height. Dropped from the legacy dashboard: revenue YTD and acceptance rate, which are agency metrics a client cannot act on, and the five equal-weight KPI cards that hid the day's work.

The portal is the same product from the client's side, so it keeps the house shapes (Fraunces headlines, pill buttons, crisp white) and changes one thing: a fixed petrol accent in assets/portal.css — opposite the internal terracotta on the wheel. A client never gets a theme picker: for them the colour is not a preference, it is which door they came through. Copy is Italian here, unlike the internal mockups — this is the one screen a client reads before anything else.