Feeding a group should not require one ordering conversation per guest. Hospass models host-paid hospitality as a controlled pass: the host sets the event, rules, guest entitlement, and provider boundary; each guest claims a personal pass and chooses within that entitlement.
Built for
AI Garage in-house product
Current state
A public product preview with authenticated host and guest workflows under active development.
Stack
Next.js · Supabase · Swiggy MCP · Resend
The coordination problem
Group meals usually make one host the coordinator for every preference, order, payment question, and change. The work grows with the guest list, even though the decision each guest needs to make is personal.
Hospass separates control from choice. The host controls the event and its budget. The guest controls what they want within the pass they were issued.
Two sides of one event
The product keeps host authority and guest choice separate, then joins them through the same event, pass, and entitlement model.
Host lane
Shared control plane
Event rules, email-bound pass, available entitlement, and approval state
Final provider submission remains in validation
Guest lane
Trust boundary
Hospass connects an event to the host’s own Swiggy account for saved-address selection, restaurant and menu discovery, and provider-backed pricing. In the inspected build, Hospass can reserve a guest’s entitlement or route an over-budget choice for approval. Final order submission to Swiggy is still being validated and is not presented here as a completed production flow.
A Swiggy connection belongs to the profile that created it. Organization roles do not transfer its credentials, saved addresses, or reconnect rights.
Provider access is attached to a specific event by the account owner. Another member does not receive blanket access because they share an organization.
A claimed pass can use the event’s approved provider context without exposing the host’s provider credential.
In-budget choices can reserve entitlement. Over-budget choices become an approval request instead of silently exceeding the cap.
Verified implementation
Current limits
Build lessons
01
The difficult part is not generating a meal suggestion. It is deciding who may connect an account, bind it to an event, spend an entitlement, approve an exception, and inspect the resulting record.
02
The host and guest need different interfaces, language, and permissions, but both must read from the same event, pass, and entitlement state.
03
A flow that has reserved budget but has not submitted a provider order needs a distinct state. Honest intermediate states make a complex product safer to operate and easier to improve.
Build with AI Garage
We help founders and operators turn the workflow into a system with explicit boundaries, testable states, and an interface each participant can understand.
