Discovery
Identity, atmosphere and cuisine presented clearly, with the information guests need to plan a visit.
Bocao Latin Grill: a connected digital experience designed around the customer and the operation behind it.
Discover the restaurant on social media. Find the menu on a website. Call about a table. Message about catering. Order through another platform.
For the customer, the experience can feel fragmented. For the restaurant, those interactions create additional administrative work.
The project began as a website redesign and expanded into a broader question about how customers move through the business digitally.
How can the digital experience reduce friction for guests and the people running the restaurant?
Bocao’s new digital environment is being designed around the actions customers want to take, with clear paths for menus, reservations, events, catering and ordering.
Existing operational platforms should continue handling the functions they already perform well. The website becomes a useful starting point, with integrations and workflow design connecting the journey behind it.
The website is the visible part. The larger opportunity is what happens afterward.
Identity, atmosphere and cuisine presented clearly, with the information guests need to plan a visit.
Menu structure and ordering paths connected to the restaurant’s existing systems.
A clear path from interest to a table, with reservation integration in the customer journey.
A distinct inquiry workflow that captures the details staff need to evaluate and respond.
A foundation for event discovery, promotion and future guest communication.
Planning the handoff between customer requests and the people responsible for a response.
Once the website and core customer journeys are ready, the next opportunity is to connect requests with internal action.
A structured request can lead to an internal notification, a customer acknowledgment and a deliberate follow-up.
Confirmations and reminders can support the guest experience when connected to the right systems and communication preferences.
Classifying and routing common inquiries can help the team respond with the context already available.
These are planned opportunities, not claims of deployed automation.
My role spans both the customer-facing experience and the operating processes behind it.
The website and customer experience are being implemented. Operational automation, structured follow-up and future customer-data workflows are later opportunities built on that foundation.
A website should not exist independently from the business it represents.
The experience needs to account for what happens before a customer arrives, what they need while interacting with the business and what staff must do afterward.
That is where a collection of pages becomes a connected business system.
Tell me where things get complicated. We can define a useful first step.
Hospitality operations system · Operational Prototype