Build a client dashboard portal for an Amazon review removal service (React/Node or Laravel)

ABOUT THE PROJECT I run an Amazon agency and I am launching a service that helps Amazon sellers get negative product reviews (1 to 3 stars) removed when those reviews break Amazon's Community Guidelines. For each client, my team finds the violating reviews, reports them to Amazon through its official channels, and tracks the outcome. I need a professional client portal where each client can log in and see exactly what we are doing for them: which reviews we flagged, which cases are open, which reviews were removed, how their rating is affected, and what they owe. I already have a working demo of the main layout, so you will not be designing from nothing. I will share it with shortlisted developers. WHO USES IT 1. Clients (Amazon sellers and brand owners). They log in, look at their own data only, add a comment on a review if they want, activate products, download invoices, and contact support. 2. My team (admins). They add and update clients, products, reviews, case status and invoices, and can switch between client accounts. PAGES AND FEATURES (VERSION 1) 1. Login and accounts - Email and password login, with password reset by email. - Two roles: client and admin. - A client can be linked to more than one Amazon seller account/brand (for example, one US account and one Canada account), with a switcher at the top to change which one they view. - A client must never be able to see another client's data. 2. Dashboard (home page) - Summary cards: all products, active products, 1 to 3 star reviews found, reviews flagged, cases filed, reviews removed, and fees to date. - A chart over time showing "removals in progress" against "reviews removed". - A box listing the seller accounts being monitored: brand name, marketplace, Seller ID, and number of active products. 3. Products page - A table of the client's products (ASINs): image, title, brand, category, rank, price, star rating, and the number of 1, 2 and 3 star reviews. - Tabs: Active, Inactive, All, and Potential. "Potential" means products where we found reviews that may break Amazon's rules. - Buttons to activate or deactivate a product, or to activate all potential products at once. - A rating tool: for each product, a small screen that shows how many 1, 2 and 3 star reviews would need to be removed to raise the average rating to a target (for example from 4.2 to 4.4). - Search, sort and export to CSV. 4. Results page (the most important page) - Tabs: Graph, Removed, and Removals in Progress. - A table with: review ID (linking to the review on Amazon), ASIN, review title and text, star rating, review date, client comment, status, date removed, and the fee charged ("Charged" or "Not charged"). - Filters on every column, a search box, pagination, and export to CSV. - Charts: removals by month, by star rating, and by brand. - The client can add or edit a short comment on each review (with a character limit). - A short note on the page explaining that a removed review can sometimes reappear for a while, and what happens in that case (a credit on the account). 5. Payments page - List of invoices: date, description, amount, status, and a button to download the invoice as a PDF. - Our pricing is a fee for each removed review, plus an enrollment fee that is credited to the final invoice and refunded if nothing is removed. The system should be able to create invoice lines for these. - Card on file per seller account is a nice-to-have for a later version (a payment provider such as Stripe). 6. Support page - A simple form (name, email, seller ID, topic, subject, description). - Submissions are saved, and my team gets an email. If you can connect it to a ticket tool such as HubSpot, tell me; it is optional. 7. Admin area - Add and edit clients, seller accounts and products. - Add or update reviews one by one, or import many from a CSV file. - Change a review's status (for example: flagged, case filed, removed, rejected) and set the removal date and fee. - Create invoices. - See a list of all clients with their numbers. DATA - For version 1, my team enters and updates the data in the admin area or through CSV import. Nothing has to be pulled from Amazon automatically. - Later (version 2) I may connect the Amazon Selling Partner API to pull product details and ratings automatically. If you already have SP-API experience, please mention it. It is a plus, not a requirement. TECHNICAL REQUIREMENTS - Your choice of stack, for example React or Next.js with Node.js, or Laravel. Please tell me what you would use and why. - A relational database (PostgreSQL or MySQL). - Responsive design that works well on a phone and on a laptop. - Security basics: hashed passwords, role-based access, every query limited to the logged-in client's own data, HTTPS, and regular backups. - The code must live in a repository that I own, and the database and hosting must be in accounts that I own. You can have access during the project, but nothing should be locked to your accounts. - Deployed to a standard cloud service (for example Vercel, AWS or DigitalOcean) with clear setup notes so another developer can take over. - Clean, commented code and a short written guide on how to run, update and deploy the project. HOW I WOULD LIKE TO WORK - Fixed price, paid in milestones. Milestone 1: login, roles, admin area, and the dashboard home page. Milestone 2: products page and results page. Milestone 3: payments, support page, polish and deployment. - A short update twice a week, and a live link I can test between milestones. - I will pay each milestone after I test it. WHAT I NEED IN YOUR PROPOSAL 1. A link to a dashboard or client portal you built before. A live demo is better than screenshots. 2. The tech stack you would use for this project and why. 3. Your price and time estimate for each milestone. 4. One thing in this brief that you think is missing or unclear. 5. Whether you have worked with Amazon seller tools or the Amazon SP-API. Please start your proposal with the word "PORTAL" so I know you read the full post.