Skipper Hospitality Booking Engine · Product Design

Helping subscription 
customers never run out of 
food — without adding friction

Helping subscription 
customers never run 
out of food — without adding friction

Helping subscription customers never 
run out of food —
 without adding friction

B2B SaaS

Subscription

Customer Portal

Lead designer

End-to-end

Spot & Tango customers on UnKibble meal plans were occasionally running out of food before their next delivery. I designed Buffer Bags — a one-time add-on embedded in the customer portal — that started as a 10% pilot and scaled to 100% of users, driving over $300K in sales.

$300K+

In Buffer Bag sales

10% —> 100%

Rollout to all users

-10%

CX complaints

$300K+

In Buffer Bag sales

10% —> 100%

Rollout to all users

-10%

CX complaints

01 · Context

About Spot & Tango

Spot & Tango is a direct-to-consumer pet food brand offering fresh and dry (UnKibble) meal plans delivered on a subscription basis. Customers customize a meal plan for their dog and receive regular shipments sized to their pet's caloric needs.

As the sole product designer on a team of 10+ engineers, I owned the end-to-end design of Buffer Bags — from initial research through the shipped portal experience. I worked closely with a PM and engineering leads across approximately 3 months.

My role

Sole Product Designer

Team

1 PM, 2 engineers

Timeline

Team

~3 months, 2024-2025

1 PM, 2 engineers

Tools

Figma, User Teting, Data Dog

Tools

Figma, User Teting, Data Dog

Timeline

~3 months, 2024-2025

"How might we give UnKibble subscribers a way to top up between deliveries — without disrupting their existing subscription or creating order management complexity?"

The subscription model

The subscription model

Typical delivery cycle

Typical delivery cycle

Order placed

Order placed

Subscription renews automatically

Subscription renews automatically

Food arrives

Food arrives

Portioned for dog's caloric needs

Portioned for dog's caloric needs

Food runs low

Food runs low

7–10 days before next delivery

7–10 days before next delivery

Next order

Next order

Still 1 week away

Still 1 week away

The gap

The gap

No way to purchase extra food outside the regular subscription cycle — customers had to contact CX or skip meals.

No way to purchase extra food outside the regular subscription cycle — customers had to contact CX or skip meals.

"How might we give UnKibble subscribers a way to top up between deliveries — without disrupting their existing subscription or creating order management complexity?"

Phase 02

Define

"My dog's food ran out two days before delivery. I ended up buying kibble from a pet store, which felt like a betrayal of the whole reason I subscribed."

Customer interview participant

02 · Problem

Customers were running out of food with no self-serve solution

Spot & Tango's meal plans are calibrated to a dog's exact caloric needs — which means there's no built-in buffer. When something disrupted a customer's schedule, they'd run out of food before their next shipment. The only options were to contact CX, wait, or buy elsewhere. All three eroded trust.


Customer pain

Running out of food unexpectedly (ROOF)

No self-serve way to get extra food

Multi-dog households needed flexibility

Anxiety about pet care gaps

Business pain

Business pain

High volume of 'out of food' CX tickets

Risk of churn when buying elsewhere

Missed revenue from customers who'd pay

No existing portal solution

"I wish there was just a way to get extra when we need it. We always end up panicking around delivery time."

Customer support ticket synthesis

CX impact

"Out of food" was one of the most frequent reasons customers contacted support — driving avoidable tickets and pressure on CX to manually expedite orders.

From customer support data

"My dog's food ran out two days before delivery. I ended up buying kibble from a pet store, which felt like a betrayal of the whole reason I subscribed."

Customer interview participant

"I wish there was just a way to get extra when we need it. We always end up panicking around delivery time."

Customer support ticket synthesis

CX impact

"Out of food" was one of the most frequent reasons customers contacted support — driving avoidable tickets and pressure on CX to manually expedite orders.

Understanding how customers think about food supply

Understanding how customers think about food supply

Before designing anything, I needed to understand how customers experienced running low on food. I drew on CX data, Data Dog session recordings, and competitive research.

Before designing anything, I needed to understand how customers experienced running low on food. I drew on CX data, Data Dog session recordings, and competitive research.

📊

📊

CX ticket analysis

CX ticket analysis

Reviewed 'out of food' support tickets. Identified this as a top-5 contact reason by volume.

Reviewed 'out of food' support tickets. Identified this as a top-5 contact reason by volume.

🎥

🎥

Data Dog recordings

Data Dog recordings

