Selfserv connects hotel room service from guest intent to staff action.

Selfserv is an internal Agara product built by Kresna Putra in 2026. It explores a focused, browser-based room-service journey: guests enter through a QR code, browse an offering, place an order, and move through checkout while hotel staff manage the operational side in one dashboard.

Product
Selfserv
Type
Internal functional MVP
Industry
Hospitality technology
Built by
Kresna Putra
Verified technology
Next.js
Selfserv hotel room-service MVP shown on desktop

Can room service become one coherent digital workflow?

Traditional room-service ordering divides one guest need across a printed menu, a phone conversation, manual order capture, and separate staff coordination. Selfserv explores whether the core interaction can live in a browser without requiring a guest app download.

This case study documents the product build. It does not present Selfserv as a commissioned hotel project or claim deployment, adoption, transaction volume, revenue, conversion, or operational improvement.

Guest job

Enter the correct hotel context, understand the available offering, select items, review an order, and move through a clear checkout journey from a phone.

Staff job

Configure the service, maintain the offering, receive orders, understand their state, and coordinate the work through an operational interface.

What makes Selfserv an MVP?

The product focuses on one connected service loop rather than trying to become a full hotel-management platform. The useful unit is not an isolated menu screen or dashboard mock-up; it is the complete path between guest demand and staff response.

01

Enter through context

The product starts from a hotel-specific access point rather than a generic application home screen.

02

Browse and decide

Guests can understand the available room-service offering and move from discovery toward a selection.

03

Build and review an order

The journey maintains enough context for a guest to select, review, and confirm what they want.

04

Hand work to operations

The staff side turns guest demand into an order state that can be reviewed and managed.

05

Administer the service

The internal product includes management views rather than leaving all configuration outside the system.

How was the experience shaped?

The interface separates guest decisions from operational control while keeping both sides inside the same product concept. That boundary makes the MVP understandable without pretending the first version is a complete hospitality suite.

Browser-first access

A guest can enter from a QR code and use the service without installing a native hotel application.

Role-specific views

Guest-facing choices remain simple while administration and order management live in dedicated staff views.

One primary workflow

The product stays centred on room-service ordering instead of accumulating unrelated hotel features.

Product development by Kresna Putra, Mobile & Fullstack Developer at Agara.

Eleven views of the working product

These screenshots are presented as product evidence, not performance evidence. They show the breadth of the implemented interface without implying live hotel adoption or measured commercial results.

Selfserv product overview interface
Selfserv product view 01
Selfserv account and access interface
Selfserv product view 02
Selfserv product setup interface
Selfserv product view 03
Selfserv hotel service management interface
Selfserv product view 04
Selfserv catalogue management interface
Selfserv product view 05
Selfserv product detail interface
Selfserv product view 06
Selfserv operational dashboard interface
Selfserv product view 07
Selfserv order management interface
Selfserv product view 08
Selfserv workflow status interface
Selfserv product view 09
Selfserv reporting and administration interface
Selfserv product view 10
Selfserv connected product experience
Selfserv product view 11

What are we not claiming?

A credible MVP case study must distinguish a working build from a validated business outcome. Selfserv demonstrates product execution. The following claims require evidence that is not currently published.

  • • Live deployment at a named hotel
  • • Active payment processing or transaction volume
  • • Guest adoption, conversion, retention, or satisfaction
  • • Revenue or average-order-value improvement
  • • Staff time savings or fewer ordering errors

Need a focused first release for your own product idea?

Agara helps define the assumption, constrain the scope, design the experience, and ship the software required to learn from real users. Start with the complete MVP development guide or explore the delivery service.

Explore MVP Development