Farmley

UX Design · Brand Strategy · Shopify · Dev Coordination

One Brand. Many Worlds.

Redesigning Farmley.com to hold a house of brands without losing what makes each one distinct.

Role
UX Design · Visual Design · Brand Strategy
Platform
Shopify — Metro Theme
Timeline
Dec 2024 → Feb 2025 (MVP)
Live Site

01 — Context

A brand that had evolved.
A website that hadn't.

Farmley started as a dry fruits and nuts brand. By the time this project began, it had grown into something more complex — a mother brand with an established sub-brand (Date Bites) and a new one in the pipeline (Maka Shaka, timed for an IPL launch in March 2025).

The website hadn't kept up. It was a catalogue functional but disconnected from the brand's actual packaging, social presence, and positioning. Google Ads money was landing on pages that weren't converting.

"Google Ads money was landing on pages that weren't pretty enough for conversion or compelling enough to make people stay."

02 — Brand Architecture

Three brands. One coherent system.

Before touching a single frame, I needed to understand what each brand was — and what role it played in the structure. This informed every design decision downstream.

Farmley
Mother Brand

Clean, confident, neutral. Establishes trust before handing off to sub-brands.

Date Bites
Sub-Brand

Rich, warm, indulgent. The dessert that loves you back.

Maka Shaka
Sub-Brand · New

Energetic, playful, light. Makhana-based snack for IPL season.

03 — Key Decisions

Where I diverged from the brief.

Good design isn't always about executing the brief. Sometimes it's about recognising which parts of the brief will hurt the outcome.

Scope → Changed

MVP-first, not full redesign at once

Original brief called for sub-brand pages, bundle builder, editorial sections — all simultaneously. Pushed back. MVP first reduces risk, validates the platform, gives a stable base.

Theme → Owned

Metro after evaluating against a checklist

Not the most popular Shopify theme. Chosen because it separates content sections cleanly — essential when Date Bites and Maka Shaka need different visual temperatures.

Nav Architecture → Rebuilt

Date Bites as brand, not product category

The original nav treated Date Bites as a category alongside Seeds and Makhana. That's a positioning problem masquerading as a navigation problem.

Homepage Hierarchy → Defined

Brand trust before commercial ask

Defined sequence: Farmley brand moment → sub-brand showcase → category → products → social proof. You understand what Farmley is before you're asked to buy anything.

04 — Outcome

What shipped.

49
Days from brief to live MVP
3
Homepage architectures tested
3
Brand identities held on one homepage

"A Shopify build doesn't have to look like a Shopify build. The constraint of a theme is a design problem, not a design ceiling."

05 — Learnings

The things worth keeping.

01

Owning a project means owning the uncomfortable questions first.The brief had a scope problem. The best thing I did early was slow down, push back, and get alignment on what Phase 1 needed to be.

02

Brand architecture has to be decided before IA.The nav structure treated Date Bites as a category. That's a positioning problem masquerading as a navigation problem.

03

Good handoffs are a design artefact too.Spec notes, component documentation, and a clear Phase 2 roadmap — these are the deliverables that outlast the sprint.

← All work View IHSS →