Vesperevents/blueprint/portal

VESPER Events — Hospitality Operations Intelligence Blueprint VESPER Events — Hospitality Operations Intelligence Blueprint Confidential · Youtiva Blueprint 1 Business Overview 2 Pain Points Workflow 3 Current Workflow 4 Optimized Workflow Build 5 System Architecture 6 Execution Proof 7 Case Studies 8 Live Demo Investment 9 Investment Business Overview VESPER Events — Hospitality Operations Intelligence A proven, 12-year Brooklyn hospitality operator — two event venues and a restaurant, 1,000+ events delivered, running on manual coordination across four disconnected tools. The business already works. The limits now are moving information by hand and the lack of per-event financial visibility. This blueprint consolidates it into one home base — and shows Joe his own margins before each event happens. Key Metrics $5–7M Annual revenue across 2 venues + restaurant · 30–40% per-event margin 1,000+ Weddings & events delivered over 12 years — the framework is proven 365 Hard ceiling — one event per venue per day. Growth comes from margin & labor leverage, not more bookings Business Profile Business Name VESPER Events Business Type Hospitality & event operations — venue ownership + full event execution Industry Weddings Corporate Events Private Events Assets 2 event venues + 1 restaurant — a luxury space and an affordable Brooklyn-style rooftop space (Brooklyn, NY) Wider Group Part of a family of businesses — residential & commercial real estate, 3 hotels, capital markets. Shared accounting team across all entities. Team Size ~9–10 full-time (planners, designer, coordinator, ops director, chef) + part-time servers & bartenders per event Revenue ~$5–7M annually · 30–40% per-event margin · ~100 events per year Capacity Model Fixed — one event per venue per day. Hard 365-day ceiling by design. Core Assets The framework (how every event runs) + the historical record (what every event cost, ate, and timed) Stage Diagnosis The business works — "it kind of already works." The bottlenecks are operational coordination and financial visibility, not sales, demand, or execution. Current Tech Stack Mikla — ~$300/mo AI lead qualification & sales communication (Claude-based). Handles initial client conversation and tour booking. Works — not a bottleneck. Tripleseat — ~$400/mo Event CRM, calendar, client communications, invoicing Prism / AllSeated — ~$1,000/mo Spatial floor planning built to venue architecturals Google Sheets The fill-out sheet — the real working document, copied & hand-edited per event Google Drive Photos, assets, contracts — pulled and emailed manually ACH / Check Payment collection — no credit cards, a deliberate choice to avoid fees Roughly $20K/year in killable or consolidatable subscriptions — the natural baseline for the investment conversation. The team's real cost, though, is the manual labor of moving information between these four tools and email. The North Star The Vision — In Their Own Words "It all lives in one home. A home base." One privately-owned operating system that consolidates four disconnected tools into a single platform — for both the client's front-end experience and the team's back-end operations. Every wedding feels unique to the client while the business runs from one intelligent framework — and Joe can see the profitability of every event before he approves it. VESPER Events · Hospitality Operations Intelligence Blueprint · Youtiva Pain Points → Pain Points It Already Works. The Coordination Doesn't Scale. VESPER has run successfully for 12 years and proven the model 1,000+ times. Sales aren't the bottleneck. Demand isn't. Execution isn't. The cost is in everything around the event — the manual data movement between four tools, and the fact that Joe can't see what an event makes until after it's over. Core Bottlenecks Category The Problem The Cost Pricing As guest count (100→120→200) and menu tier (base vs. filet/lobster/truffle) change, the planner re-cross-references the one-month balance against the contract by hand. Planner time, error risk, slow turnaround to clients. Payments Manual, color-coded reminder schedule. On every payment, the invoice and the Google Sheet are updated separately, and confirmation emails sent by hand. Administrative burden, cash-flow lag. Coordination The same event data is re-entered across Tripleseat, AllSeated, Sheets, Drive, and email. Assets are pulled from Drive and emailed manually. Duplicate work, lost context, planner time. BEO Creation The banquet event order is compiled manually from the fill-out sheet for every event. Duplicate work, manual compilation. Staffing Deterministic rules (1 server per 10-guest table, 1 bartender per 50 guests) live only in the ops director's head; crew is emailed/texted ~1 week out. Single point of failure as event volume grows. Food Cost Order quantities are estimated from the chef's memory (e.g. the Korean fried chicken done thousands of times) rather than from costed recipes. Possible waste, no cost accuracy, no margin baseline. Financial Visibility No per-event or per-venue P&L. Client payments aren't linked to the food, beverage, and labor costs they generate. Can't defend or predict margin under rising costs. Operational Knowledge The framework, staffing logic, and cost know-how live in people — the planner, the ops director, the chef — not in any system. Key-person dependency. Scaling limitation. Why the Current Model Strains at Scale The Coordination Problem Revenue is capped by design — one event per venue per day. So growth comes from labor leverage and margin , not more bookings. Every new event adds more emails, reminders, and manual cross-referencing before it adds any execution difficulty. Joe won't open a third venue if it means his planners and ops lead lose the mental capacity to keep up. The system scales slower than the venues. Two Things Called "Vendors" — Keep Them Separate Event vendors (the couple's florist, DJ, photographer) are information the couple enters into the fill-out sheet for the BEO and timeline — they are not portal users and don't transact in the system. Supply vendors (net-30 produce, beverage) are a cost input to the accounting engine. The earlier "connected vendor coordination" concept conflated these and has been removed. ← Overview Current Workflow → Current Workflow Every Step. Manual Coordination. VESPER runs a 15-step process from lead through financial review. Sales and execution work. The middle — planning, pricing, payments, BEO, staffing — runs entirely through four tools and email, with people holding the information and re-entering it at each handoff. How the Workflow Runs Today — And Where It Breaks # Step How It Happens Today The Friction 01 Lead Generation Website, The Knot, WeddingWire. Multiple channels feeding in. 02 Qualification Mikla (automated, Claude-based). Works well. Not a bottleneck. 03 Venue Tour Sales director walks the space, captures wants and needs in conversation. Notes live in email; no structured capture. 04 Contract + Deposit Contract drafted to the couple's date & needs. 25% deposit. The contract is "the Bible" — it sets price, date, terms. Manual drafting and data transfer. 05 Planner Handoff Sales director introduces the planning team to the client by email. Context loss between sales and planning. 06 Fill-Out Sheet Google Sheet template copied and hand-edited per event (names, date, food minimum). Manual setup, re-entry from the contract. 07 Client Planning Back-and-forth in the Sheet + email — design, timeline, menu, ceremony, seating. Scattered, repetitive, limited client experience. 08 Pricing Adjustments Planner recalculates the one-month balance by hand as guest count and menu tier change. Error-prone cross-referencing against the contract. 09 Payment Tracking Manual color-coded schedule; invoice + Sheet updated on each payment; reminders sent by hand. Administrative burden, follow-up load. 10 Floor Planning AllSeated — a separate tool, built to venue architecturals. Another system to leave and re-enter. 11 BEO Creation Banquet event order compiled manually from the fill-out sheet. Duplicate work. 12 Staffing Ops director applies rules of thumb; emails/texts part-time crew ~1 week out. Knowledge in one head; no system support. 13 Food Ordering Chef reads the BEO and orders from memory and experience. No cost accuracy; possible over-ordering. 14 Event Execution Team coordination on the day. Proven over 1,000+ events. Not the bottleneck. 15 Financial Review Shared AR/AP team, after the fact, across many businesses. No event-level P&L; margin only visible in hindsight. The financial blind spot compounds all of the above. Costs (food, beverage, labor) are never linked to the payments a specific event brings in. Joe knows his expenses and his event count, but cannot see whether a given event is profitable before he commits to it — only after. This is the single highest-value gap the system closes. ← Pain Points Optimized Workflow → Optimized Workflow Every Venue Stays. Information Moves Automatically. Every venue stays. Every planner stays. Every operator stays. What changes is the layer that moves information — replacing the four-tool shuffle with one home base, replacing manual pricing with a contract-driven engine, and giving Joe the numbers on every event before he approves it. The Priority Stack — This Is the Build Order Priority 1 — Consolidation Into One Home Base Collapse Tripleseat, AllSeated, Sheets, Drive, and email into one platform. The fill-out sheet becomes a guided client flow; the BEO generates itself. "It all lives in one home. A home base. That's the idea." Priority 2 — Margin Visibility Before the Event Per-event and per-venue P&L, predicted before approval, with a spend target attached. "You can only spend $8,000 on food and $10,000 on labor to make this event happen." The team is handed a number to beat — not a free hand. Priority 3 — Dynamic Contract Pricing Guest count and menu tier auto-recalculate the balance against the contract. "We have the information at our fingertips — we just have to go through the manual process." The platform removes that manual process. Priority 4 — Operational Intelligence Deterministic framework rules (staffing ratios) plus historical cost baselines (recipe × invoice price) compound over time. Honest framing: this is a rules engine + cost lookups that sharpen as new events are captured — not a black-box model. The foundation built first is what this grows on. Change Management — A Precondition, Not a Footnote Introduced as Load Reduction — Led Through the Team Joe raised this three times: his crew is largely part-time and middle-income, and he does not want anyone feeling "something's coming for them." The system is introduced as load reduction , with role-based views so each person sees only their part. Adoption is led through the ops director and chef — both of whom Joe says would be "very grateful" for a real program. The Optimized Flow — From Client to Event Step How It Works in the System The Win 01 · Onboarding Contract is signed; the client gets instant portal access. The contract — "the Bible" — pre-fills the date, names, terms, and price. No copied Google Sheet. Setup is automatic; nothing re-entered by hand. 02 · Guided Planning The couple works through a guided fill-out flow — design, timeline, menu, ceremony, seating — that feels custom but runs on the proven framework. One structured space; nothing lost in email. 03 · Dynamic Pricing As guest count (100→120→200) and menu tier change, the balance recalculates automatically against the contract. No manual cross-referencing; instant, accurate quotes. 04 · Floor Plan The couple arranges tables within set layouts via embedded AllSeated; the team reviews and approves. One platform — no separate tool to leave. 05 · Vendor & Items The couple enters florist, DJ, and photographer details and personal items, feeding the BEO and timeline. Complete event data captured at the source. 06 · Payments Automatic schedule, reminders, and status; ACH/check confirmation kept — no forced card fees. Better cash flow; the admin burden is gone. 07 · Team Review & BEO The team monitors planning in the admin portal; the BEO generates itself from the fill-out data. No manual compilation; the BEO is always current. 08 · Staffing The rules engine recommends crew (1 server/table, 1 bartender/50 guests) and drafts the call sheet — validated with the ops director. Knowledge out of one head; consistent as volume grows. 09 · Food & Cost Recipe quantity × historical invoice price sets a cost baseline; the chef verifies and orders. Order accuracy, less waste, a real margin baseline. 10 · Margin Check Per-event P&L is predicted, with spend targets, before Joe approves the event. Margin defended before committing — not in hindsight. 11 · Event Day The team runs the event from one connected source of truth — the same proven execution, fully coordinated. Everyone works from one live picture. 12 · Financial Close Payments are reconciled to the event; per-event and per-venue P&L is finalized. Profitability visible per event and per venue. ← Current Workflow System Architecture → System Architecture One Operational Foundation — Two Portals. One Source of Truth. A Client Portal that gives every couple a guided, self-served planning experience. An Admin/Operations Portal that gives the team full visibility and control — including the financials. A shared engine underneath that connects events, payments, costs, staffing, and floor plans into one live picture. Architecture Principle Integrate, Don't Rebuild Mikla stays as the sales front door — recently upgraded, not a bottleneck. AllSeated is embedded or linked , not rebuilt — rebuilding spatial floor planning would consume the entire budget and still trail the incumbent. Tripleseat's functions are absorbed into the platform where consolidation actually pays for itself. The win is one home base — not reinventing every tool from scratch. Client Portal & Operations Portal Every Couple, Their Own Event Environment Every client has their own portal — their event, their agreement, their planning, their payments. They plan, choose, approve, and pay in one structured environment that feels custom while running on the proven framework. The system remembers everything. Nothing gets re-entered. Nothing gets lost. Client-Facing Capabilities Client Portal Event dashboard — overview, countdown, agreement & status Guided fill-out flow — design, timeline, menu, ceremony, seating Dynamic pricing — recalculates against the contract as the event changes Floor plan — embedded AllSeated, arrange tables within set layouts Vendor & items capture — florist, DJ, photographer details for the BEO Payment center — schedule, reminders, invoices, history Communication center — threaded questions the team answers Documents & event history Admin / Operations Portal Internal Team Client & event management — records, history, contracts Planning management — progress, missing-info flags, approvals Auto-generated BEO from the fill-out data Staffing rules engine — recommended crew + call sheet (validate with ops) Financial management — per-event & per-venue P&L, cost baselines, targets Internal AI assist — asset retrieval & client email drafting Communication history per client Executive dashboard — utilization, forecasts, payment status, margin Shared Operational Engine Data Foundation — One Source of Truth Clients, events, venues, payments, costs, inventory, vendors, and documents — all in one connected database. Every portal and workflow reads from and writes to the same source. Honest note: the "1,000+ events" is not yet a clean dataset — it's a thousand Sheets, BEOs, Tripleseat records, and invoices. Because the artifacts are templated, structured cost and staffing baselines can be backfilled — a structuring effort, not pre-existing ML data. Financial Engine — The Highest-Value Workflow Every client payment is linked to its event and the food, beverage, and labor costs it generates. The contract-driven pricing engine recalculates balances automatically. Cost baselines (recipe × historical invoice price) produce per-event and per-venue P&L — predicted before approval, with spend targets. This is the capability Joe spent the most time on, and the only one that touches his wider family of businesses. Workflow Foundation — Routing, Approvals, Reminders Contract → fill-out → dynamic pricing → BEO → payments → staffing → execution → P&L. Each step triggers the next. Automation layer: payment reminders, missing-information alerts, planning milestones, internal task creation. The team stops manually moving information between steps and tools. Memory Foundation — Compounds Over Time "Learning" here means structured capture going forward — every new event sharpens the cost and staffing baselines. Deterministic framework rules + historical cost lookups, getting more accurate with use. This compounds on the foundation Phase 1 creates — it is not a Phase 1 deliverable on its own. ← Optimized Workflow Execution → Execution Four Phases · 60 Days Each — Capture → Execute → Account → Intelligence. Each phase is a standalone win you can fund one at a time, and each makes the next more valuable. Two 30-day stages per phase, built in dependency order — the client + admin foundation first, the AI that knows VESPER last. Development Timeline You start using the system at Day 60 — not after 8 months. Phase 1 goes live and runs your planning operation the moment it's done. Every later phase ships onto the live product while you're already using it, so value compounds from month two — you never wait for the full build. Phase 1 Client + Admin Foundation replaces the spreadsheet ▲ Goes live · Day 60 60 Days Stage 1 30 Days Client Onboarding & Guided Planning We build the post-sale entry and the couple's planning experience. The signed contract carries over and pre-fills the event — no re-typing — the planning team is introduced, and the guided fill-out flow replaces the Google Sheet: design, timeline, menu, ceremony, seating . Plus dynamic pricing that recalculates against the contract, the payment center (schedule, reminders, ACH/check), messages, and documents. Stage 2 30 Days Admin Event Module We build the team's side of the portal. The admin receives every event , sees the upcoming-events pipeline and each event's full info, and flags what's missing per event — which fill-out sections the client hasn't completed yet. Document upload, answering client messages, and the auto-generated BEO from the fill-out data. End of Phase 1: the Sheet / Drive / email shuffle is gone. Phase 2 Operational Intelligence gated on the ops director & chef ▲ Live · Day 120 60 Days Stage 1 30 Days Staffing & Vendors We build the modules that turn a finished event into the work each team does. The staffing rules engine derives crew from guest count (1 server per 10-guest table, 1 bartender per 50) and drafts call sheets. Vendor coordination handles event vendors (client-entered) and supply vendors (cost inputs) as separate things. Stage 2 30 Days Kitchen & Ordering We build the kitchen module. Recipe × invoice cost baselines produce prep and order lists, with inventory, lead-time, and vendor-cost intelligence to cut waste. The internal AI assist (asset retrieval, email drafting) and the automation / reminder / task layer thread through both stages of this phase. Phase 3 Financial Intelligence the margin-defense tool ▲ Live · Day 180 60 Days Stage 1 30 Days Per-Event & Per-Venue P&L We build the prediction side. Cost baselines plus revenue produce a per-event and per-venue P&L , with margin predicted before Joe approves the event and spend targets set for the team — "beat $8k food / $10k labor." Stage 2 30 Days Accounting · Payables & Receivables We build the actuals side. Link payments ↔ events ↔ costs , match net-30 produce invoices, payroll, and bank receipts, and roll up monthly per venue — "10 events in May; here's revenue, expenses, payroll, and profit." Receivables in, payables out, reconciled to each event. Phase 4 VESPER Intelligence the event-planner AI ▲ Live · Day 240 60 Days Stage 1 30 Days Admin Co-Pilot We build the AI that knows VESPER. Trained on the framework, events, and accounting from Phases 1–3, it answers business questions in plain language and supports decisions — surfacing margin and risk patterns across the data so Joe can ask his own connected numbers anything. Stage 2 30 Days Client Planning Assistant We build the couple-facing event-planner AI. Scoped to that couple's event plus VESPER's planning knowledge, it guides how to plan and answers event and venue questions on-framework — handling the repetitive questions for the team, and walled off from internal financials . Live from Day 60 Phase by phase each phase ships onto the live system · fund one at a time · ~8 months to the full build What the Full System Delivers Delivered Client portal Onboarding, guided fill-out, dynamic pricing, payments, comms, documents — one environment per event Admin portal Receives every event, contract + sales handoff, planning review/approve, auto-generated BEO Dynamic pricing Guest count + menu tier recalculate the balance against the contract automatically Floor plan & seating Embedded AllSeated, vendor & items capture, guest assignments Staffing rules engine Recommended crew + call sheets — validated with the ops director Kitchen, cost & inventory Recipe × invoice baselines, ordering quantities, lead times, less waste Internal AI assist + automation Asset retrieval, email drafting, reminders, missing-info alerts, task creation Financial intelligence Pre-event P&L prediction + reconciled accounting (payments, invoices, payroll) per venue What the System Replaces Copied Google Sheet Replaced — guided digital fill-out flow Sales → planning email handoff Replaced — contract pre-fills, context carried Manual pricing math Replaced — contract-driven pricing engine Color-coded payment tracking Replaced — automatic schedule, reminders & alerts Manual BEO + tool re-entry Eliminated — auto-generated from one source of truth Guess-based ordering Replaced — recipe × invoice cost baselines Hindsight-only financials Replaced — pre-event prediction + reconciled actuals Knowledge held in people Captured — rules, baselines & accounting in the system Future Phases & Strategic Upside Future phases are scoped after Phase 1 based on real usage and adoption. The levers below are the case that moves VESPER past "it already works" — sequenced to Joe's own priorities ("maximize for my use first"). Third Venue & Multi-Space Scaling With the operational load lifted, the system supports adding a third venue without adding administrative overhead — the explicit reason Joe wants this before he expands. Onboard a new space onto the same framework and data model in days, not months. Valuation Lift The system becomes an asset that sells with the venues — proprietary operating IP, not just real estate. A documented, transferable operating model can carry a meaningful multiple on exit. Productize for Other Venues The platform can be packaged and sold to other venue owners — Joe knows what they want and don't want after 12 years. Explicitly secondary: "maximize for my use first," then offload. Expand Into the Family Office Once events proves the model, the same financial engine extends to the wider group — real estate, the 3 hotels, capital markets. Events is the controllable beachhead for a larger rollout. Predictive Margin Intelligence As more events are captured, surface which packages, menus, and guest counts deliver the best margin — and recommend pricing and menu adjustments proactively as ingredient costs move. Leadership Dashboards Joe opens one screen and sees upcoming events, venue utilization, revenue & staffing forecasts, payment status, and event profitability — in under a minute, in real time. ← System Architecture Case Studies → Case Studies Real Results — Proof It Works See how Youtiva has built operational intelligence systems for service businesses, field operations, and high-touch client workflows — and what happened after. View Case Studies 📋 Youtiva Case Studies Real businesses. Real results. See the operational intelligence systems Youtiva has built and the impact they delivered. View Case Studies → blueprint.client.youtiva.com/casestudies ← Execution Live Demo → Live Demo The Operational Portal. Live & Interactive. Two portals — one system. Walk through the client planning experience and the admin operations side independently. Both are live and fully interactive. Access the Portals Client Portal VESPER Events — Client Planning Experience Guided fill-out · Dynamic pricing · Floor plan · Payments · Messages · Documents Open Portal → Admin Portal VESPER Events — Operations & Financial Dashboard Event management · BEO · Staffing · Per-event P&L · Payments · Alerts Open Portal → How to experience the system Open both portals side by side. Plan an event in the Client Portal — then switch to the Admin Portal to see it land complete, with the BEO generated and the P&L calculated. That is the loop this system is built on. ← Case Studies Investment → Investment Two Ways To Own the Infrastructure Both paths build the same system — privately owned, fully documented, built to grow. Phase 1 delivers consolidation, dynamic pricing, and per-event financial visibility. Every future phase plugs into the same foundation. Nothing is pre-fixed beyond Phase 1. How We Work Together The Same for Both Investment Structures Phase 1 is scoped, built in stages, and delivered with a working win at each stage. Future phases are defined together based on what the business needs next. Nothing is pre-fixed beyond Phase 1. The system grows with VESPER — not ahead of it. All infrastructure, data, and workflows are owned exclusively by VESPER Events from day one. The Framing — Net Against What You Already Spend This isn't a speculative future bet — it's a maintenance and margin platform measured against today's reality. Weigh it against (1) the ~$20K/year in subscriptions it consolidates or replaces, (2) the planner and admin labor it removes — not accounting headcount, which serves the wider group — and (3) the valuation lift on the real exit asset. Owned outright, on a 2–3 year payback lens. Phase 1 Goes Live Day 60 Client + admin foundation live and running your planning operation — you start using it at month two, not after the full build. Ownership 100% Yours All infrastructure, workflows, pricing logic, and data belong exclusively to VESPER Events from day one. Choose Your Path Lease to Own $2,000 / month Fixed monthly investment — own the system as you build it. Sits right at what VESPER already spends on the tools it replaces. Fixed monthly — predictable investment throughout the build Ownership transfers as each stage is completed and delivered Long-term partnership — continues as the platform expands into future phases Option to convert to full buyout at any point Buy Outright $16,000 / phase One-time per phase, owned outright on delivery. Full build across all four phases: $64,000. One-time payment per phase — no ongoing fees for completed work Each phase fully owned upon delivery Continue into future phases as the business scales Full ownership from day one — per phase delivered What Both Paths Include Same Build. Same Quality. Same Ownership. Long-Term Partnership. Regardless of which path is chosen, the infrastructure built is identical — privately owned, fully documented, built to the same standard. This is not a project with an end date. It is a long-term partnership that grows as VESPER grows. The first time Joe sees a full per-event P&L before approving the event — and a multi-change quote recalculate itself instantly — that alone demonstrates the ROI. Infrastructure 100% Owned Privately built — not a SaaS subscription. VESPER Events owns everything built. IP Protection Full Ownership All data, workflows, pricing logic, framework, and client records belong exclusively to VESPER. Ongoing Support Included Refinements, updates, and support included throughout the engagement in both paths. ← Live Demo VESPER Events · Hospitality Operations Intelligence Blueprint · Youtiva · Confidential