All Work

Kafili / Product Design / Early-stage

A busy cafe isn't
necessarily a
profitable one.

From fragmented financial data to clearer operational decisions for cafe owners.

My contribution
Financial-data analysis, product direction, and report UX.
Product status
Early-stage and evolving.
Source context
Real cafe operational data. Private figures are not reproduced here.
Kafili Persian wordmark and red cup-shaped brand symbol on a cream background.
Kafili project cover photograph of iced coffee, espresso, a milk pitcher, and takeaway cup packaging on a light surface.
Coffee photograph — project cover, not a photograph identifying the client cafe.

The design journey

Make the connections.
Then make them useful.

  1. Fragmented data

    Spreadsheets, recipes, costs, and sales channels.

  2. Connected economics

    Understand how costs and allocation affect the picture.

  3. Decision-focused reports

    Help owners see what deserves a closer look.

A summary of the product-design process, not a product screen or a measured outcome.

The starting point

Activity is visible. Profitability takes more work.

Kafili is an early-stage cafe profitability analytics product. My starting point was a real cafe's financial and operational data: understanding how its recipes, costs, sales channels, and overhead fit together. A busy service or a strong sales total alone could not explain what the business kept.

Kafili Persian analytical presentation slide asking about item profit, delivery-channel commissions, popular low-margin items, and hidden losses.
Illustrative analytical slide — the profitability questions behind the product direction. Original Persian text is preserved; this is not a record of customer research.

Understanding the data

Before designing a report, understand the business behind it.

I worked through fragmented financial spreadsheets to understand the relationships between ingredients, recipes, costs, and sales. My contribution was to connect those pieces into a product view: what an owner needs to understand, which costs belong in a comparison, and where missing context can make a number misleading.

Kafili Persian slide connecting point-of-sale reports, recipes, purchase costs, inventory, and sales channels to a profitability view, with an example calculation.
Illustrative analytical slide — connecting fragmented data to a decision. The example figures explain the presentation, not the client cafe’s private finances or measured results.

Finding the hidden questions

The same sale can tell very different stories.

I analyzed recipes, costs, and sales channels to identify profitability problems that sales volume could obscure. This meant looking beyond an item's selling price: considering its recipe cost, the channel it sold through, and how overhead was allocated. The public story explains that analytical lens without exposing the cafe's figures or claiming a quantified loss or saving.

Revenue
What was sold.
Contribution
What remains after the costs included in the analysis.
Profitability
A broader question that also depends on overhead and allocation assumptions.
Kafili Persian slide illustrating how high sales, ingredient costs, waste, and channel commissions can conceal a smaller margin.
Illustrative analytical slide — why sales and margin can tell different stories. The diagrams are explanatory, not quantified financial outcomes.
Kafili Persian presentation of an anonymized cafe example, contrasting strong sales with low item margins and delivery-channel costs.
Illustrative presentation of an anonymized cafe example — the client identity is omitted. The qualitative diagrams are not audited financial results or evidence of improvement.

Defining report UX

Move from “what is the number?” to “what should I examine?”

I translated the spreadsheet complexity into a direction for owner-facing reports. The focus was a readable path from a profitability question to the costs and assumptions behind it, then to an operational decision worth examining. A useful report needs to explain its basis as clearly as its headline.

Report direction: questions to support, not validated recommendations or findings from the cafe.

Recipe economics

What does this item cost to make?

Connect the selling price to the ingredients and recipe costs behind it.

Decision to examineReview the recipe or pricing assumptions.

Sales channels

Does the channel change what remains?

Make channel-related costs visible when comparing sales.

Decision to examineExamine the economics of the channel mix.

Overhead allocation

Which costs are still outside the picture?

Distinguish recipe-level economics from a view that includes shared operating costs.

Decision to examineCheck the allocation before drawing a conclusion.

Kafili Persian report-direction slide with illustrative item-profit bars, channel profitability comparisons, a menu matrix, and inventory-cost questions.
Illustrative report direction — example charts, amounts, and menu classifications, not a shipped dashboard, verified client figures, or proven financial impact.

Product direction

Design around decisions, rather than more data.

My work helped define Kafili around translating financial analysis into actionable insights for cafe owners. Recipe economics, channel differences, and overhead allocation shaped the questions the product should answer. The report structure and product direction remain part of an evolving exploration, rather than a finished, validated reporting system.

Still evolving

A clearer direction. More to validate.

Kafili is still evolving. The work presented here is my contribution to understanding real operational data, identifying profitability questions, and defining product direction and report UX. It does not establish product adoption, improved cafe profitability, or measured business impact. The next question is whether owners can understand the reports, trace the assumptions, and use them to decide what to investigate.