Arabica Coffee Co.

Context

Arabica is a mobile coffee service in Cape Town. They bring a full coffee bar to corporate events, weddings, and markets. The coffee was good and the operation was professional, but they had no identity system and no website. At an event, they looked improvised next to the brands around them.

They needed to start booking. I had three weeks.

The Problem

One identity, three audiences. The brand had to read correctly to corporate event planners, wedding coordinators, and weekend market-goers. Those groups judge credibility very differently.

Physical before digital. At an event, the brand is the cart, the apron, and the signage. The website matters afterwards. Most brand processes work screen-first; this one couldn’t.

Three weeks, end to end. Positioning, identity, physical applications, print, and a live website, with a client who needed to be booking events at the end of it.

My Role

Brand strategy, visual identity, print and physical applications, web design, and WordPress build. Solo, direct with the owner.

Process

1. The brand sprint

I ran a compressed brand sprint to fix positioning before drawing anything. The decisive question was what kind of business Arabica actually is.

The answer reframed the project: Arabica is a service business that happens to make excellent coffee, not a third-wave café. Event planners aren’t buying beans, they’re buying the confidence that a supplier will show up, look right, and not need managing. That shaped every subsequent decision, away from craft-coffee signalling and toward reliability and polish.

2. Identity, built physical-first

I designed the physical touchpoints before the digital ones: cart wrap, signage, staff apparel, business cards, because that’s the order the customer meets them.

3. A website with one job

The site exists to make requesting an event quote effortless. Everything else (portfolio, testimonials, service breakdowns) supports that single conversion.

I built it on WordPress so the owner could manage content without me, with an e-commerce foundation ready for bean sales later.

Key Decisions

Service business, not café. The positioning call that made the rest of the project straightforward. Warmth, but with the professionalism a corporate booker needs to see before they commit a budget.

Physical applications first. Designing for the cart and apron before the screen gave the identity more weight, and meant the website inherited a system that was already proven at scale.

WordPress over a custom build. The client needed to run it themselves and wanted a route to selling beans online. A bespoke site would have been better looking and worse suited.

Outcome

Reported 40% lift in enquiries. The owner reported roughly a 40% increase in inbound event enquiries after launch.

Live in three weeks. From no brand assets to a complete identity and live website, with the client booking events on a professional presence almost immediately.

A system that scales. New applications, markets, and products can be added without a redesign.

E-commerce ready. The WordPress foundation supports the planned move into selling beans and equipment.

Technical Implementation

Reflection

What worked. The brand sprint. Compressing the usual back-and-forth forced better decisions earlier, and the positioning statement settled arguments that would otherwise have run for weeks.

What I’d do differently. I didn’t set up any measurement before launch, so the 40% is the client’s account rather than something I can evidence. On any project where the result is the argument, I’d now agree what gets measured before the work starts.

What I learned. Designing physical applications first, then adapting to digital, produced a stronger system than the usual screen-first order. The constraints of a cart wrap and an embroidered apron force decisions that a website never would.