Pullup: brand, system and build plan

Status: approved by default. Nobody was available to answer questions, so every open point below is a written assumption (section 0) rather than a question.

0. Assumptions

  1. Name: the brief gave none. Working name Pullup ("pull a shot", "pull up a cart"). Short, speakable, domain-friendly. Easy to rename: it lives in one wordmark SVG and one string table.
  2. Market: Australia first. AUD, GST-inclusive prices, Australian spelling (colour, organise), 24h clock off, 12h on ("2:30 pm"). Pricing figures are demo data and labelled synthetic.
  3. Two sides: customers book through a web app (mobile first); the business (the operator running baristas and carts) uses the dashboard. The landing sells the customer app and has a short "for operators" band.
  4. Offer model: three bookable experiences: Cart (one barista, compact cart, up to 60 guests), Bar (two baristas, full bar, up to 200 guests), Tasting (private, seated, 6 to 14 guests, guided). Add-ons: oat and almond milk, matcha, cold brew tap, branded cups.
  5. Booking rules: minimum 2 hour service window, 90 min setup, free changes until 48 h before the start. Quote is live and itemised.
  6. No real photography is available. Imagery is authored: SVG illustration of carts and cups, plus generative latte-art and steam motion. No stock photos, no invented testimonials. Social proof on the landing is clearly labelled sample data.
  7. Build path: code-led (Operate for dashboard, Persuade for landing, Read for style guide). The decision page and comp round were skipped because they need a human; direction is pinned below.
  8. Stack: landing and style guide are dependency-free static HTML/CSS/JS sharing shared/ tokens and fonts. Dashboard is the existing Vite + React + shadcn (base-nova) project, themed by mapping the same tokens onto shadcn CSS variables.

1. Brand

Positioning. Pullup is the easiest way to get a real barista, and the bar they bring, to wherever your people are. Not a coffee shop, not a catering marketplace: a booking tool that treats a morning at the office or a 40-guest launch like an appointment you can see, change and trust.

Audience.

Promise. Certainty, with a bit of theatre. Pick, confirm, done. Then the coffee shows up on time.

Personality. Warm, quick, dry. A barista who remembers your order and does not make a speech about it. Confident, never precious. Never "artisanal", never "elevate".

2. Brand elements

World (own-world). Italian enamel cart signage meets a booking confirmation: a saturated cobalt field, crema-yellow highlights, ink-dark type, cool milk-white ground. Deliberately not the cream, serif and terracotta coffee default. The scene: a phone in one hand in bright daylight outside an office, so contrast is high and light is the base theme.

Wordmark. Lowercase pullup in Bricolage Grotesque ExtraBold, tight tracking. Companion mark: a cup seen from above (cobalt ring, crema disc, handle rendered as an upward tick). Minimum size 20 px high. Clear space equals the height of the "u". Never on busy imagery, never recoloured outside cobalt, ink, milk and crema.

Colour (OKLCH, committed strategy: cobalt carries 30 to 60% of branded surfaces).

Token Value Use
cobalt-600 oklch(0.46 0.19 264) primary, brand fields
cobalt-700 oklch(0.37 0.17 264) hover, deep fields
cobalt-100 oklch(0.93 0.04 264) tints, selected rows
crema-300 oklch(0.88 0.13 90) highlight, key action on cobalt
crema-500 oklch(0.78 0.15 78) charts, warm accent
ink-900 oklch(0.2 0.03 265) text
ink-500 oklch(0.5 0.03 265) secondary text (4.5:1 on milk)
milk-50 oklch(0.985 0.006 255) page ground
steam-100 oklch(0.955 0.01 255) panels
leaf-600 oklch(0.52 0.13 155) confirmed, success
chilli-600 oklch(0.55 0.2 27) cancelled, error
Status colours always pair with a word or icon.

Type. Display: Bricolage Grotesque (variable, self-hosted), weights 600 to 800, tracking -0.03em, balanced wrapping, max 6rem. Body and UI: Geist (variable, already in the dashboard), 400 to 600. Numerals tabular in tables and quotes. Scale (1.25 ratio, fluid at the top): 12, 14, 16, 20, 25, 31, 39, 49, 61 to 96 clamp.

Imagery. Authored vector scenes: cart elevations in flat cobalt/crema/ink shapes, top-down cups with generated latte-art patterns, steam as animated paths. Real photography is a to-supply asset (see section 7). All illustration uses 2px round-cap strokes plus flat fills, no gradients.

Iconography. Lucide, 1.5px stroke at 20px, round caps. Custom glyphs only for cup, cart, bar, tasting (drawn to match). No emoji.

Motion principles. 1) Motion explains state: things pour, fill and slide into place where the data changes. 2) One authored moment per view (landing: the cup that fills as you configure). 3) Ease-out expo cubic-bezier(0.16,1,0.3,1), 150 ms for feedback, 300 ms for layout, 600 to 900 ms for the signature moment. 4) Everything starts visible; animation is enhancement. 5) prefers-reduced-motion removes movement, keeps state changes as instant or fades.

