Budget: up to €1500 (fixed price) Timeline: up to 8 weeks Tech preference: Laravel 10/11 + Blade, MySQL/MariaDB. Stripe only for the MVP (PayPal can be Phase 1.5). What I’m building I’m building QR2Sell, a small SaaS where users create a Listing (car / real estate / business), generate a static QR code (1 QR → 1 Listing), and then purchase a digital package plus optional extras. There’s also an optional physical product purchase, but printing/fulfillment is manual in Phase 1 (no print provider APIs yet). The key requirement is a single cart + single payment that can include: digital package (one-time) optional upsell (“Remove Branding”) optional subscription optional physical product Must-have (Phase 1) Authentication Register / login / logout Forgot password + reset password by email (time-limited token) Listings + QR Create / edit / delete listings (basic fields) Public listing page by slug Generate a static QR that points to the public listing URL Activate/deactivate a listing (status stored) User dashboard List all listings/QRs Activate/deactivate listings Downloads area for purchased files Order history Admin dashboard Manage subscription plans: name, price, billing period, active QR limit Manage physical products and sizes as data: size = width / height / unit (cm/inch) enable/disable sizes per product Manage orders and order statuses (manual fulfillment workflow) Billing One-time “Digital Package” purchase + optional “Remove Branding” upsell Subscription plans limit the number of ACTIVE QRs If a subscription expires, existing QR pages must keep working (only block creating/activating beyond the limit) Stripe for MVP Deliverables Code in my Git repo Staging deployment (shareable URL) Basic setup docs (README + .env notes + migrations) Out of scope (Phase 1) Analytics Dynamic QR / QR expiration Logo upload Premium templates Print provider API integration Prototype / references I have a short video prototype and a WordPress prototype showing the intended flow and UI. I’ll share these on request with shortlisted candidates. Please confirm you’re happy to review them and align the build accordingly. Payment plan (milestones — required) I’m paying by milestone delivery (no large upfront). I’m open to small adjustments, but milestone-based delivery is a must. Milestone 1 — Setup + Auth + Password Reset (€300) (Week 1–2) Acceptance: register/login/logout works forgot password emails work and reset works (token expires) repo + staging live Milestone 2 — Listings + Public Page + QR (€350) (Week 2–4) Acceptance: listing CRUD public page by slug QR points to the public page activate/deactivate works Milestone 3 — Subscriptions: active QR limit (€350) (Week 4–6) Acceptance: admin can create/edit plans (price + active QR limit + billing period) limit enforced only on ACTIVE listings expired subscription does not break existing public pages Milestone 4 — Single checkout + Stripe + downloads (€500) (Week 6–8) Acceptance: single cart supports: digital package + remove branding + subscription + optional physical product single Stripe payment after payment, user can download the digital file(s) in dashboard (at least an A4 PDF to start) orders visible in admin with statuses When you apply, please answer Share 1 example of a Laravel project you’ve done with Stripe + subscriptions (link/screenshot is fine). How would you implement “subscription limit by ACTIVE items” while keeping existing public pages working after expiry? Confirm you can work with Git + staging + milestones (Yes/No). What PDF generation approach would you use in Laravel (and what limitations should I expect)?