Demo Workspace

Hobbybop Readiness Demo Workspace shows the core organizer path with static fixture data only. It is safe for customer demos because it does not write to production customer tables.

Demo Data Boundary

  • Read-only demo fixture. Does not create accounts, events, guests, orders, groups, sponsor records, or CRM contacts.
  • The demo API is GET-only fixture content for walkthroughs, screenshots, sales calls, onboarding, and support training.
  • Fixture emails use example.com addresses, fixture sources, and demo IDs so they cannot be mistaken for customer-owned records.

Core Demo Flow

  • Workspace Setup: Create or sign in to the organizer account, name the workspace, invite teammates, and confirm billing state.
  • First Event: Draft the first event, set visibility, capacity, timezone, registration rules, checkout mode, groups, and sponsors.
  • First RSVP: Use the public event page to collect the first RSVP or waitlist record without touching demo-only fixtures.
  • Follow-Up: Review AI-assisted follow-up drafts, unsubscribe suppression, no-contact controls, and sponsor recap notes before sending.
  • Analytics: Read the dashboard funnel, source attribution, attendance, revenue, email, sponsor, group, and marketplace signals.

Implemented Readiness Facts

  • /demo renders the read-only workspace story from static fixture data.
  • /api/demo/readiness is a GET-only JSON endpoint with public five-minute caching.
  • Fixture data uses demo IDs, fixture source labels, and example.com emails.
  • The payload declares databaseWrites false and productionSafe true.
  • The workspace story covers event lifecycle, RSVP, CRM, sponsor, group, billing/readiness, and import states.

Event Lifecycle

  • draft: Is this event ready to publish? Event creation supports draft visibility, capacity, timezone, registration, paid-event, group, sponsor, and readiness states.
  • published: Where are attendees coming from? Public event pages expose RSVP, checkout routing, calendar, engagement, and attendee self-service states.
  • live ops: What needs attention at the door? Organizer workflows include guest lookup, check-in, waitlist, poor-network, and event status controls.
  • completed: What happened, and who needs follow-up? Analytics summarize conversion, attendance, revenue, source attribution, sponsor, group, and follow-up signals.
  • follow up: Which follow-up actions are safe to approve? AI drafts, lifecycle playbooks, no-contact controls, unsubscribe suppression, and sponsor recaps remain reviewable before send.

Sample Events

  • Community Workshop Dry Run: completed, 3 fixture RSVPs, free, CSV preview fixture, Denver Creative Operators, Neighborhood Studio Supply, 64% conversion.
  • Paid Summit Walkthrough: published, 3 fixture RSVPs, external checkout, Provider migration fixture, Front Range Founder Circle, Craft Tools Co., 58% conversion.
  • Live Market Operations Demo: live ops, 2 fixture RSVPs, provider test, Meetup webhook reconciliation fixture, Weekend Makers Guild, Corner Roasters, 41% conversion.

RSVP And CRM

  • Maya Demo: first time, hobbybop_rsvp_fixture, first RSVP, workshop, send welcome note.
  • Noel Demo: vip, luma_import_fixture, VIP, checked in, invite to founder circle.
  • Priya Sponsor Demo: sponsor lead, mailchimp_import_fixture, sponsor prospect, proposal review, no-contact respected.
  • Sam Demo: reactivation, csv_import_fixture, waitlisted, reactivation, follow-up draft.

Groups And Sponsors

  • Denver Creative Operators: active, 184 fixture members. Directory privacy, join requests, discussions, albums, series calendars, and moderation routes are represented.
  • Weekend Makers Guild: forming, 47 fixture members. Demo includes membership growth, notification preference, and group-to-event planning states.
  • Neighborhood Studio Supply: fulfilled package. Logo placement, attendee offer, post-event recap, and performance report. Sponsor CRM, deliverables, due dates, evidence, and reporting are visible as fixture facts.
  • Craft Tools Co.: reserved package. Founder lounge mention, reserved placement, invoice-ready proposal, and recap draft. Sponsor marketplace inventory and proposal approval states are represented without billing writes.

Billing And Import Readiness

  • ready: Plan limits, checkout, billing portal, discounts, downgrade, cancellation, failed-payment, receipt, refund, transfer, and payout states are represented with safe status language.
  • ready: Provider-test checkout and external-checkout examples explain paid-event readiness without creating live charges.
  • review: Production secrets and provider credentials are intentionally absent from the fixture payload.
  • csv previewed: CSV contacts are shown as preview rows with duplicate and consent review before commit.
  • eventbrite validated: Eventbrite orders, attendees, refunds, and payout status are represented as provider validation fixtures.
  • meetup webhook reconciled: Meetup RSVP updates demonstrate source record reconciliation and live-ops waitlist changes.
  • luma conflict review: Luma guest imports demonstrate source confidence, conflict notes, and organizer review before apply.
  • mailchimp undo ready: Mailchimp audience imports demonstrate CRM tagging, unsubscribe suppression, and undoable dry-run exports.

Customer Readiness Coverage

  • Imports are shown as preview fixtures before commit.
  • Billing and paid-event demos show portal, checkout, refund, receipt, and payout status language without charging anyone.
  • Groups, sponsor workflows, AI drafts, and privacy controls are demonstrated as reviewable organizer actions.
  • Trust, support, abuse, security, and data-request pages are linked from the same readiness path.