Summary We are building a marketplace where providers can subscribe to paid plans and purchase visibility add-ons. We need a Laravel developer to build our subscription module, add-ons, and a manual payment flow (bank transfer + receipt upload). Start your cover letter with a subscription in capital letters or be ignored. This will be the core revenue engine for the platform. Responsibilities 1. Build subscription plans (Free, Mid, Top) with upgrade/downgrade logic 2. Build Add Ons: Spotlight (per-day) and Featured Ads (per day/week/month) 3. Create a unified manual payment flow: 3. 1 User selects plan/addon 3.2 Uploads bank/bitcoin receipt 3.3 Admin approval dashboard 3.4 Auto activate subscription/addon on approval 3.4.1 Build provider dashboard pages to manage plans and add ons 3.4.2 Build admin pages to control plans, pricing, slot limits and approvals 3.4.3 Implement expiry logic for plans and add ons 3.4.4 Write clean migrations, models, and service classes 3.4.5 Ensure other modules can easily check plan status (helper methods) Requirements - Strong Laravel 9/10 experience - Experience with subscription or membership systems - Strong understanding of database design - Experience building admin dashboards and approval workflows - Ability to write clean, reusable service-layer code - Good communication and independent problem solving Nice to Have - Experience with marketplace platforms - Experience with Stripe/PayPal (future integration) - Experience working with multi-role systems (user/provider/admin) - Understanding of event-driven logic (for auto activation) Full detailed scope will be provided to selected candidates. You will be asked to answer the following questions when submitting a proposal: Have you built a subscription or membership system before? Have you implemented manual payment flows (receipt upload + admin approval) in past Laravel projects? If you had to design a unified payment_requests table for subscriptions and add ons, how would you structure it? How would you trigger auto-activation of a subscription after admin approves a payment? (Event? Observer? Direct call?) What would you do to ensure your subscription logic does not break when other modules depend on it later?