Reviewed portal session recordings for customers looking for extra food. Most exited to contact CX — no self-serve path existed.

Reviewed portal session recordings for customers looking for extra food. Most exited to contact CX — no self-serve path existed.

🔍

🔍

Competitive analysis

Competitive analysis

Audited The Farmer's Dog, Ollie, Nom Nom. None offered a portal add-on attaching extra food to an existing subscription.

Audited The Farmer's Dog, Ollie, Nom Nom. None offered a portal add-on attaching extra food to an existing subscription.

🗣️

🗣️

Stakeholder interviews

Stakeholder interviews

Spoke with CX and ops leads — Buffer Bags must attach to an existing order, not create a new one.

Spoke with CX and ops leads — Buffer Bags must attach to an existing order, not create a new one.

Key findings

Top 5

'Out of food' was a top-5 CX contact reason — a preventable friction point with a clear design solution

3 Types

Three distinct needs: reactive (ran out), proactive (want safety stock), multi-dog (need flexibility)

0 of 4

No competitor offered a portal add-on attaching extra food to an existing subscription order

100%

Of portal sessions reviewed showed customers leaving to contact CX — no self-serve path existed


"I wish there was just a way to get extra when we need it. We always end up panicking around delivery time."

Customer support ticket synthesis

CX impact

"Out of food" was one of the most frequent reasons customers contacted support — driving avoidable tickets and pressure on CX to manually expedite orders.

Understanding how customers think about food supply

Before designing anything, I needed to understand how customers experienced running low on food. I drew on CX data, Data Dog session recordings, and competitive research.

📊

CX ticket analysis

Reviewed 'out of food' support tickets. Identified this as a top-5 contact reason by volume.

🎥

Data Dog recordings

Reviewed portal session recordings for customers looking for extra food. Most exited to contact CX — no self-serve path existed.

🔍

Competitive analysis

Audited The Farmer's Dog, Ollie, Nom Nom. None offered a portal add-on attaching extra food to an existing subscription.

🗣️

Stakeholder interviews

Spoke with CX and ops leads — Buffer Bags must attach to an existing order, not create a new one.

Research synthesis

The opportunity wasn't just to sell extra food — it was to give customers control and confidence. A Buffer Bag that attached to their existing order, framed in days rather than bags, with dynamic quantity recommendations, was something no competitor offered.

Phase 02

Define

Framing the problem before designing the solution

With research complete, we aligned on a clear problem statement and the principles that would guide the design. One of the most important early decisions was framing — "days of extra food" was immediately meaningful in a way "bags" was not.

Problem statement

UnKibble subscribers need a frictionless way to purchase extra food mid-cycle — because peace of mind around their dog's nutrition shouldn't require a phone call.

MVP constraints

Attaches to existing subscription order

Cannot be a standalone order — must add to the next UnKibble delivery

UnKibble only at launch

Fresh food plans use different logistics; auto-removed if customer switches

Max 4 bags per order

Cap applied across all recipes to prevent overstocking

No days recalculation on plan change

Quantity stays fixed if customer changes plan size

Design principles

Principle 01

Frame in outcomes, not units

Customers think 'how many days will this last?' not 'how many bags do I need?' Language should match their mental model.

Principle 02

Zero new flows, maximum discoverability

Buffer Bags should feel like a natural part of the portal — entry points must live where customers already go.

Principle 03

Remove the calculation burden

Dynamically calculate how many days a bag provides based on the customer's current plan. No math required.

Phase 03

Design process

The selection modal: days, not bags

The core interaction was a quantity selector inside a modal. Framing as "14 days of extra food" rather than "2 bags" made it immediately meaningful. The interface dynamically calculated days based on the customer's current plan — always personalized.

For multi-dog households, the modal defaulted to all dogs first, with individual selection as a secondary option. This resolved most cases in one tap while supporting complexity when needed.

Buffer Bag modal

Phase 04

Solution

Three decisions that made Buffer Bags work

Each design decision was grounded in a specific research finding or constraint — and each required navigating a real tradeoff.

Buffer Bag modal

Decision 01

Days-based framing over bag quantity

Instead of showing how many bags, the interface translated quantity into days of food — dynamically calculated based on the dog's current calorie plan. A large-breed customer saw '7 days,' not '2 bags.'

Design rationale

Customer interviews showed 'bags' meant nothing to them — they thought about feeding schedules. Days created an immediate, personal connection to the purchase.

Orders

Design rationale

