Description
Summary About the project: CVGamePass is a digital ticketing platform built for Central Valley high school athletics. Our mission is simple: give every school in the region a modern, professional way to sell tickets, and give fans a seamless way to support their teams. No more cash boxes at the gate, no more lost revenue, no more lines. Schools keep more of their money, get real-time attendance data, and grow their programs — and as they grow, we grow with them. The platform is live at https://cv-gamepass-935.created.app/ and the core product is built: event listings, ticketing flow, school pages, and an admin dashboard. It was developed on Created.app (an AI app builder), and we're now at the stage where it needs an experienced developer to take it from "mostly working" to production-grade — the kind of platform a school athletic director trusts with their gate revenue on a Friday night. This is not a throwaway gig. We operate the fastest-growing girls basketball recruiting brand in the Central Valley, run a children's nonprofit that has served over 10,000 kids, and have deep relationships with schools across the CIF Central Section. CVGamePass has a built-in customer pipeline. The developer who gets this platform stable becomes our first call for everything that comes next. Phase 1 — Full platform audit (paid milestone): Before any code is written, go through the entire platform as a fan, as a school admin, and as a bad actor. Deliver a written report covering: Every bug, error, and broken flow you find UX friction points and dead ends Security concerns (auth, payment handling, data exposure, admin access control) Performance issues on mobile — most of our fans will buy tickets on their phones in a parking lot Your recommendation: fix in place on Created.app, or migrate to a conventional stack — with honest reasoning and cost implications for each path We'll finalize Phase 2 scope and pricing based on this report. Phase 2 — Core fixes and completion: 1. Account creation and authentication Signup currently fails for users. Diagnose and fix the root cause. Two clean account types: fans and school admins, with proper role-based access Email verification, password reset, and session handling that just works School admin onboarding flow: a new school should be able to sign up, get verified by us, and start listing events same-day 2. Complete Stripe payment infrastructure Full checkout flow: fan selects event, picks ticket quantity, pays, and instantly receives a ticket (QR code) via email and in their account Stripe webhooks for payment confirmation, failed payments, and disputes Refund and event-cancellation handling (school cancels a game → fans automatically refunded) Stripe Connect for school payouts: each school gets connected as a recipient so their gate revenue flows to them automatically, with our platform fee taken out per transaction. If you'd recommend a different payout architecture, make the case in your proposal. Clean receipts, transaction history for fans, and revenue reporting for schools 3. School admin dashboard Schools manage their own locations/venues: add, edit, and remove facilities with addresses and capacity Full event management: create, edit, reschedule, and cancel games; set ticket types, prices, and capacity; see live sales counts Changes reflect immediately on the public-facing site A revenue view: tickets sold, gross sales, payout status per event 4. The fan experience Mobile-first ticket purchase in under a minute Tickets accessible in account and by email, with QR codes ready for gate scanning Simple gate check-in tool: a school volunteer opens a scan page on their phone, scans the QR, ticket validates once and can't be reused Phase 3 (future, for the right partner): Season passes and family bundles, multi-school tournament ticketing, promo codes, attendance analytics for athletic directors, and integration with our other Central Valley sports products (recruiting platform, highlight tape tools, school sports sites). Scoped and paid separately — mentioned so you understand the trajectory. Required experience: Production Stripe integrations, ideally including Stripe Connect / marketplace payouts Full-stack debugging: auth systems, databases, API layers, webhook reliability Mobile-first frontend work — this platform lives on phones Experience with AI-builder codebases (Created.app, Lovable, Bolt, Mocha) or migrating off them is a major plus Strong written English — the audit report and ongoing communication matter How to apply: Visit the platform and attempt to create an account In 2-3 sentences, tell me what you observed and your initial theory on the signup failure One sentence on whether you'd recommend Stripe Connect for school payouts and why Your relevant Stripe/marketplace project links Generic or copy-paste proposals will be skipped. We're looking for the developer who treats this like their own product. Budget: Fixed-price by milestone. Quote Phase 1 (audit) in your proposal; Phase 2 will be quoted after the audit report.