Full-Stack MVP for Insurance SaaS

Замовник: AI | Опубліковано: 11.03.2026

I’m ready to move Catalyst from concept to a working MVP and need an experienced full-stack partner to make it happen. Catalyst will serve insurance brokers as an all-in-one operating system, replacing today’s patchwork of spreadsheets, email quote requests, and individual insurer portals. Scope of this first build The MVP must let a broker log in, create or import a client, request quotes from the major national insurers we’ll support at launch, display side-by-side comparisons, track compliance evidence automatically, and communicate outcomes back to the client—all through a single, responsive web interface that works smoothly on desktop and mobile. Core modules to deliver • Automated quoting: trigger and retrieve quotes via the insurers’ APIs, cache results, and update in real time when product parameters change. • Compliance management: capture every decision point and document trail, timestamp them, and surface actions needed to stay FCA-compliant. • Client communication: in-app messaging and templated email dispatch so the broker can share comparison reports or request missing data without leaving Catalyst. Architecture & tech expectations I’m agnostic on language so long as the stack is mainstream, test-driven, and scalable (a React/TypeScript front end with a Node or Python backend and a PostgreSQL core is one example that would fit). API integrations must follow each insurer’s OAuth or token-based requirements, and the codebase should be containerised for easy deployment to AWS or an equivalent cloud platform. Acceptance criteria 1. A broker can complete an end-to-end quote journey for at least two major national insurers in under five minutes. 2. Every user action is logged in an auditable compliance ledger. 3. The same codebase renders cleanly on a 13'' laptop and a modern smartphone without separate styling effort. 4. Unit and integration tests cover critical flows (quotation, comparison generation, compliance logging, client messaging) at a minimum 80 % threshold. 5. A README explains local setup, environment variables, and build/deploy commands in plain English. If you’re skilled at turning green-field ideas into production-ready SaaS—API wiring, data modelling, UI polish, and release pipelines—let’s discuss timelines and a milestone plan.