Product Overview

What We're Building

Jubiloop is an event planning platform. Authentication, organizations, and event creation are available in the webapp. Event updates and draft event-plan creation currently have API support only. The block-based planning experience, AI generation, vendor discovery, and guest portal described below are product direction and are not all shipped.

Problem

When planning a wedding and other events, we ran into:

• Didn't know what kind of venue to use or what we needed at all
• Don't want to set everything up from scratch each time
• Finding vendors is time-consuming and you don't know who's reliable
• Event photos end up scattered across different phones and lost

Solution Approach

Core Planning System

Status: partially implemented. Users can create events in the webapp. Event updates and draft plan variations have API support; their UI remains planned, along with editing blocks, tasks, budgets, collaborators, personnel, comments, and detailed permissions.

Events are built from "blocks" - modular components like venue, catering, entertainment. Each block contains tasks, notes, and budget items. Users can organize blocks in a draft area for brainstorming, then create multiple plans to compare approaches. One plan becomes the active plan for execution.

This gives flexibility without overwhelming users with a blank canvas.

AI Integration

Status: planned.

LLMs can generate decent event plans from basic inputs (event type, budget, guest count). We use this to give users a starting point they can modify. Also useful for vendor search and budget suggestions.

The AI is additive - the platform works fine without it, but it speeds things up.

Vendor Discovery (Phase 1: Search)

Status: planned. Vendor discovery is not a current product capability. The sequence remains search, directory, then marketplace.

Start with web search integration - AI searches for vendors and presents options. We cache results to build our own database over time. This avoids the complexity of building a marketplace while still solving the vendor discovery problem.

Phase 2 (future): Full marketplace where vendors can join, get reviews, handle bookings.

Guest Portal

Status: planned. The public guest portal is not currently available.

Each event gets a public-facing website where guests can:

• RSVP with dietary restrictions, plus-ones, etc.
• Upload and view photos
• See event details and updates
• Participate in discussions

This solves the photo collection problem and gives events a social element.

Target Users

Starting with consumers planning personal events:

• Weddings (complex, high-value, people care a lot)
• Birthday parties
• Family reunions
• Small community events

Later expansion to event planning businesses (they need team features, client management).

Product Decisions

Why separate draft area and multiple plans?

• Users need to experiment without breaking their plan
• Clear mental model (draft = brainstorming, plans = structured approaches)
• Enables "what-if" scenarios and plan comparison

Why blocks instead of tasks?

• Events naturally decompose into vendors/areas (venue, food, music)
• Blocks can support different planning needs
• Templates become collections of blocks

Why start with vendor discovery instead of a marketplace?

• Marketplace is complex (onboarding, quality control, payments)
• Discovery gives immediate value without vendor onboarding
• Repeated discovery can inform a future directory
• Natural progression: search → directory → marketplace

Revenue Model

Subscription Tiers

• Free: Individual users, basic features
• Individual (TBD pricing): Personal event planning with enhanced features
• Team/Business (TBD pricing): Multiple users, team collaboration features

Add-ons

• AI credits (pay-as-you-go for heavy users)
• Photo storage (for events with lots of guest uploads)
• Premium templates
• Custom domains

Future Revenue (Vendor Marketplace)

Once we have vendor marketplace:

• Commission on bookings (3-5%)
• Lead generation fees
• Featured listings
• Vendor subscriptions for advanced features

MVP Scope

This section is the planned MVP target, not a list of currently shipped features.

Must Have

• Event creation with basic blocks (5-7 types)
• Draft area and multiple plan creation
• Task management within blocks with basic collaboration (invite users, assign tasks)
• Budget tracking
• Basic AI plan generation
• Vendor discovery
• Simple guest portal with RSVP and photos
• User authentication and workspaces
• Task-level comments (nice to have)

Potential Future Features

Some features we're considering based on initial thinking (will be refined based on user feedback and business needs):

• Chat-based AI iteration
• Vendor database building from searches
• Advanced collaborative planning (real-time editing, permissions, full comment system)
• Advanced portal features (discussions, live updates)
• Mobile apps

Future Business Features

As we expand to the B2B market, we'll need business-focused features. Potential areas include:

• Team management and permissions
• Client relationship management
• Project management tools specific to event planning
• Integration with business systems
• Enterprise features

The exact features will depend on user research and market demand as we scale.

Vendor Strategy Evolution

All vendor phases below are planned and should be delivered in order. No vendor table or vendor search API is currently active.

Phase 1: Search (MVP)

• Search the web for relevant vendors
• Use AI to summarize results and recommend vendors
• Show contact info, websites, basic details
• Retain useful results to improve future discovery

Phase 2: Directory

• Build a structured vendor directory from prior discoveries
• Allow users to save preferred vendors
• Basic vendor profiles (auto-generated from web data)
• User can add notes about vendors

Phase 3: Marketplace

• Vendors can claim and manage profiles
• Reviews and ratings system
• Direct booking through platform
• Payment processing
• Lead distribution