Skip to content

Wait, which
cake was that?

Cakely is a cake ordering and management system being designed for SME bakeries: custom requests, bookings, production schedules and deposit records, together.

Six students, one bakery interview.
Starting with the work behind the counter.

IN DEVELOPMENT · EXPLORE THE TEAM’S INTERFACE CONCEPTS BELOW.

Cakely team meeting a bakery representative during fieldworkCakely customer dashboard design mockup
YES, THE
CAKE MESSAGE
GOES HERE TOO ♡
Custom cake ordering ✴Order tracking ✴Booking calendar ✴Deposit monitoring ✴

An order comes in.
Then the admin.

A date, a flavour, a message, an allergy note. Someone has to keep track of it all. The team’s investigation focused on three places where that work can get difficult.

20Bakeries contacted during outreach
1Interview opportunity secured with Morii Baking Studio
3Order-management problems shaping the design
01 / THE SCATTERED ORDER

A booking in the notes. Another in the chat.

When orders live in different places, a deadline can slip through. A forgotten cake costs time and customer trust.

THE PROPOSED FIX
A central order list, a booking calendar and daily production limits.
02 / THE UNSECURED BOOKING

The ingredients are bought. Then they cancel.

A custom cake can be hard to resell. Without an agreed deposit, the bakery may be left carrying the cost.

THE PROPOSED FIX
Deposits set by each bakery, with payment status attached to the booking.
03 / THE MISSING DETAIL

The flavour changed. Did the order?

Size, wording, design notes and allergies can get buried in a message thread. A missed detail can mean rework or an incorrect order.

THE PROPOSED FIX
A structured custom cake form, allergy alerts and pricing based on selected options.

Here’s where
the details go.

A customer needs to explain the cake. A bakery needs to plan the work. These interface concepts show how the team wants to connect the two.

Cakely customer dashboard design concept

The customer’s side of the counter

The proposed dashboard brings the cake catalogue, custom requests, upcoming bookings and order status into view.

DESIGN CONCEPTS · FUNCTIONALITY NOT YET VERIFIED
① Cake catalogue

A catalogue of cakes and available styles, ready to browse.

② Detailed customisation

Size, flavour, wording and allergy notes, with option-based pricing.

③ Booking + calendar

Advance bookings and daily limits to help plan what fits.

④ Deposits + tracking

Each bakery sets its deposit policy; records show payment status.

Before the apron,
there’s a booking.

This is the intended order flow. Cakely would give bakery operators a way to take a request from the first choice through to the production schedule.

STEP 01

Choose a cake

Browse an existing design or begin a custom request.

STEP 02

Get specific

Share date, size, flavour, message, design and allergy details.

STEP 03

Confirm the booking

Review the calculated price and the bakery’s own deposit requirements.

STEP 04

Keep it on track

The bakery checks capacity, schedules preparation and updates the order status.

Getting an interview
took some asking.

The team contacted 20 bakeries to ask about their operations. Those requests were declined. They kept trying and secured one interview opportunity with Morii Baking Studio, visiting on 16 October 2026.

The useful part started when someone had time to talk.

One interview is a starting point. The team still needs to hear from more bakeries.

Members of Cakely participating in a bakery interviewCakely members in conversation during bakery research
16 OCT 2026 · MORII BAKING STUDIO ♡
Cakely research visit
01 / At MoriiMorii visit
A bakery environment documented by the team
02 / Bakery observationsObservation photo
Cakely members documenting bakery-related observations
03 / Out in the fieldObservation photo

The six people
doing the asking.

Meet Cakely’s founding team. Pick a portrait for a closer look.

The six Cakely student founders posing together
These are the students behind the outreach, the visit and the interface designs. Six faces to put to the work you’ve just seen.

For the team
behind the counter.

Cakely’s primary audience is SME bakeries, especially teams handling custom cakes and advance bookings. Here’s how the team positions the idea alongside familiar tools.

WhatsApp Business

Useful for the conversation. Tracking cake details, dates and deposits can still mean keeping separate records.

GrabFood

Built around food ordering and delivery. Detailed custom cake bookings are a more specific workflow.

EasyStore

Offers online shop and order tools. Cake options and custom booking requirements may need extra configuration.

Cakely’s proposed focus: cake-specific options, automatic pricing, advance bookings, production capacity and configurable deposits. Suitability still needs testing with bakeries.

Now, back
to the bakeries.

Next, the team plans to test the flow with more bakeries, refine the custom cake form and booking calendar, and make deposit status clearer. The screens are design concepts; the next job is to build and test the workflow.

Explore interface concepts View presentation mode