# One host budget, a personal meal pass for every guest

> Hospass turns group meal coordination into controlled, email-bound passes. Hosts set the event rules and per-guest budget, while guests use Nomi and a Swiggy-connected discovery flow to choose for themselves.

**Project:** Hospass
**Category:** AI product build
**Status:** Active build. A public product preview with authenticated host and guest workflows under active development.
**Headline design property:** ₹0 customer funds held by Hospass, by design
**Qualification:** ₹0 is a product-design property, not an audited financial result. Hospass is designed without a customer-funds wallet or payment custody path.
**Stack:** Next.js · Supabase · Swiggy MCP · Resend
**Audience:** Founders and operators building a multi-sided web application with authentication, permissions, third-party tools, approvals, and auditable workflows.
**Live product:** https://hospass.com
**Case study:** https://aigarage.in/case-study/hospass

## Product premise

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.

## 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.

## Host journey

- Connect an owned Swiggy account and choose a provider-verified saved address.
- Set the event window, food rules, guest list, and default or individual budget caps.
- Launch private, email-bound passes and manage claims, approvals, and event state.
- Generate a private CSV event record for the people authorized to manage the event.

## Guest journey

- Open a personal invitation and authenticate with the invited email address.
- Claim the pass and see its event, venue, rules, time window, and available entitlement.
- Use Nomi for provider-backed restaurant and menu discovery within the pass rules.
- Reserve an in-budget choice or ask the host to approve an amount above the entitlement.

## Provider and money 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.

- **The person owns the provider account:** A Swiggy connection belongs to the profile that created it. Organization roles do not transfer its credentials, saved addresses, or reconnect rights.
- **The event gets an explicit binding:** Provider access is attached to a specific event by the account owner. Another member does not receive blanket access because they share an organization.
- **The guest gets an entitlement, not a credential:** A claimed pass can use the event’s approved provider context without exposing the host’s provider credential.
- **The budget is a control boundary:** In-budget choices can reserve entitlement. Over-budget choices become an approval request instead of silently exceeding the cap.

## What is implemented

- Authenticated organization and member roles
- Owned provider connections and event-scoped authorization
- Event creation, guest budgets, launches, and email-bound pass claims
- Nomi-assisted provider discovery and current-price context
- Entitlement reservation and over-budget approval requests
- Host activity, notifications, tracking state, and private CSV reports

## Current limitations

- Final provider order submission is still in validation. The current real-pass action stops after entitlement reservation or approval routing.
- The case study makes no claim about completed deliveries, customer adoption, order volume, reliability, revenue, conversion, or time saved.
- The example occasions, names, budgets, and pass states on the public marketing site are illustrative, not evidence of real customers or usage.

## Build lessons

- **Model authority before automating action:** 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.
- **Keep the two sides independently legible:** The host and guest need different interfaces, language, and permissions, but both must read from the same event, pass, and entitlement state.
- **Show partial states honestly:** 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.

All case studies: https://aigarage.in/case-study
AI Garage is a builder community and delivery studio in Bangalore. Email: hey@aigarage.in