All work

Case study

Freshii Ordering Platforms

Enabling users to order ahead via the app or the website — a white-label platform rebuilt in-house, from the ground up.

7 min read

Freshii ordering app and website
The rebuilt platform — native app and web ordering, side by side.

155K users

Since launch

2.1 → 4.5

App Store rating

3 platforms

Rebuilt solo → team

Background

A white-labeled platform, at a white-label cost.

Freshii already had an ordering platform, built and run through a third-party vendor. The cost of running it per partner location was high, and the turnaround time for fixing critical issues or shipping new features was slow — with next to no control over the actual user experience.

Existing Freshii app — home screen, limited time offer menu, and item customization
The existing app — home, limited-time offers, and item customization.
Build a new ordering platform, in-house — one that was cost-effective, gave us the roadmap, and let us address critical issues with a faster turnaround.

The mandate: own the platform enough to grow KPIs and sales, not just maintain the status quo.

Key principles

Three numbers to design around.

Key features

Four capabilities the old platform didn't have.

Research

One designer, a team of five, short on resources.

Being the only designer on a lean team of five, I relied on user interviews and guerrilla testing at the stores, competitive research against apps like the ones we were replacing, and ongoing customer feedback surfaced through support teams and Medallia.

Information architecture

Five sections, mapped before a single screen was drawn.

Home, Rewards, Order, Gift Card, and Account — each broken down to the individual screen and state before wireframes started, so the ordering flow's structure was settled early.

Information architecture diagram — Home, Rewards, Order, Gift Card, and Account navigation structure
Mapping the new navigation structure across all five sections.

Wireframes

Selected flows, tested in grayscale first.

Home, store selection, menu, and item customization all went through low-fidelity wireframes before any visual design — cheap to change, easy to test against the principles above.

Wireframes for the home screen and store selection flow
Early wireframes — home screen and store selection, before visual design.

Visual design

Real photography, real prices, real nutrition data.

The wireframes became full visual designs across web and mobile web — every ingredient shown with its own photo, calorie count, and price, so customizing a bowl never felt like guessing.

Visual design of the Tex Mex Bowl product page with real photography and ingredient list
Visual design — bringing the wireframes to life with real photography.

A better home experience

Fewer steps, faster checkout.

Hypothesis: by decreasing the number of steps, we could speed up ordering and provide a faster checkout experience — and that, in turn, would improve the quality of user engagement.

New app homescreen compared to the upcoming redesign
New app homescreen (left) versus the next iteration (right).

Expanding to other brands

One platform, re-skinned for a second brand.

The system was built to scale beyond Freshii — the same ordering platform, re-themed, powered Quesada's app. Proof the architecture wasn't a one-off, it was a platform.

Quesada app built on the same ordering platform as Freshii
The same platform, re-skinned for Quesada.
Once the core loop worked, the real work was everything a bowl of rice and beans doesn't show you.

Payments that split across gift cards and cards. Loyalty points that redeem mid-checkout. Two-factor login. Promotions with real restrictions. Every one of these had to work as well as the happy path.

The finished experience

Every flow, designed to the same fidelity.

From first launch to order confirmation, each piece of the platform — ordering, customization, checkout, payments, loyalty, gift cards, promotions, security — was designed as its own complete flow, not an afterthought bolted onto the core loop.

Core ordering flow — homescreen, store selection, menu, and product screens
The core loop — homescreen, store selection, menu, product.
Customizing a product — replace, remove, and add ingredients
Customization — replace, remove, and add ingredients, priced live.
Added ingredients, upsell, checkout, and promotions screens
Added ingredients, upsell, checkout, and promotions.
Payment methods, gift card payment, split payments, and checkout
Payments — cards, gift cards, and split payments in one flow.
Redeem loyalty points, tips, order confirmation, and rate the app screens
Redeeming loyalty points, tipping, and order confirmation.
Sending gift cards and the resulting gift card email
Sending a gift card — from selection to the email it generates.
New capabilities, in-app messages, and full screen messages
In-app messaging — offers, gifting prompts, and referral.
New home screen, offer details, and guided meal deal flow
Guided meal deals — a step-by-step path through a bundled offer.
Two-factor authentication login flow and email verification
Two-factor login, added for account security.

Outcome

Key metrics, since launch.

Revenue figures are kept out of the public version of this case study — everything else from the metrics dashboard is below.

155K

Total user count

303K

Total orders

24,000

Monthly active users

8,800

Weekly active users

1,500

Daily active users

10.5%

App as a share of total sales

2.1 → 4.5

App Store rating, Android

→ 4.6

App Store rating, iOS

45 / 28 / 60

Conversion — iOS / Android / Web

Three-plus years on one product is the closest thing design has to compound interest.

Owning both the problem and the solution — first as the designer, then as the PM too — changed how I approach every project since.

What I'd do next: the redesign in this deck (the "upcoming redesign" home screen) shipped after this deck was built — the natural next step is a follow-up on what changed once it went live.