3. Information structure

Landing (Persuade). One job: get an organiser to start a booking.

  1. Header: wordmark, How it works, Experiences, For operators, FAQ, primary "Book a barista".
  2. Hero: headline, one-line promise, and the interactive booking preview (pick experience, guests, date, time; live quote; cup fills with the guest count; "confirm" plays a confirmation ticket). This is the first-viewport thesis: the product does its job in the hero.
  3. Drink-name marquee strip (motion, pausable, static under reduced motion).
  4. How it works: three steps with an animated stepper (choose, confirm, relax).
  5. Experiences: a selectable list (Cart, Bar, Tasting) that swaps an illustrated scene and spec sheet. Not three identical cards.
  6. Manage it: an interactive appointment ticket you can reschedule or cancel in place (shows the post-booking app).
  7. Sample voices (labelled sample) and reliability facts as plain statements, not a metric grid.
  8. For operators: dashboard screenshot-style mock and the one-line pitch.
  9. FAQ (details/summary).
  10. Close: cobalt field, "Your next meeting needs a barista." CTA. Footer.

App (customer, described in the landing demo). Tabs: Book, My bookings, Account. Booking flow: experience, details (date, time, guests, address), add-ons, review quote, confirm. Booking detail: status, barista, setup time, change/cancel, add to calendar, message.

Dashboard (Operate). Left sidebar: Overview, Schedule, Bookings, Roster, Revenue (all five are anchors to sections of one scrolling overview page; the active item follows scroll). Overview order of importance: 1) alert for unassigned bookings, 2) stat strip, 3) week schedule with roster and utilisation, 4) upcoming bookings (capped at 6, show all), 5) revenue. The first draft ranked upcoming bookings first; the build leads with the actionable alert and the schedule because "who is where" is the daily question, then keeps the capped bookings table above the fold on most screens. Task frequency: daily glance, weekly planning. Scanability over expression.

4. Voice, tone and sample copy

Voice. Plain, warm, a little dry. Short sentences. Verbs first. Numbers over adjectives. Australian spelling. No exclamation marks outside confirmations, no puns in errors. Tone dial. Marketing: confident and playful. Booking flow: calm and exact. Errors: direct, apologise once, offer the fix. Operator dashboard: terse and factual.

Headlines.

Microcopy.

5. Direction contract (development only, not shipped)

THESIS: the booking tool is the hero; the page proves the product by letting you book a barista in the first viewport. Refuses: stock coffee photo hero, cream-and-serif café mood, icon-card grid. OWN-WORLD: cobalt enamel fields, crema-yellow action and highlights, ink type, milk ground, 2px ink outlines on tickets, 14px radii, ticket-stub perforation motif, no gradients, no glass. STORY: organiser understands "real baristas, booked like an appointment", believes the quote is exact and changing is easy, and starts a booking. FIRST VIEWPORT: left 55%: display headline (up to 6rem), sub, and CTA row; left column also carries a 200px animated cup beneath the facts; right 45%: the booking-preview ticket on the cobalt field. The cup fills as guests are added. Primary action in the ticket and the header. FORM: single-page product landing with a live booking widget (the brief offered an interactive booking preview as an example). The concept roll and decision page were skipped because they need a human to choose and nobody was available, so this direction is the builder's own call, not a pinned or rolled one. seed: none (unavailable). FINISH: unreviewed and undocumented is unfinished; this build ends with the finish review, the verdict, DESIGN.md, and every shipping raster carrying its provenance.

6. Build plan

Shared system: shared/tokens.css (colour, type, space, radius, shadow, motion), shared/base.css (reset, fonts, type, focus, selection, scrollbar), shared/components.css (button, field, chip, badge, ticket, tabs, toast), shared/fonts/, shared/brand.svg.

Tasks:

  1. Shared tokens, fonts, components. Verify: opens, no 404 on fonts.
  2. style-guide/index.html: tokens, colour, type scale, spacing, radius, elevation, components with live states, motion demos (with reduced-motion toggle), voice and copy, logo rules. Verify: screenshots desktop and mobile.
  3. landing/: index.html, landing.css, landing.js (booking preview state machine and quote function, experience switcher, appointment ticket, stepper, marquee, reveal). Verify: quote maths via a node check, interactions in browser, reduced motion, 375 and 1440 widths.
  4. dashboard/: map tokens to shadcn variables in src/index.css; add shadcn components (sidebar, card, badge, table, avatar, tabs, progress, tooltip, separator, button); build src/data.ts (synthetic data), Overview, ScheduleWeek, BookingsTable, Roster, RevenueChart (SVG), UtilisationBars. Verify: npm run typecheck, npm run build, screenshots.
  5. Review: detector, one fresh finish review, DESIGN.md.

7. To supply later

Real photography of actual carts and baristas, real logo lock-up if the name changes, real pricing, real testimonials, payments and calendar integrations (the demo is front-end only).