A heritage tea brand returns to the shelf.
Forty years of reputation, a shrinking shelf presence, and a product no younger buyer could explain. This concept explores how strategy, packaging and a simple commerce site answer that — end to end.
The brief
- Discipline
- Brand strategy, packaging, website
- Sector
- FMCG — specialty tea
- Status
- Concept exploration, not a shipped client project
The challenge
The brand had everything a newcomer wants — heritage, direct grower relationships, a taste regulars defend — and everything its shelf didn't show. Younger buyers met it as "our parents' tea": trustworthy, and invisible. Imports with better stories were eating the gift aisle.
The approach
We started with one sentence of positioning the growers themselves could verify — "tea that remembers who grew it." Every later decision had to defend that sentence. Packaging moved from decorative to documentary: origin, harvest, the person's name. The website's job became explaining, beautifully, in three minutes what forty years couldn't communicate in a label square inch.
The design system
Warm paper palette, a single editorial serif, one signal color reserved for the harvest story. A token set small enough to survive the printer, the shopfront, and a Bangla/English bilingual lockup without breaking either.
Development sketch
WordPress for the editorial side (harvest journals are the content engine), static marketing pages for the story, and a store layer the existing distributor could actually operate.
Visual exploration
Placeholders stand in for licensed photography; see assets/images/README.md.
What this concept demonstrates
- Positioning written to be falsifiable — one sentence, then every asset defends it.
- Strategy, packaging and site built as one system instead of three briefs.
- Honest labeling: no invented sales lifts, no fake client quotes, no "300% growth" numbers we can't source.
Verified outcomes will appear here when real projects ship. Until then this page shows process, and only process.
Curious what this does for your situation?
More concepts on the work page — or bring us the problem this one solves.