Package the event
Create tiers, quantities, benefits, and public recognition details before publishing.
Build publishable events, receive sponsor applications, send contracts, and track payment status from a workspace shaped around the application lifecycle.
Required fields, packages, imagery, and free-event claim are visible before publish.
Applications carry sponsor profile, package, cover message, and capacity context.
The application record stays the source of truth through e-signature, payment, invoice, and recognition.
Create tiers, quantities, benefits, and public recognition details before publishing.
See sponsor company details, package fit, cover message, and capacity before making a decision.
Approved applications become contract packets, using uploaded PDFs and embedded signing.
After full signature, sponsors pay through Stripe Checkout and invoice generation closes the payment record.
These rules come from the app specs and are intentionally concrete.
Events need at least one package and future start dates before publishing. Suspended organizers cannot publish.
Contract creation requires an active Stripe Connect account so payment can be collected after signature.