Besteas - Specialty Tea Storefront
"Every tea has a bestie" - ritual-focused, sourcing-transparent, autonomously built
Top outcome
Pre-launch and technically ready end-to-end - deployed at www.besteas.com with a complete catalog, brewing ritual interaction, transparency viz, journal, and investor pitch surface; commerce wiring waits on Orchard storefront-runner integration, not on Besteas itself
Stack
Next.js 16 App Router · React 19 · TypeScript strict · Tailwind CSS 4
Overview
Besteas is a ritual-focused specialty tea storefront built on the thesis that "every tea has a bestie" - a pairing, a partner, a context that makes the cup matter. The site centers three signature surfaces that no competitor offers: the Brewing Ritual at /brew/[slug] (full-screen countdown arc with radial honey-bloom and haptic feedback), color-reactive product detail pages that tint the surrounding theme to match the brewed tea, and a transparency visualization at /partners that breaks down exactly where every $32 spent goes - from the named partner-maker upstream to the shipping line at the bottom. Master blender Bess Dallal anchors the voice with a real bio. A password-gated investor pitch surface sits behind an HMAC-signed cookie for outreach to potential partners and investors. The build is shipped by two autonomous Claude Code routines - a PM agent that picks tasks from the backlog and opens PRs hourly, and a dev-lead agent that runs a 14-gate review and merges hourly - with hard brand-voice and protected-path constraints that block any merge that violates the soul of the brand. Deployed today as a standalone Next.js front-end at www.besteas.com - pre-launch but technically ready; scheduled to migrate onto Orchard's storefront runner as one of its tenants once both go to market.
The Problem
The specialty tea category is crowded with generic DTC tropes - exit-intent popups, urgency banners, anonymous "small-batch" sourcing claims. None of it earns trust, and none of it respects the ritual that makes tea worth drinking in the first place.
The Solution
Designed and shipped Besteas as a ritual-first storefront with three signature surfaces: a full-screen Brewing Ritual at /brew/[slug] with countdown arc, radial honey-bloom, and haptic feedback; color-reactive product detail pages with a 700ms tea-color tint overlay; and a transparency visualization at /partners showing exactly where every $32 goes. Master blender Bess Dallal (real person, real bio) anchors the brand voice. A password-gated investor surface sits behind an HMAC-signed cookie.
Impact
- 1Pre-launch and technically ready end-to-end - deployed at www.besteas.com with a complete catalog, brewing ritual interaction, transparency viz, journal, and investor pitch surface; commerce wiring waits on Orchard storefront-runner integration, not on Besteas itself
- 2Password-gated investor pitch surface protected by an HMAC-signed 7-day cookie
- 3Built by autonomous Claude Code routines: hourly PM agent picks from the backlog and opens PRs; hourly dev-lead agent runs a 14-gate review and merges
- 4Scheduled to migrate onto the Orchard storefront runner once Track D ships
Key Decisions
- Designed and built end-to-end - brand conception, product strategy, interaction design, full-stack implementation, QA, photography pipeline, and operations. The autonomous Claude Code routines amplify shipping cadence with a 14-gate review
- Brand-voice guardrails are hard constraints: no exit-intent popups, no urgency banners, no fake scarcity, no generic DTC growth hacks
- Sourcing transparency is non-negotiable: named partner-makers, attributed heritage, and the $32-breakdown viz are protected paths
- Stripe wiring deliberately stubbed at v1 - real commerce waits for Orchard storefront-runner integration to avoid throwaway work
- Two autonomous Claude Code routines (besteas-pm hourly at :10, besteas-dev-lead hourly at :40) drive day-to-day shipping with a PAUSED kill-switch for interactive sessions
- Protected-paths list (pitch auth, brand voice files, product data, charters) blocks auto-merge and requires operator approval
- AI-generated photography only via the canonical PHOTOGRAPHY-PROMPTS.md - commits without prompt provenance are rejected
Lessons Learned
A brand voice survives autonomous shipping only if it is encoded as hard CI constraints, not as taste
Protected-paths gating is the difference between agents that ship work and agents that ship damage
Designing the interaction first (the Brewing Ritual) and the commerce wiring last is the right order when the storefront engine is still being built underneath you
Real attribution (Bess as the named master blender, named partner-makers throughout the sourcing chain) raises the floor for every other design decision
Screens
1 / 5