Crema Crew: Brand and Product Plan

0. Assumptions (nobody was available to ask)

  1. The product needs a name. Chosen: Crema Crew. Short, warm, says "coffee" and "people who turn up".
  2. Market is Australia (a .com.au domain): AUD, en-AU spelling, 24h-free "9:30 am" time style, GST-inclusive prices.
  3. Two sides: customers book through the app; the business (a barista company) runs it through the dashboard. The landing page sells to customers, with a small "run a coffee business? " strip for operators.
  4. Service catalogue (sample data): Office Espresso Bar, Wedding and Event Cart, Private Tasting (cupping), Pop-up Bar (large). Each includes 1 to 3 baristas plus a cart or bar setup.
  5. Pricing is illustrative: hourly rate by setup, 2 hour minimum, travel fee by distance. Sample figures only.
  6. No backend. Landing demo and dashboard use static sample data. Dashboard is a front-end only shadcn project.
  7. Static pages (style guide, landing) are plain HTML/CSS/JS with no build step, sharing shared/tokens.css. Dashboard uses the existing Vite + React + shadcn (base-nova) project.
  8. Fonts load from Google Fonts for static pages (Fraunces, Inter) and from fontsource for the dashboard, with system fallbacks. Imagery is illustrated in inline SVG (no stock photos can be fetched).
  9. "Reduced motion" means prefers-reduced-motion: reduce removes all non-essential animation everywhere.

1. Brand

Name: Crema Crew. Tagline: "Fresh coffee, brought to you." Positioning: The easiest way to book a real barista, with the cart, for any gathering. Café quality without the café. Book in under a minute, change your mind without a phone call. Audience:

2. Brand elements

3. Information hierarchy

Landing page (one page, top to bottom)

  1. Nav: logomark, links (How it works, Services, Pricing, For baristas), CTA "Book a barista".
  2. Hero: headline, subhead, primary CTA, animated cup/steam illustration with floating booking chips.
  3. Interactive booking preview (the product demo): choose event type, guests, date, hours; live quote and an animated confirmation card. This is the centrepiece.
  4. How it works: 3 steps (Choose, Book, Sip) with scroll-reveal.
  5. Services: 4 cards with price-from.
  6. Manage your bookings: mock appointment cards (reschedule, add baristas, cancel) to show the app.
  7. Social proof: 3 testimonials, a count-up stat row.
  8. Pricing note and FAQ (accordion).
  9. Final CTA and footer (operator strip: "Run a barista business? See the dashboard").

Customer app (described, shown via landing demo)

Home (next booking, quick rebook) > Book (type, when, where, extras) > Quote and confirm > My bookings (upcoming, past, manage) > Account.

Dashboard (business)

Sidebar: Overview, Bookings, Schedule, Baristas, Reports, Settings. Overview order: stat cards (revenue, bookings, utilisation, avg. booking value) > revenue chart + utilisation by weekday > upcoming bookings table > week schedule > barista roster with status.

4. Personality and copy

Voice: friendly, warm, a bit cheeky, always clear. Like a barista who remembers your order. Tone dial: playful on landing, calm and exact on confirmations, plain and fast in the dashboard. Never use puns in errors. Do: short sentences, verbs first, real numbers. Don't: "revolutionary", exclamation spam, jargon, em-dashes.

Headlines: "Fresh coffee, brought to you." / "Your event, properly caffeinated." / "Book a barista in under a minute." CTAs: "Book a barista", "See a quote", "Reschedule". Microcopy:

5. Deliverables and build order

  1. shared/tokens.css: CSS custom properties for everything above (single source for static pages).
  2. style-guide/index.html: tokens, colour, type, spacing, components, motion demos, voice.
  3. landing/index.html (+ landing.css, landing.js): sections above, booking preview, reduced-motion.
  4. dashboard/: theme src/index.css to the palette (oklch of tokens), add shadcn components (card, badge, table, avatar, progress, tabs, separator), build Overview page with sample data.
  5. Verify: dashboard npm run build and typecheck, serve static pages and check they load, review reduced-motion CSS.

A detailed task plan was kept separately (not included).