Case study 01
JKitchen Cooks
A private chef’s Sunday drop, turned into a site you can order from before Friday at five.
- Role
- Design and build
- Year
- 2026
- Focus
- A weekly menu drop
- Live
- jkitchencooks.com
What I built
Try it
Orders close at 5pm on Friday. Here’s the countdown, as it shows on the site:
––
days
––
hrs
––
min
––
sec
Build a box
10 meals, delivered Sunday. First box 15% off.
“Premium, meets meal prep.”
What Changed
This week’s menu, the Friday cutoff and a postcode check are all on the page. Customers can subscribe and change their Sunday box without messaging the kitchen.
The Problem
JKitchen cooks a new menu every week and delivers on Sunday across the North West, North East and North Yorkshire. Boxes run from 6 to 15 meals, with breakfasts and juices as extras. Subscribe and your first box is 15% off.
It had to feel like the food: considered, not mass-produced. It also had to do the practical jobs: check a postcode, show this week’s plates with calories, and make the Friday cutoff hard to miss.
What I Built
The menu is the product
This week’s plates, with calories and prices, up front instead of buried in a generic shop.
Build a box
Choose 6, 8, 10, 12 or 15 meals, swap plates, and add breakfasts and juices if you want them.
A deadline you can see
Orders close at 5pm on Friday so the kitchen can buy in and cook. The page tells you before you start.
Postcode, then the box
A delivery check up front, so nobody builds an order the drivers can’t deliver on Sunday.
The box remembers the choices
Meal count, swaps, breakfasts and juices all stay in one flow. Customers can change their Sunday order without starting again or messaging the kitchen.
- Delivery
- Every Sunday
- Cutoff
- Friday, 5pm
- Box sizes
- 6 to 15 meals
- First box
- 15% off if you subscribe