Operations flagged that separate orders would disrupt fulfillment. Rather than treating this as a blocker, we leaned into it — 'it arrives with your next order' is clearer and more trustworthy than two deliveries.

Decision 02

Add-on to existing order, not a separate purchase

Buffer Bags attach to the customer's next scheduled UnKibble order rather than creating a standalone order — arriving with the regular delivery, no extra tracking number.

Design rationale

Operations flagged that separate orders would disrupt fulfillment. Rather than treating this as a blocker, we leaned into it — 'it arrives with your next order' is clearer and more trustworthy than two deliveries.

Phase 05

Testing & Rollout

A 10% pilot before full rollout

Rather than launching to all users immediately, we introduced Buffer Bags as a 10% pilot — enabling a real-data validation loop before committing to full engineering support. I monitored adoption rates, modal drop-off, and CX ticket volume throughout.

Test setup

Participants

5 hotel guests via UserTesting.com

Method

Moderated remote usability test

Prototype

High-fidelity Figma, Journey East Hampton brand

Tasks

3 core flows: search → select → pay

Strong adoption

Purchase rate exceeded benchmark

Customers added Buffer Bags at a higher rate than projected, validating the days-based framing and genuine demand for the feature.

↓ Tickets

'Out of food' contact rate dropped

Customers with access to Buffer Bags were measurably less likely to contact support about running out of food — confirming the feature solved the right problem.

1 UX fix

Qty selector was hard on mobile

Mouseflow recordings showed customers struggling with +/- buttons on smaller screens. We increased tap target size and added a slider before full rollout.

Strong adoption

Purchase rate exceeded benchmark

Customers added Buffer Bags at a higher rate than projected, validating the days-based framing and genuine demand for the feature.

↓ Tickets

'Out of food' contact rate dropped

Customers with access to Buffer Bags were measurably less likely to contact support about running out of food — confirming the feature solved the right problem.

1 UX fix

Qty selector was hard on mobile

Data Dog recordings showed customers struggling with +/- buttons on smaller screens. We increased tap target size and added a slider before full rollout.

Strong adoption

Purchase rate exceeded benchmark

Customers added Buffer Bags at a higher rate than projected, validating the days-based framing and genuine demand for the feature.

1 UX fix

Qty selector was hard on mobile

Data Dog recordings showed customers struggling with +/- buttons on smaller screens. We increased tap target size and added a slider before full rollout.

↓ Tickets

'Out of food' contact rate dropped

Customers with access to Buffer Bags were measurably less likely to contact support about running out of food — confirming the feature solved the right problem.

Phase 06

Outcome & Reflection

From a 10% pilot to $300K+ in sales

After a successful pilot, Buffer Bags scaled to 100% of UnKibble subscribers. The feature became one of the highest-performing add-ons in the portal — demonstrating that solving a genuine customer pain point drives sustainable adoption.

$300k

In Buffer Bag sales

Post rollout

10% —> 100%

10% —> 100%

Rollout expansion

After successful pilot

−10%

'Out of food' CX tickets

Reduced in pilot cohort

30+

Frontend Launches

As sole designer that year

What shipped

Buffer Bags launched in the Spot & Tango customer portal and remain available to all UnKibble subscribers.

Accessible from the Orders tab, home page, and Shop — exactly as designed in the three-entry-point approach.

What this project taught me

Buffer Bags was the first project where I felt the full weight of being the sole designer on a team. No senior designer to review my work — just me, the PM, engineering leads, and a deadline. That forced a level of confidence in my decisions I hadn't needed to develop before.

The most important thing I learned was about constraint as creative input. The operations constraint — Buffer Bags had to attach to an existing order — initially felt limiting. Reframing it as a feature made the product clearer and more trustworthy.

What I'd do differently

I'd involve CX and operations earlier. The order attachment constraint came late and almost derailed the timeline. Cross-functional alignment in week one rather than week four would have saved significant back-and-forth.

What surprised me

The framing change — days instead of bags — had a bigger impact than almost any visual design decision. Language is design. The copywriting decision mattered as much as the UI component.

Main nsight

In subscription products, retention is the product. Buffer Bags wasn't really about selling extra food — it was about removing a churn trigger. The $300K in sales was a byproduct of solving a retention problem.

What came next

Add-ons in booking flow (early check-in, special requests) — highest-priority v2 feature from testing

Multi-CRS integration to support additional hotel clients beyond Journey East Hampton

Analytics dashboard for hoteliers to monitor conversion and drop-off in real time

Expanded design system to support 5+ hotel brands without per-client rebuilds