Portfolio demo · Fictional data · Screenshots only
Product case study / Responsive web

A thoughtful path
from cake inquiry
to human review.

I research and plan the LuxWhisk Cake Programme, shaping product requirements and AI workflows, evaluating options, and coordinating execution and quality reviews.

I propose product decisions; the Founder / Owner retains final authority over strategy, business commitments, major investment, and product approval.

Role
Product Research & AI Coordination
Team
Founder / Owner + AI-assisted execution
Timeline
Mid-July 2026–present
See the product → Read the decisions
INQUIRY → HUMAN REVIEWLuxWhisk product Home with persona imagery omitted
A clear handoff: one inquiry, ready for a person to review.
01 / Problem

Collect the details. Keep commitments human.

A cake inquiry brings together contact information, event details, design requests, and dietary questions. The interface needs to make those details easy to share while making clear that an inquiry is not a confirmed price, booking, or order.

The design challenge was to connect customer intake with staff review across desktop and mobile, without turning guidance into an automatic business commitment.

02 / My role and constraints

Research, planning, and coordinated execution.

My responsibilities

I work on product research, product planning, workflow design, option evaluation, cross-functional coordination, and quality assurance coordination. I participate in direction discussions and requirements analysis, then coordinate tasks, handoffs, and execution reviews.

Decision boundaries

I make recommendations and assess options. the founder makes final decisions on company strategy, commercial commitments, major resources, and product approval.

For this case study, the constraints are explicit: use only example data; expose no staff controls; keep customer replies and commitments under human authority; and make the existing interfaces readable across screen sizes.

03 / Decisions

Specific choices, with reasons and trade-offs.

DECISION 01 / CONTACT NAMES

Structure new names; preserve older records.

Options: keep a single name field, or collect First and Last name separately.

Decision: use required First and Last name for new inquiries while keeping the combined name used by existing review screens.

Trade-off: add structure without guessing how to split historical names.

DECISION 02 / COMMITMENTS

An inquiry starts review, not a sale.

Boundary: the intake creates a NEW inquiry and an acknowledgment. It does not calculate a quote, confirm an order, or send a customer response automatically.

Reason: business commitments require a person's decision. This boundary is documented in the intake contract and visible in the acknowledgment screen.

DECISION 03 / SCHEDULING

Keep scheduling separate from intake.

Design: LuxWhisk provides the branded consultation container; the existing scheduler remains responsible for booking.

Trade-off: keep the inquiry interface and scheduling responsibility separate. The portfolio shows a static calendar instead of connecting to real appointments.

04b / Mobile guidance

A visible entry. A guided next step.

The mobile entry opens the existing Concierge panel. Topic choices help visitors choose a next step without making a business commitment.

ENTRYMobile Home with mobile navigation
AFTER CLICKActual mobile Concierge panel opened from the mobile entry
Screenshot walkthrough

Explore in 45 seconds.

Six selected screens with captions. This is a Screenshot walkthrough, not an operation recording.

Cake Inquiry desktop overview
01 / 06

Cake Inquiry overview

Six accordion sections and a separate Review and submit area.

Paused · 0 / 45 seconds

05 / Outcome

A built, controlled inquiry-to-review flow.

The sample inquiry reaches an acknowledgment and the staff queue with NEW status. The screenshots also show responsive navigation and an actual Concierge open/close interaction. This demonstrates interface work and a connected sample flow, not measured business performance.

What I would measure next

Inquiry completion rate, the share of inquiries with dietary questions answered, time to first human response, and mobile form abandonment. These are proposed measures; no results or improvement percentages are claimed.

What success would mean

Enough information for the owner to assess a request, a clear next step for the customer, and fewer unclear handoffs between intake and review.

06 / Reflection

Define evidence as carefully as the interface.

My takeaway is to distinguish an implemented screen, a connected example workflow, and a validated customer outcome. For the next iteration, I would define success measures before testing and collect structured feedback on the intake and review handoff.

About this portfolio demo

Screenshots use fictional data and provide no staff access, live ordering, or booking. The calendar is a static illustration. Sample labels replace internal identifiers. Person imagery is omitted from this demonstration.

AI-assisted execution supports my research, planning and coordination work; business decisions remain human-reviewed.

Full-size demonstration screen