Crema Crew: Brand and Product Plan
0. Assumptions (nobody was available to ask)
- The product needs a name. Chosen: Crema Crew. Short, warm, says "coffee" and "people who turn up".
- Market is Australia (a
.com.au domain): AUD, en-AU spelling, 24h-free "9:30 am" time style, GST-inclusive prices.
- 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.
- 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.
- Pricing is illustrative: hourly rate by setup, 2 hour minimum, travel fee by distance. Sample figures only.
- No backend. Landing demo and dashboard use static sample data. Dashboard is a front-end only shadcn project.
- 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.
- 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).
- "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:
- Primary: office and workplace managers (team coffee days, client events).
- Secondary: couples and hosts (weddings, parties), and coffee-curious groups (private tastings).
- Business side: barista company owners and rosterers who need to see bookings, staff and utilisation at a glance.
Brand idea: "The good part of the morning, delivered." Warm, crafted, unfussy.
2. Brand elements
- Wordmark: lowercase "crema crew" in Fraunces (soft, high-contrast serif), with a crema-swirl glyph: a circle (cup from above) containing an S-curve in crema colour. The swirl is the logomark and favicon, built as inline SVG.
- Colour:
- Espresso
#2A1810 (text, dark surfaces)
- Roast
#5B3A29 (secondary text, borders on dark)
- Crema
#E9C99B (highlights, swirl)
- Milk
#FBF5EA (page background), Steam #F2E8D6 (cards, subtle fills)
- Ember
#D4561F (primary action; white text meets AA on it at large/bold sizes, use Espresso text on Crema for small)
- Sage
#5F7F5C (success, confirmed)
- Berry
#9B2F4B (danger), Honey #D99A1E (pending/warning)
- Type: Fraunces (display, 600) for headlines; Inter for UI and body. Scale 12/14/16/18/22/28/38/52/72, ratio about 1.25 with fluid clamp for display. Tabular numerals for money and times.
- Imagery: flat, warm illustrations in inline SVG: cart, cups from above, steam curls, grain texture overlay. Rounded, no harsh black outlines.
- Iconography: Lucide, 1.75px stroke, rounded caps, in Espresso or Ember. Never filled.
- Shape and space: radius 12px cards, 999px pills, 4px spacing base. Soft warm shadows (brown tint, never grey).
- Motion principles: (1) Pour, don't pop: ease-out curves, things settle like liquid (
cubic-bezier(.2,.8,.2,1)). (2) Steam rises: ambient motion is slow and upward. (3) Purposeful: motion explains state (confirm, select), 150 to 400 ms for UI, up to 1.2 s for ambient. (4) Always optional: reduced-motion removes movement and keeps opacity changes only at most.
3. Information hierarchy
Landing page (one page, top to bottom)
- Nav: logomark, links (How it works, Services, Pricing, For baristas), CTA "Book a barista".
- Hero: headline, subhead, primary CTA, animated cup/steam illustration with floating booking chips.
- Interactive booking preview (the product demo): choose event type, guests, date, hours; live quote and an animated confirmation card. This is the centrepiece.
- How it works: 3 steps (Choose, Book, Sip) with scroll-reveal.
- Services: 4 cards with price-from.
- Manage your bookings: mock appointment cards (reschedule, add baristas, cancel) to show the app.
- Social proof: 3 testimonials, a count-up stat row.
- Pricing note and FAQ (accordion).
- 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:
- Empty bookings: "Nothing brewing yet. Book your first barista."
- Confirmation: "You're booked. We'll bring the beans."
- Reschedule: "Plans change. Pick a new time, no fee up to 48 hours before."
- Error: "That slot just got taken. Here are three nearby times."
- Dashboard empty roster: "No baristas on this shift. Add one to take bookings."
- Loading: "Warming the grinder..."
5. Deliverables and build order
shared/tokens.css: CSS custom properties for everything above (single source for static pages).
style-guide/index.html: tokens, colour, type, spacing, components, motion demos, voice.
landing/index.html (+ landing.css, landing.js): sections above, booking preview, reduced-motion.
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.
- 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).