Case study · Daymaker · 2026

Bringing order to Daymaker's orders page

Daymaker sends cakes to teams, but its orders page had grown scattered, and founders had to hunt for each order. In two weeks I audited the page and merged its scattered parts into one table you can scan. The redesign went to the founders as Figma screens and a working prototype, ready to build.

Role
Product designer
Timeline
2 weeks
Users
Startup founders
Team
Daymaker's founders
After: the redesigned orders page with colored status pills, recipients, and cake photos
Before: the orders page built in Lovable
BeforeAfter

Drag the handle to compare the Lovable version with the redesign.

Quick look

I redesigned the orders page so founders can find any order in one look.

Two weeks to turn a scattered page into one table a founder can scan.

The redesigned orders page: status pills, recipients, and cake photos in one table
Who it is for

The founder who checks every morning

She read around grey tags and an empty Employee column to find the orders due that week. She needed to see who each cake is for, and which orders are live, without opening anything.

Line sketch of a founder with a coffee, scrolling a long list of orders to find one row
Before and after

From reading every row to scanning the page

The Lovable build had every feature, spread across panels and pages. The redesign brings them into one table.

Drag the handle to compare.

After: the redesigned orders page
Before: the orders page built in Lovable
BeforeAfter

How the project went

  1. The old filter panel from the Lovable build
    AuditI went through the Lovable build and noted where the page made people hunt.
  2. The old side menu with a separate One Time Celebrations page
    GroupThings that belonged together were merged, so each job has one home.
  3. Four status pills with their own color and icon
    PolishStatus, recipient, and cakes became easy to read at a glance.
  4. The finished orders table
    Hand overFigma screens and a working prototype, with what I would test first.
The details

Open an order without leaving the table

A side panel holds the order info, recipient, delivery details, and notes. The table stays in view behind it.

The orders page with the side panel open for a birthday order
Plain words

When there is nothing, or something to lose

An empty page says so and points to Add Celebration. Cancelling asks first, and Keep order is the safe choice.

Empty state: No orders yetCancel this order dialog

The problem

Finding one order took three steps

I started by auditing the Lovable version, and found the spots where the page made people read, hunt, or switch pages. Answering one question took three steps, for every cake, every day. Open the filter panel, scan the grey tags, find the pencil icon.

Line sketch of a founder with a coffee, scrolling a long list of orders to find one row

The founder who checks every morning

The pattern
Read around the grey tags and the empty Employee column every morning to find the orders due that week.
What they needed
To see who each cake is for, and which orders are live, without opening anything.

One of the founders, as I remember the conversation.

Old filter panel with date inputs, status checkboxes, and advanced filters
FiltersA big grey filter panel came before a single order.
Old status column where Scheduled and Cancelled use the same grey tag
StatusScheduled and Cancelled used the same grey tag.
Old side menu with a separate One Time Celebrations page
MenuOne-time celebrations had their own page.
Old Employee column showing only a dash
EmployeeThe Employee column showed only a dash.

Editing was the fifth problem. It hid behind a small pencil icon on each row.

Bringing features together

Scattered features were merged into one place

Things that belonged together were spread across the page and the menu. I merged them, so each job has one home.

Employee columnOccasion
One Recipient column
Date rangeStatus checkboxesAdvanced filters
One filter bar
One Time Celebrations pageOrders page
One table, with a Type filter
Pencil iconOrder details
One side panel with Edit order

What changed

The four biggest changes on the page

Status and recipient

Each status gets a color, and each row says who and why

Scheduled, Confirmed, Fulfilled, and Cancelled are easy to tell apart at a glance. Cancelled rows also fade back, so live orders stand out. Each row shows the name and the occasion, and a countdown says how soon the cake is due.

Status
Before: grey Scheduled and Cancelled tags that look the same. After: four pills with their own color and icon.
Recipient
Recipient cells with a name and an occasion: birthday, one time, and work anniversary
Cakes

See the cake, not just its name

A photo, the servings, and the quantity sit together. When an order has more cakes, a small +3 tag keeps the row short. Hover the tag to see the rest.

Before
Old cakes column with plain text
After
The +3 tag open, listing The Beverly, Vanilla Bean, and Mango Mouse with servings and quantity
Filters

Filters fit in one line

Search, Status, Type, and Delivery date sit right above the table. More filters open from + Filter, so the orders show up first. One-time celebrations lost their own page, so a founder who bookmarked it has to filter instead.

Before
Old filter panel with date inputs and status checkboxes
After
New filter bar with search and three dropdowns

The details

Small details that make the table easier to read

Hover cards

The dates you need, only when you ask

Hover a name and a card shows that person's birthday and work anniversary. Those dates would widen every row. So they live in the card instead. The dates leave the row, so a founder who wants them at a glance has to hover.

A hover card for John Doe showing a large initial, Birthday: 28 Mar, and Anniversary: 24 Jul
Side panel

Open an order without leaving the table

Editing moved from the pencil icon into a panel that opens on the right. Order info, recipient, delivery details, and notes sit there. The table stays in view behind it. Editing is two clicks instead of one.

The side panel for a birthday order: Scheduled pill, order info, recipient, and delivery details
Cancel and empty

Plain words when there is nothing, or something to lose

When there are no orders, the page says so and points to Add Celebration. Cancelling an order asks first. The dialog spells out the recipient and the date, and Keep order is the safe choice. Cancelling takes one more click, because the dialog asks first.

Empty
Empty orders page: No orders yet, add a celebration to schedule the first cake
Cancel
Cancel this order dialog with Keep order and Cancel order buttons
Paging

Room for more than seven orders

One screen has the Demo Video button floating over the corner of the table. The revised screen moves it into the header. It also adds a rows per page control and page arrows under the table. A control most days never need.

Header
The header with the Demo Video button next to the user menu
Footer
Under the table: Showing 7 orders, a Rows control set to 100, and page arrows

What happened

The founders got the screens and a prototype in two weeks

  1. Handover

    It went to the founders as screens and a prototype

    After two weeks, the redesign went to the founders as Figma screens and the working prototype on this page.

  2. Reaction

    The founders reacted to status and recipient first

    Their first reaction was to the status colors and the recipient column, the two things they had been reading around every day.

  3. Limits

    What I did not do

    Two weeks left no time for user sessions. The audit of the Lovable build stood in for research. An audit can show where a page makes you read or hunt. The first thing I would test is whether a founder can find one order, like a birthday cake due next week. Can they do it without a single filter?

Two weeks earlier, checking on one cake took three steps. In the prototype it takes one look.

Prototype

Try the new orders page

I used Claude to turn my Figma screens into this working prototype. The screens and sample data come from my final design.

Next case study

Turning phone records into leads for police investigators

I visited police in Lucknow and I4C, then tested the design with investigators.

Read case study
CDR Analyzer table view