Zeny / Muhammad Bin Saif

The problem

01 / 07

We build the layer between chat and kitchen.
The Zeny manifesto

Every order in Pakistan starts with a WhatsApp message from someone under 45 and ends with a rider at a gate. Between those two moments (across two, five, twenty branches) sits chaos: missed stock, late prep, blind dispatch.

Missed stockInventory decisions made after the spike, not before it.

Late prepKitchens cooking what might sell rather than what will.

Blind dispatchRiders assigned without sight of load across branches.

Zeny exists to replace that chaos with a single operating layer that forecasts demand, stages inventory, and routes couriers before the spike arrives.

The scaling paradox

02 / 07

The manifesto names the chaos. A later chapter explains why it compounds: every system a growing chain buys was built for a single kitchen, so each new branch adds another tool instead of absorbing one. Growth itself becomes the thing that breaks the operation.

01More branches→ more tools

02More tools→ more friction

03More friction→ slower operations

04Slower operations→ lost revenue

05Lost revenue→ can’t grow

The book ends that chain on a flat line (the cycle repeats until the system breaks), then puts figures against the two states. These are the argument the document makes to internal and investor readers, not outcomes measured in a live kitchen. Zeny never shipped.

TOOLING Six tools, or one layer POS, ERP, delivery, analytics, WhatsApp and inventory each hold a fragment of the same order.

RECONCILIATION 14 hours a week, or none The time the document attributes to matching those systems against each other by hand.

ORDER TIMING 23% late, or 96% on time Claimed for agentic dispatch and forecasting, against orders lost in the handoff gaps between tools.

The chapter closes on a line that reads as the identity in miniature: AI manages the chaos. The chef manages the craft. It is the same From Chaos to Craft framework that organises the identity system, stated as an operating claim rather than a design one.

Positioning

03 / 07

MISSION

Make every Pakistani store 15 minutes ahead of demand.

We give multi-branch operators a console that replaces six tools with one. Forecast, prep, dispatch, and settle across every location: AI-assisted, every metric visible, every rupee accounted for.

VISION

The operating system for South Asian retail chains.

Every growing chain, dark kitchen network, and multi-branch restaurant across Pakistan running on one real-time layer: demand predicted, supply staged, delivery optimised. Not a dashboard. An operating reflex.

WHO WE SERVE Multi-branch operators, 2+ locations B2B: chains, dark kitchens and growing QSRs. B2C: WhatsApp-native consumers under 45, with internet access across Pakistan.

WHO WE DON'T Single-location stalls or dhabas No multi-branch ops layer needed. And operators without digital order flow: the system requires WhatsApp or a marketplace to sit behind.

Naming who the product is not for did more work than any feature list. It set the floor at two branches, which in turn decided the whole interface: if the smallest customer runs two kitchens, the dashboard is a comparison view before it is anything else.

Audience architecture

04 / 07

Two audiences that never meet. Merchants were segmented by operational scale, consumers by lifestyle intent: a 3×3 classification where every segment carries its own psychographic driver, retention trigger, north-star metric and interface requirement.

B2B · merchants by scale

Solo-Kitchen Operator2-3 branches · owner-operated

Multi-Unit Franchise Lead4-20 branches · ops team of 3-8

Legacy Brand in Transition20+ branches · ledger to cloud

B2C · consumers by intent

Convenience Professional25-40 · 4-6 orders a week

Social Coordinator22-35 · group orders, Friday peak

Brand-Loyalist Regular28-45 · single-restaurant allegiance

Three of these carried the product. Each one is defined by what would make them trust the system, not by demographics.

Rakesh, the chain operator Runs 2-8 branches across Karachi and Lahore. Lives in the console 14 hours a day. Judges Zeny by whether it reduces his WhatsApp coordination load across locations.

Ayesha, the connected consumer Under 35, orders via WhatsApp 3-4 times a week. She doesn't know Zeny exists. She just knows her order arrives faster and the ETA is always right.

Hamza, the courier captain Coordinates 5-12 riders across a city zone. Needs routing decisions made for him, not suggested. When Zeny auto-routes, his SLA breach rate drops by half.

Ayesha is the one that shaped the brand most. She is a user of the system and will never see it, which is why the consumer-facing surface is a WhatsApp thread and not an app, and why the identity had to work at the scale of a restaurant's own branding rather than competing with it.

Principles & voice

05 / 07

Five principles to settle arguments before they start, and four rules for how the product speaks.

01Forecast, don't guess.

02The operator is the hero.

03Every screen earns its place.

04Specifics beat adjectives.

05Ship Thursdays.

DirectLead with the number. “+34% GMV across 4 branches” beats “huge gains.”

SpecificName the branch, name the rider, name the zone. Our operators run 2+ locations. Context matters.

CalmZeny thinks ahead so operators don't panic. Our tone is the control room, not the fire alarm.

InvisibleThe consumer under 45 never sees our brand. They just know the ETA was right and the karahi was hot.

Identity system

06 / 07

From Chaos to Craft.

The framework the mark is built on, and the shortest statement of the whole product. The problem is chaos: missed stock, late prep, blind dispatch. The answer is the positioning itself: AI absorbs the ordering complexity so the merchant is left with the craft of food.

A lowercase wordmark in a rounded geometric sans, with an inverted terracotta triangle set into the arms of the Y: a cursor, a play head, a drop. The palette is deliberately warm and unlit: this is a tool used in kitchens, not a fintech dashboard.

Aa

LT Saeada

Aa Bb Cc Dd Ee Ff Gg Hh Ii Jj Kk Ll Mm
Oo Pp Qq Rr Ss Tt Uu Vv Ww Xx Yy Zz

Fiery Terracotta #F74E35 R247 · G78 · B53

Coffee Bean #311C21 R49 · G28 · B33

Black #030303 R3 · G3 · B3

Dust Grey #DDD3CB R221 · G211 · B203

Wordmark & surfaces

Three approved surfaces, one triangle

Photography direction

Food shot close, warm and hand-held: the craft the operator is trying to protect while the system handles everything around it. Reference imagery, not commissioned photography.

A hand reaching into a spread of curries served in hammered copper bowls on a patterned cloth — Warm, close, hand in frame

A stack of French toast with banana and blueberries on a dark plate, dusted with sugar — Dark ground, single subject

A hand holding a two-scoop ice cream cone against a warm ochre background — Flat colour behind the subject

The agentic vision

07 / 07

A second version of the strategy widened the scope. The product stopped being a way to take orders and became the infrastructure underneath them.

FROM A conversational interface for restaurant ordering.

TO

The agentic retail ecosystem that runs Pakistani commerce.

From the moment a customer types “biryani” in WhatsApp to the moment a rider hands over the bag. Not a chatbot. Not a dashboard. An agentic system where AI handles the ordering complexity so merchants can focus on the craft of food.

Agentic orderingAI agents that take orders, upsell contextually, and handle the full conversation. The merchant never touches the order flow.

Predictive ERPDemand forecasting in 15-minute windows. The kitchen prepares what will sell, not what might.

Omni-channel POSWhatsApp, app, webview and social link. All orders merge into a single kitchen queue.

Frictionless fulfilmentRider auto-dispatch and route optimisation. The courier captain sees decisions, not suggestions.