Skip to content
Brand Identity Let’s talk
Brand Identity

Desi Tadka Catering

Identity for a catering business: a wordmark that survives a flex banner and a 60mm box label, a menu system a non-designer can update, and packaging that makes takeaway look deliberate.

Brand IdentityPackagingMenu design
Desi Tadka Catering — Brand Identity case study by Chetan Sharma
Client
Desi Tadka
Year
2025
Role
Identity and menu collateral
Type
Design
The brief

What needed solving

Catering brands get printed on everything from a three-metre hoarding to a sticker on a gravy tub, and half the collateral is produced by a shop with a machine and no designer. Anything subtle or small was going to be lost.

Approach

How it was built

(01)

Drew the wordmark for distance viewing, then checked it at box-label size before anything else was designed.

(02)

Built the menu as a table-driven layout the kitchen can edit, with fixed spacing so an added dish cannot break the page.

(03)

Limited the palette to two inks, which is both what a small print shop handles well and what makes the boxes look like a set.

(04)

Set up the WhatsApp-forward version of every piece: one image, no crop surprises, phone number legible without zooming.

Outcome

What changed

The brand holds up on cheap materials, the menu updates without a designer, and the box that arrives at a function looks like the hoarding outside it.

MarkLegible from 3m and at 60mm
MenusEditable by the kitchen, layout-stable
PrintTwo inks, specified for small shops
Wordmark and supporting markPackaging and label artworkEditable menu systemPrint specifications for vendorsSocial and forward-ready exports
Process

The same six stages,
every project

(01)

Discovery

Clarify the goal, users, constraints, current systems, success measures, and delivery risks.

(02)

Architecture

Choose the right structure, integrations, data model, security boundaries, and technology stack.

(03)

Design

Map important journeys and responsive states before expensive decisions are locked in.

(04)

Development

Build in reviewable milestones with clean code, documented decisions, and visible progress.

(05)

Testing & Launch

Validate functionality, performance, accessibility, security, and production readiness.

(06)

Support & Improvement

Monitor real use, resolve issues, and prioritize improvements using evidence.

Have something similar in mind?

Tell me the outcome you need and the deadline you are working to. I will tell you honestly what is possible.