Hi, I have a project to accomplish. This project is long term base. You need to provide work weekly.Price vary base on the workload you can accomplish and your skill. it's a big project that required a NDA sign with my company. I will show you the project in HTML, that need to be redone in next.js. You need to be able to give some advice and be knowledgable on every aspect including security. Here what we need so far. Objective will be given each week base on your previous result. 1) Use Next.js the “right way” for MGA needs Next.js App Router (server components + server actions) for secure data operations. SSR for authenticated areas (portal, submissions, policy admin) so data loads fast and stays private. Static/ISR for marketing pages (homepage, product pages) for maximum speed and SEO. 2) Core modules you’ll likely need (MGA) Broker Portal Broker onboarding + KYB/KYC checklist Submissions list, status, notes, attachments Quotes, bind requests, policy downloads Underwriter / Admin Portal Product configuration (forms, rules, pricing parameters) Submission triage (assign underwriter, tasks, SLA timers) Quote generation, bind, endorsement workflow Payments Pay premium (card/ACH if applicable), receipts, refund handling Finance reconciliation exports Client Area (insured) View documents, invoices, payment status, renewals Messaging / Email automation Templates, triggers, audit logs (“who sent what, when”) 3) Data model + workflow approach (speed + flexibility) Store “products” as config-driven forms (JSON schema style): Fields, validations, conditional logic, required docs Versioning (forms change over time; you must keep history) Submission pipeline: Draft → Submitted → In Review → Quoted → Bound → Issued → Renewing Every action should create an audit event (compliance + traceability). 4) AWS stack that fits Next.js + heavy data A clean, modern setup: Frontend: Next.js on Vercel or AWS Amplify Hosting API layer: If you want speed of development: Next.js server actions + route handlers If you want enterprise separation: API Gateway + Lambda (or ECS) Database: PostgreSQL (RDS or Aurora) for MGA workflows (relational, reporting, constraints) Files: S3 for uploads (quotes, loss runs, PDFs), with pre-signed URLs Auth: Cognito (roles: Broker, Underwriter, Admin, Accounting) Email: SES (templates + deliverability) + event tracking Search / filtering (optional but powerful): OpenSearch if you need fast global search across submissions/policies Observability: CloudWatch + structured logs, plus error tracking (Sentry is great) 5) Security + compliance (important for MGA) Role-based access control (RBAC) + row-level permissions: Brokers see only their book Underwriters see assigned queues Encryption: S3 + RDS encryption at rest, TLS in transit Audit trail everywhere PIPEDA / Law 25 friendly practices Consent, retention policy, access logs, data export/delete processes (when applicable) 6) Performance rules (so it feels “instant”) Use server-side pagination + filters (never load thousands of rows). Add caching where safe (e.g., product catalogs, static reference data). For tables: use virtualization (front-end) if needed. 7) Payments integration considerations If you’re doing premium financing or broker-fee models: Separate “invoice” vs “premium” vs “fees” line items Store payment intent + webhooks + reconciliation status Never trust front-end “paid” state—webhook confirms truth 8) Dev workflow & testing TypeScript everywhere, shared types between UI/API. Automated tests for: form rules pricing logic permission checks CI/CD: staging + production environments, feature flags for new products. Let's talk about all the details if you are interested. Come to the chat. Alain