Daash - Making restaurant operations feel simple.

Restaurants often had different tools for different parts of their business.

The result was a lot of disconnected processes and data. Daash was being built to bring these workflows together.

But that created another challenge:

Before designing the product, I needed to understand how restaurants actually operated.

I visited restaurants and spoke with:

I wanted to understand their daily workflows, where things became difficult, and what they needed from a system like Daash.

I also looked at existing products and patterns, particularly for online ordering and POS.

One of the biggest things I had to understand was how the different parts of Daash connected.

For example:

Customer orders → Sale → Inventory → Revenue → Reports

So I wasn’t designing completely separate features.

I was designing one connected system with different workflows.

So across the product, I focused on things like:

The POS requirement initially sounded simple:

Create an order → Take payment → Produce a receipt

But research showed that the real workflow was more complicated. Attendants perform these actions repeatedly throughout the day, so I focused on making common actions fast.

For example, instead of requiring attendants to search for every product, commonly sold products were immediately visible.

I also introduced Hold Order for situations where a transaction couldn’t be completed immediately.

We had roughly three months to get the MVP out, so we couldn't build everything we might eventually want.

The online store was a good example.

We considered a flexible no-code builder, but that would have required significant engineering effort.

Instead, we chose a template-based approach that still allowed businesses to apply their branding while being much faster to build.

We launched the MVP to real businesses.

That changed the way we worked.

Instead of relying only on assumptions and internal reviews, we could see how businesses actually used the product.