Fuel Meals featured work example

Fuel Meals

A product design engagement for a prepared-meal platform, focused on making planning, editing, and repeat ordering easier for customers to trust and complete.

Focus
Product strategy, UX/UI, visual systems
Collaborators
Fuel Meals team + General Dev

A design partnership from dashboard design to full customer journey.

We designed a full subscription management portal, then rolled out the same design language across the entire funnel — acquisition funnel, post-purchase experience, and retention systems.

75% increase in rewards redemption

Our subscription dashboard redesign drove a measurable lift in loyalty program usage, a leading indicator of customer retention.

25% decrease in meal order skips

Our customer portal redesign enabled customers to actively make changes to their meal selections, which made them less likely to skip meals.

Fuel Meals redesigned product interface comparison
Original
Fuel Meals redesigned product interface comparison
Redesign
Fuel Meals original product interface comparison

End-to-end product design for a DTC meal subscription company

Fuel Meals needed a clearer product experience around account management and meal selection. The work centered on dashboard structure, editing flows, and a mobile-first interface system that could support recurring customer decisions without adding friction.

Core Challenge
  • Customers needed to understand what was scheduled, what could change, and what required attention without moving between disconnected subscription views.
  • Meal selection needed to support different goals and preferences while making nutrition information easy to compare.
  • Recurring subscription actions needed to feel low-risk, repeatable, and easy to resume so users had fewer reasons to skip or cancel.
Design Direction
  • Treat the dashboard as a weekly decision hub for meals, delivery dates, rewards, and subscription status.
  • Use reusable interface patterns for goal-based browsing, nutrition comparison, editing, and delivery-date changes.
  • Default the first decision where possible, then keep successive actions short, clear, and reversible.
Home

Meal planning is inherently
a systems problem.

Customers were not making one isolated choice. They were balancing goals, taste, timing, trust, and a recurring subscription, so we framed the redesign around the decisions that needed to feel clear every week.

Dietary goals

How will users know the meal program is effective for different fitness goals?

Personalization

Can users quickly find meals that match their preferences, variety needs, and confidence signals?

Subscriptions

How can the experience keep users in the funnel and reduce churn?

Decision fatigue

Can the first decision feel defaulted, with minimal clicks to reach the desired outcome?

Repeat behavior

How can repeatable actions, like editing meals for different delivery dates, become systematized?

Trust

How can nutrition information become salient for people browsing Fuel Meals for the first time?

Building blocks for repeatable weekly decisions.

We focused on modular UI patterns that visually guide customers through a decision matrix: goals, meal preferences, nutrition signals, delivery timing, quantity thresholds, and repeat edits. The goal was a weekly platform that made planning feel easier to understand, personalize, and return to.

Fuel Meals interface building blocks for meal goals, nutrition, quantity incentives, delivery dates, and editing.
(a) From account page to weekly decision hub
  • Reframed the dashboard as the anchor of the experience so customers could understand upcoming meals, account status, and next actions in one place.
  • Pulled the most important decisions forward instead of burying them across disconnected subscription pages.
(b) Goal-based meal selection
  • Organized meal browsing around goal and preference cues so customers could find relevant options faster.
  • Made nutritional information easier to scan at the moment of comparison.
(c) Editing as repeat behavior
  • Designed ordering and editing flows to reduce ambiguity before customers confirm a change.
  • Made recurring adjustments feel manageable and reversible across delivery dates.
(d) Retention through control
  • Used clearer hierarchy and guided account flows to make subscription changes easier to understand.
  • Gave the team reusable patterns that could extend across acquisition, post-purchase, and retention surfaces.