I’m looking for a seasoned PHP-Laravel developer to craft a fully-custom admin and customer portal that revolves around robust user management yet extends into everyday business operations. Core build I already have the high-level structure mapped out: Super Admin, Admin, Partner Admin, Partner Manager, Customer, and Customer User all need separate dashboards with role-based permissions. Each of those roles must be editable from the Super Admin panel, and activity for every account (login, logout, key actions) has to be logged for quick auditing. Operational modules • Inventory Management – add, update, track stock, set low-quantity alerts. • Service Subscription & Renewal – create plans, set expiry reminders, prorate upgrades or downgrades. • Wallet & Online Payments – recharge balance, collect payments, show real-time wallet history, integrate popular payment gateways. • Invoicing & Collections – auto-generate invoices from subscriptions or wallet usage, expose PDF/print options, mark payments as received. User management features – Create, deactivate, or delete accounts in bulk or individually. – Assign or revoke granular permissions for Super Admin, Admin, Partner Admin, Customer, and Customer User. – Record user actions with a timestamped log searchable by role, date range, or action keyword. Tech expectations Laravel 12 (or the latest stable), Blade or Inertia/Vue for the front end, Eloquent ORM for data access, and best-practice RESTful routing. Code must follow PSR-12, be fully commented, and ship with a concise README covering local setup. Deliverables 1. Complete Laravel source code committed to my private Git repository. 2. SQL migrations and seeders for initial roles, permissions, and sample data. 3. Front-end views/components matching the role hierarchy. 4. Tested payment gateway integration (sandbox keys provided). 5. Activity log module with filter & export. 6. Step-by-step deployment guide for a standard LAMP stack. Acceptance criteria A role-based test matrix must pass for every module; no unauthorised role should reach restricted routes. PHPUnit or Pest coverage for critical services (auth, payments, subscriptions) at 80 % minimum. If this scope matches your expertise, let me know your estimated timeline, any clarifying questions, and the stack enhancements you’d suggest before we kick off.