Full Mobile App Development – Booking + Membership Platform (iOS & Android)
Budget: ₹12,500 – ₹37,500 INR
ENTRY+
MASTER PRODUCT & DEVELOPMENT DOCUMENT
(Website + Mobile App)
Version: 1.0
Prepared for: Product, Engineering & QA Teams
Founder: Gururaj Shetty
1. PRODUCT OVERVIEW
1.1 What is ENTRY+?
ENTRY+ is a subscription-based, invite-only dining platform that enables members to access a curated network of restaurants with transparent pricing and reserved table access.
It is a closed-circle dining community focused on trust, predictability, and long-term value.
2. PLATFORM STRATEGY
Phase 1 (Immediate Launch)
• Website-first (responsive web)
• Core flows live
• Invite-only membership
• Restaurant onboarding
• Table reservations
• Payments
• Analytics
Phase 2 (1–2 Weeks Later)
• Mobile App (iOS + Android)
• Same backend & dashboards
• Additional features (AI bill scan, savings tracker UX polish)
⚠️ Important:
Backend, dashboards, logic, APIs must be common for Web & App.
3. USER ROLES
3.1 User Types
1. Subscriber (Member)
2. Restaurant Partner
3. Admin (Internal Team)
Each role has a dedicated dashboard, but all dashboards are powered by the same backend system.
4. CORE FEATURES (HIGH LEVEL)
For Subscribers
• Invite-only registration
• Subscription purchase
• Restaurant discovery
• Table reservation
• Payment for reservation
• AI bill scanning
• Savings tracker
• Booking & visit history
For Restaurants
• Quick onboarding
• Booking management
• Slot management
• Daily performance view
• No commission / payout dependency
For Admin
• Full analytics
• User behavior tracking
• Restaurant control
• Revenue dashboards
• System governance
5. USER REGISTRATION & INVITE SYSTEM
5.1 Invite-Only Registration (Mandatory)
• No open signup allowed
• User must enter a valid invite code
• Each registered user gets 1 new invite code
• Invite code rules:
o One-time use
o Expiry: 7–14 days
o Admin override available
Flow:
1. User enters invite code
2. Code validated
3. User registers via OTP
4. Invite marked as used
5. New invite generated for user
6. SUBSCRIPTION MEMBERSHIP
6.1 Plans (Phase 1)
• Monthly – ₹499
• Quarterly – ₹999
• Half-Yearly – ₹1,999
• Yearly – ₹2,999
(Strike prices shown on UI, logic stored in DB)
6.2 Subscription Logic
• Subscription linked to user ID
• Active / expired / grace period states
• Subscription status checked at:
o Restaurant booking
o Bill scan
o Dashboard access
7. RESTAURANT DISCOVERY
7.1 Discovery Parameters
Restaurants shown based on:
• Location (GPS / city)
• Trending
• Vibe (tags)
• Cuisine
• Ads / Featured placement (future)
• Availability (slots open)
7.2 Restaurant Listing Data
• Brand name
• Location
• Images
• Cuisine
• Vibe tags (date, work, chill, loud, premium, casual)
• Slot availability
• ENTRY+ eligibility badge
8. TABLE RESERVATION SYSTEM
8.1 Reservation Flow (Zomato-like but simpler)
1. User selects restaurant
2. Select date
3. Select time slot:
o Slot 1: 12 PM – 6 PM
o Slot 2: 6 PM – 12 AM
4. Select number of guests
5. Pay ₹99 reservation fee
6. Booking confirmed
8.2 Reservation Rules
• Booking fee is platform fee
• Fee deducted from final bill
• Non-refundable if no-show (policy configurable)
• Restaurants can set:
o Max ENTRY+ covers per slot
9. PAYMENT GATEWAY
9.1 Payments Required For
• Subscription purchase
• Table reservation fee
9.2 Gateway Requirements
• Razorpay / Stripe / Cashfree
• Supports:
o UPI
o Cards
o Wallets
• Payment status synced in real-time
10. USER DASHBOARD (WEB + APP)
10.1 User Dashboard Sections
1. Profile
2. Active membership
3. Invite code
4. Bookings history
5. Savings till date (IMPORTANT)
6. AI bill scan
7. Support
11. AI BILL SCANNING FEATURE (CORE DIFFERENTIATOR)
11.1 Feature Description
User can:
• Click photo of restaurant bill
• AI reads:
o Item names
o MRP values
o Charged prices
• System calculates:
o Overcharge (if any)
o Savings via ENTRY+
11.2 AI Flow
1. User uploads bill image
2. OCR extracts text
3. NLP identifies:
o Beverages
o MRPs
o Quantities
4. Price comparison engine runs
5. Result shown to user
11.3 Output to User
• “You saved ₹X today”
• “Total savings till date: ₹Y”
• Flag if overcharging detected
This feature builds trust + brand credibility
12. SAVINGS TRACKER (VERY IMPORTANT)
• Each bill scan updates:
o Session savings
o Lifetime savings
• Display prominently on dashboard
• Used as:
o Retention hook
o Value reinforcement
o Marketing proof
13. RESTAURANT DASHBOARD
13.1 Restaurant Onboarding
• Enter GST number
• Auto-fetch:
o Legal entity name
o Address
• Manual fields:
o Brand name
o Location
o Manager name
o Manager phone
Other data pulled from:
• Google Places API
13.2 Restaurant Dashboard Views
• Today’s bookings
• Upcoming reservations
• Slot-wise covers
• Entry+ vs non-ENTRY+ ratio
• Simple performance metrics
14. ADMIN DASHBOARD
14.1 Admin Controls
• User management
• Restaurant approval
• Subscription analytics
• Revenue dashboards
• Booking analytics
• Invite code control
• City-wise growth
• AI scan usage stats
14.2 Analytics Required
• DAU / MAU
• Subscription conversion
• Booking conversion
• Savings generated
• Restaurant performance
• Churn metrics
15. USER BEHAVIOR ANALYTICS
Track:
• App opens
• Searches
• Clicks
• Bookings
• Bill scans
• Subscription upgrades
Use:
• Mixpanel / Amplitude / GA4
16. SCALABILITY REQUIREMENTS
Initial Capacity
• Users: 200,000+
• Restaurants: 2,000+
Architecture Must Support:
• Multi-city expansion
• Multi-language (future)
• Feature toggles
• Load balancing
• Cloud-native scaling
17. TECH STACK (RECOMMENDED)
Frontend
• Web: Next.js / React
• App: React Native / Flutter
Backend
• Node.js (NestJS / Express)
• REST APIs (future GraphQL optional)
Database
• PostgreSQL (primary)
• Redis (caching)
AI / OCR
• Google Vision API / AWS Textract
• Custom logic layer
Hosting
• AWS / GCP
• Dockerized services
18. SECURITY & COMPLIANCE
• OTP-based login
• Secure payment handling
• GDPR-style data practices
• Audit logs for admin actions
19. FUTURE EXPANSION (MUST KEEP IN MIND)
• Social features
• Co-working memberships
• City ambassadors
• Dynamic pricing
• AI dining assistant
All architecture decisions must not block future features.
20. NON-NEGOTIABLE PRINCIPLES
1. Single backend for Web + App
2. Clean modular architecture
3. No hardcoding business logic
4. Feature toggles everywhere
5. Analytics-first development
6. Performance over cosmetics
21. FINAL NOTE TO DEVELOPMENT TEAM
ENTRY+ is not a feature-heavy app —
it is a trust-driven platform.
Every line of code should support transparency, stability, and scalability.
MASTER PRODUCT & DEVELOPMENT DOCUMENT
(Website + Mobile App)
Version: 1.0
Prepared for: Product, Engineering & QA Teams
Founder: Gururaj Shetty
1. PRODUCT OVERVIEW
1.1 What is ENTRY+?
ENTRY+ is a subscription-based, invite-only dining platform that enables members to access a curated network of restaurants with transparent pricing and reserved table access.
It is a closed-circle dining community focused on trust, predictability, and long-term value.
2. PLATFORM STRATEGY
Phase 1 (Immediate Launch)
• Website-first (responsive web)
• Core flows live
• Invite-only membership
• Restaurant onboarding
• Table reservations
• Payments
• Analytics
Phase 2 (1–2 Weeks Later)
• Mobile App (iOS + Android)
• Same backend & dashboards
• Additional features (AI bill scan, savings tracker UX polish)
⚠️ Important:
Backend, dashboards, logic, APIs must be common for Web & App.
3. USER ROLES
3.1 User Types
1. Subscriber (Member)
2. Restaurant Partner
3. Admin (Internal Team)
Each role has a dedicated dashboard, but all dashboards are powered by the same backend system.
4. CORE FEATURES (HIGH LEVEL)
For Subscribers
• Invite-only registration
• Subscription purchase
• Restaurant discovery
• Table reservation
• Payment for reservation
• AI bill scanning
• Savings tracker
• Booking & visit history
For Restaurants
• Quick onboarding
• Booking management
• Slot management
• Daily performance view
• No commission / payout dependency
For Admin
• Full analytics
• User behavior tracking
• Restaurant control
• Revenue dashboards
• System governance
5. USER REGISTRATION & INVITE SYSTEM
5.1 Invite-Only Registration (Mandatory)
• No open signup allowed
• User must enter a valid invite code
• Each registered user gets 1 new invite code
• Invite code rules:
o One-time use
o Expiry: 7–14 days
o Admin override available
Flow:
1. User enters invite code
2. Code validated
3. User registers via OTP
4. Invite marked as used
5. New invite generated for user
6. SUBSCRIPTION MEMBERSHIP
6.1 Plans (Phase 1)
• Monthly – ₹499
• Quarterly – ₹999
• Half-Yearly – ₹1,999
• Yearly – ₹2,999
(Strike prices shown on UI, logic stored in DB)
6.2 Subscription Logic
• Subscription linked to user ID
• Active / expired / grace period states
• Subscription status checked at:
o Restaurant booking
o Bill scan
o Dashboard access
7. RESTAURANT DISCOVERY
7.1 Discovery Parameters
Restaurants shown based on:
• Location (GPS / city)
• Trending
• Vibe (tags)
• Cuisine
• Ads / Featured placement (future)
• Availability (slots open)
7.2 Restaurant Listing Data
• Brand name
• Location
• Images
• Cuisine
• Vibe tags (date, work, chill, loud, premium, casual)
• Slot availability
• ENTRY+ eligibility badge
8. TABLE RESERVATION SYSTEM
8.1 Reservation Flow (Zomato-like but simpler)
1. User selects restaurant
2. Select date
3. Select time slot:
o Slot 1: 12 PM – 6 PM
o Slot 2: 6 PM – 12 AM
4. Select number of guests
5. Pay ₹99 reservation fee
6. Booking confirmed
8.2 Reservation Rules
• Booking fee is platform fee
• Fee deducted from final bill
• Non-refundable if no-show (policy configurable)
• Restaurants can set:
o Max ENTRY+ covers per slot
9. PAYMENT GATEWAY
9.1 Payments Required For
• Subscription purchase
• Table reservation fee
9.2 Gateway Requirements
• Razorpay / Stripe / Cashfree
• Supports:
o UPI
o Cards
o Wallets
• Payment status synced in real-time
10. USER DASHBOARD (WEB + APP)
10.1 User Dashboard Sections
1. Profile
2. Active membership
3. Invite code
4. Bookings history
5. Savings till date (IMPORTANT)
6. AI bill scan
7. Support
11. AI BILL SCANNING FEATURE (CORE DIFFERENTIATOR)
11.1 Feature Description
User can:
• Click photo of restaurant bill
• AI reads:
o Item names
o MRP values
o Charged prices
• System calculates:
o Overcharge (if any)
o Savings via ENTRY+
11.2 AI Flow
1. User uploads bill image
2. OCR extracts text
3. NLP identifies:
o Beverages
o MRPs
o Quantities
4. Price comparison engine runs
5. Result shown to user
11.3 Output to User
• “You saved ₹X today”
• “Total savings till date: ₹Y”
• Flag if overcharging detected
This feature builds trust + brand credibility
12. SAVINGS TRACKER (VERY IMPORTANT)
• Each bill scan updates:
o Session savings
o Lifetime savings
• Display prominently on dashboard
• Used as:
o Retention hook
o Value reinforcement
o Marketing proof
13. RESTAURANT DASHBOARD
13.1 Restaurant Onboarding
• Enter GST number
• Auto-fetch:
o Legal entity name
o Address
• Manual fields:
o Brand name
o Location
o Manager name
o Manager phone
Other data pulled from:
• Google Places API
13.2 Restaurant Dashboard Views
• Today’s bookings
• Upcoming reservations
• Slot-wise covers
• Entry+ vs non-ENTRY+ ratio
• Simple performance metrics
14. ADMIN DASHBOARD
14.1 Admin Controls
• User management
• Restaurant approval
• Subscription analytics
• Revenue dashboards
• Booking analytics
• Invite code control
• City-wise growth
• AI scan usage stats
14.2 Analytics Required
• DAU / MAU
• Subscription conversion
• Booking conversion
• Savings generated
• Restaurant performance
• Churn metrics
15. USER BEHAVIOR ANALYTICS
Track:
• App opens
• Searches
• Clicks
• Bookings
• Bill scans
• Subscription upgrades
Use:
• Mixpanel / Amplitude / GA4
16. SCALABILITY REQUIREMENTS
Initial Capacity
• Users: 200,000+
• Restaurants: 2,000+
Architecture Must Support:
• Multi-city expansion
• Multi-language (future)
• Feature toggles
• Load balancing
• Cloud-native scaling
17. TECH STACK (RECOMMENDED)
Frontend
• Web: Next.js / React
• App: React Native / Flutter
Backend
• Node.js (NestJS / Express)
• REST APIs (future GraphQL optional)
Database
• PostgreSQL (primary)
• Redis (caching)
AI / OCR
• Google Vision API / AWS Textract
• Custom logic layer
Hosting
• AWS / GCP
• Dockerized services
18. SECURITY & COMPLIANCE
• OTP-based login
• Secure payment handling
• GDPR-style data practices
• Audit logs for admin actions
19. FUTURE EXPANSION (MUST KEEP IN MIND)
• Social features
• Co-working memberships
• City ambassadors
• Dynamic pricing
• AI dining assistant
All architecture decisions must not block future features.
20. NON-NEGOTIABLE PRINCIPLES
1. Single backend for Web + App
2. Clean modular architecture
3. No hardcoding business logic
4. Feature toggles everywhere
5. Analytics-first development
6. Performance over cosmetics
21. FINAL NOTE TO DEVELOPMENT TEAM
ENTRY+ is not a feature-heavy app —
it is a trust-driven platform.
Every line of code should support transparency, stability, and scalability.