User-Friendly Ad Booking Website Build
Budget: $250 – $750 USD
I’m ready to turn the concept in the two Claude links above into a live, production-ready website where everyday customers can buy screen time for their ads without feeling overwhelmed.
Core flow I need implemented
1. Select a date and time slot on an intuitive calendar and add one or many slots to a cart.
2. Create an order, pay securely (PCI-compliant Stripe, PayPal or similar), and receive an instant receipt.
3. Upload the creative files for each slot through an ultra-simple interface—drag-and-drop or a big “Upload” button with progress feedback. All uploads must land in a moderation queue where my quality-control team can approve, reject, or request changes.
4. After approval, customers can still log in to change or cancel a slot and trigger an automatic, rules-based refund when applicable.
Key priorities
• It must live on the web (no mobile app for now).
• The experience has to be fool-proof for a non-technical 50-year-old uploading a “Happy Birthday” video. Large buttons, plain wording, guided prompts, and clear error messages are essential.
• Security for payments and file storage is non-negotiable.
• I’d like the back-end to follow the architecture sketched in the second link, but I’m open to pragmatic adjustments if you can explain the trade-offs.
Deliverables
• Fully functional website deployed to my hosting (AWS or alternative you recommend).
• Admin dashboard for booking management, QC approvals, refunds, and basic reporting.
• Source code in a private repo plus setup/maintenance documentation.
• A brief Loom or screen-share walkthrough so my in-house team can take it from there.
If this sounds like something you can knock out efficiently while keeping usability front and center, let’s talk timelines and milestones.
Core flow I need implemented
1. Select a date and time slot on an intuitive calendar and add one or many slots to a cart.
2. Create an order, pay securely (PCI-compliant Stripe, PayPal or similar), and receive an instant receipt.
3. Upload the creative files for each slot through an ultra-simple interface—drag-and-drop or a big “Upload” button with progress feedback. All uploads must land in a moderation queue where my quality-control team can approve, reject, or request changes.
4. After approval, customers can still log in to change or cancel a slot and trigger an automatic, rules-based refund when applicable.
Key priorities
• It must live on the web (no mobile app for now).
• The experience has to be fool-proof for a non-technical 50-year-old uploading a “Happy Birthday” video. Large buttons, plain wording, guided prompts, and clear error messages are essential.
• Security for payments and file storage is non-negotiable.
• I’d like the back-end to follow the architecture sketched in the second link, but I’m open to pragmatic adjustments if you can explain the trade-offs.
Deliverables
• Fully functional website deployed to my hosting (AWS or alternative you recommend).
• Admin dashboard for booking management, QC approvals, refunds, and basic reporting.
• Source code in a private repo plus setup/maintenance documentation.
• A brief Loom or screen-share walkthrough so my in-house team can take it from there.
If this sounds like something you can knock out efficiently while keeping usability front and center, let’s talk timelines and milestones.