Project Overview Replace TicketSpice with a custom-built Lovable + Authorize.net event website and ticketing system. The current stack has design limitations, platform friction, and poor website integration. The new system needs to handle event marketing, ticket sales, checkout, accounting, and on-site check-in for Boot Camp and future events.
Why This Matters Top Rep is about to market Myrtle Beach 2027 and future events. A better funnel improves conversion and brand cohesion, but a weak ticketing backend creates downstream accounting and event-day failures. The replacement decision also affects conversion, event merchandising, and how fast the team can ship a credible boot camp site.
Workstreams
- Event Website Build (Paul Gregorio)
Build the first Lovable draft of the event website Structure the draft so the team can evaluate both design quality and the eventual checkout flow Site may need to showcase multiple events across the year Coordinate with Noah on integrations and implementation constraints
- Payment and Backend Integration (Noah Wessel)
Build a working Lovable + Authorize.net event funnel demo Wire the backend and run a test payment Confirm Authorize.net batches land in a QuickBooks-friendly way similar to current TicketSpice deposits Support any needed integrations for the event website
- Accounting, Check-in, and Export Validation (Chris Thokey)
Validate that the new flow works for accounting and event-day operations Confirm support for: deposits, CSV exports, attendee counts, ticket lookup flows Review before any cutover decision is made Go/no-go criteria for when Myrtle Beach can move off the current stack
- Event Website Copy and Messaging (Valerie Schultz)
Review page copy once the first draft is ready Messaging should speak to owners and sales leaders as the real buyers, while allowing reps to self-select Pull in strongest proof and pressure-test the conversion path Copy choices depend on current offer stack, owner-vs-rep ICP, and what purchase paths remain self-serve
PRD Requirements The PRD must document end-to-end requirements before the team decides whether to fully replace TicketSpice: Batching and deposit handling Unique ticket IDs and attendee lookup Discount codes and stair-step pricing CSV exports for RepCard and badges VIP and shirt-size fields Insurance add-on handling Leader vs rep counts Portal/dashboard ideas Rollback path if the new flow fails review On-site contingency for last-minute attendee changes
Open Questions Single owner for the full migration decision has not been assigned A/B testing: Jet wants to test external-checkout flow vs embedded buying experience rather than assuming the new flow converts better Go/no-go criteria for Myrtle Beach cutover need to be defined Prototype must cover both accounting and check-in edge cases, not just front-end design
Timing Waitlist page needed immediately First event website draft targeted for end of this week (9/4) or early next week Migration update expected by end of this week
Related Tasks (consolidated L10 to-do with all merged context)
Due 2026-09-04