Where the software meets the service.

The challenge

For a restaurant, the website is part of the service. A guest needs to recognize the food, find the right location, understand when it is open, and reach the correct ordering flow.

Jarasa Kabob also needs a consistent brand across two locations while preserving the menus and fulfillment setup each location uses.

My contribution

I work across the restaurant’s digital experience and its operational implementation, connecting the public-facing storefront to the ordering infrastructure behind it.

• Created a shared marketing experience centered on food photography, menu highlights, and clear location information.
• Connected guests to location-specific ordering flows through the JMTF platform.
• Kept shared branding separate from each location’s menu, prices, POS configuration, and fulfillment details.
• Worked through the practical handoffs between the online customer experience and restaurant operations.

Designing for the actual business

Make the location decision clear

The guest’s location choice affects where an order is prepared. Directions, opening hours, contact details, and ordering entry points need to support that decision together.

Share the brand, preserve the operation

A common storefront helps guests recognize Jarasa. Location-specific ordering helps the software reflect the restaurant that will actually prepare the food. Both are necessary parts of a coherent experience.

Follow the work beyond the screen

A polished page is only useful if its links and workflows lead somewhere operationally meaningful. Working close to the business keeps the implementation tied to what guests and staff need to do next.

What this work demonstrates

JMTF is the reusable platform; Jarasa Kabob is the real-world implementation. This work connects customer experience, brand presentation, multi-location configuration, and the details of restaurant service.