Concept design — not a real business
Marlow Coffee Roasters
Melbourne, VIC · Hospitality · Scale plan
The brief
A small-batch roastery in Brunswick wanted a site as considered as their beans. Warm cream and burnt umber, elegant serif headlines, and a subscription flow that feels like a letter from a friend.
Plan
Scale
$150/mo — up to 25 pages
Pages included
- Home
- Our Beans
- Subscriptions
- Wholesale
- Our Story
- Roastery
- Journal
- Contact
- Cart
- Checkout
- Account
- FAQ
What we built
- A subscription checkout with flexible delivery intervals and pause-anytime controls
- A single-origin bean library with tasting notes, roast dates, and grower profiles
- A wholesale enquiry flow that qualifies cafe volume before routing to the sales team
Palette
Background
#F3EADF
Foreground
#2A1A12
Accent
#8C3A1B
Typography
Display — Fraunces
Marlow Coffee Roasters
Body — Inter
Specialty coffee, roasted with patience. The quick brown fox jumps over the lazy dog. 0123456789.
Concept case study: Marlow Coffee Roasters
Marlow Coffee Roasters is a fictional brand I designed to show what a hospitality business could get from Kerb. Here is the thinking behind it, and what a real business like it can take from it.
The problem a hospitality business has
A small roastery lives on repeat orders. Most of the day-to-day pain is admin: customers who want to skip a delivery, pause for a holiday or swap beans, and cafes asking about wholesale. Each one is a small email or phone call, and they stack up around roasting days when nobody is at a desk.
The website often works against the business too. Beans are listed with no roast date or tasting notes, subscriptions are clunky to change, and wholesale enquiries land in a general inbox with no detail about volume. You end up answering the same questions every week.
Why the site is built this way
In this concept for Marlow Coffee Roasters, the brief was a site as considered as the beans. I used warm cream and burnt umber with Fraunces serif headlines, so it reads like a nice paper label rather than a tech shop. The 4px radius keeps things soft but not bubbly.
It's a Scale plan because there's genuine depth: Our Beans, Subscriptions, Wholesale, Our Story, Roastery, Journal, Cart, Checkout, Account and FAQ. The subscription checkout has flexible intervals and pause-anytime controls, because people stay subscribed when leaving feels easy. The bean library carries tasting notes, roast dates and grower profiles.
The wholesale flow qualifies cafes by volume before it reaches the sales inbox. A cafe wanting two kilos a month and one wanting forty get different next steps.
Where AI would take it further
An AI chatbot on the site can answer the daily questions: when does my order roast, which bean suits a plunger, how do I pause. It can hand wholesale leads to you with volume and location already noted. Out-of-hours phone calls could be answered by an AI receptionist, so a cafe owner asking about a delivery gets a proper reply.
In the CRM, I'd set up follow-ups for lapsed subscribers and a reminder when someone's last bag is probably running low. Wholesale prospects get a tracked pipeline instead of a flagged email.
Common questions
If you have regulars who reorder the same beans, probably yes. It smooths your roasting schedule and your cash flow. Keep pause and skip simple, or customers will cancel instead.
Use a short form that asks for cafe name, location, weekly volume and current machine. That lets you reply with a real answer instead of a back-and-forth. An AI assistant can collect the same details by chat or phone.
Not at first. A few useful pages on brew guides or origins can bring in search traffic over time. Only start one if you'll keep it up.

