Skip to content
Verdant Bowl Co. — Fast casual / Restaurant project preview

Case Study

Verdant Bowl Co.

Fast casual / Restaurant · United Kingdom & Ireland

-28%

Steps to checkout

+19 pts

Mobile task success

Unified

Brand consistency score

WCAG AA

Accessibility

The Challenge

A growing bowl-and-salad concept needed digital parity between web and app: inconsistent nutrition storytelling, a long path to checkout on mobile, and loyalty flows that did not reflect the in-store brand.

Full write-up

Brand parity across web and app for a fast-casual bowl concept

Verdant Bowl Co. needed one calm design language everywhere diners touch the brand — plus fewer taps to checkout and clearer nutrition storytelling on mobile.

Fast casual lives or dies on lunchtime clarity: pick a base, add protein, choose a pickup slot, pay. When web and app drift apart visually and behaviourally, repeat diners hesitate — especially when dietary cues matter.

Where friction showed up

Nutrition and allergen prompts were accurate but buried. Checkout duplicated decisions users already made elsewhere in the journey. Loyalty affordances looked bolted on rather than part of the meal ritual.

We reframed the brief as fewer decisions per minute, not "more features".

Design system work

We shipped shared tokens for typography, spacing, and semantic colours tied to states (success, warning, dietary highlights). Marketing pages pulled from the same primitives as transactional flows so seasonal campaigns stopped introducing one-off components that polluted the app.

Storybook-backed documentation let agencies and internal designers extend without breaking rhythm.

IA for menus and dietary cues

Categories were regrouped around how people scan under time pressure: dietary filters surfaced earlier; calorie bands were consistent across SKUs; modifiers used progressive disclosure so advanced tweaks did not swamp first-time guests.

Accessibility as launch criteria

Contrast and tap targets were audited against WCAG AA for critical paths. Fixes landed before promotional pushes so campaigns did not amplify inaccessible surfaces.

Measurement stance

Public narrative sticks to indexed UX signals and moderated task outcomes — never revenue in this write-up. Checkout efficiency and mobile task-success indexes are the headline proof points alongside qualitative kitchen and ops feedback.

Timeline & outcomes

Live + ongoing A/BSep 2024 – Feb 2026

Engagement timeline

  1. Phase 1

    Menu IA & component audit

    Sep – Oct 2024

  2. Phase 2

    Design system & checkout refactor

    Nov 2024 – Jun 2025

  3. Phase 3

    Loyalty parity & geo pilots

    Jul 2025 – Feb 2026

Indexed outcome curve (baseline = early sprint, 100 = latest measurement)
Indexed performance trend

Values are normalised indices for communication only — not revenue or confidential KPIs.

Before / after index — key UX and delivery signals

Checkout efficiency (index)

Baseline
58
Outcome
92

Mobile task success (lab index)

Baseline
62
Outcome
88

Design-system coverage

Baseline
44
Outcome
96

What We Built

  • Design system for web and native shells with shared tokens
  • Menu IA reorganised around dietary cues and peak lunch journeys
  • One-tap reorder and pickup scheduling with clearer confirmation states
  • Accessibility review through AA fixes on typography and contrast

Tools Used

Next.jsFigmaStorybookSanityVercel

Related case studies

We optimised for fewer taps, clearer nutrition cues, and one voice across web and app — measurable in moderated tests, not vanity redesigns.

Engagement charter · Goals agreed at kickoff

Timeline

Sep 2024 – Feb 2026 (waves)

Investment

£8,000 – £14,000

Want similar results?

Send Enquiry
WhatsAppBook a Call