Senior Full-Stack Developer for AI-Powered MVP

Senior Full-Stack Developer Needed — Migrate & Finish Existing AI Website Builder (NOT a Rebuild) I am looking for an experienced senior full-stack developer to take over, migrate, finish, and launch an existing AI website-builder SaaS. Important: This is NOT a build-from-scratch project. CorvixAI already has a substantially developed working product originally built with Lovable. I am looking for someone who can evaluate the existing code, preserve as much working functionality as technically reasonable, complete the remaining production work, and get the platform launched on infrastructure I control. I specifically do not want someone to automatically redesign the architecture or rebuild working features simply because they prefer another stack. Existing Product The existing application already includes substantial work around: - AI business interview flow - AI website generation - Multi-page website generation - Home, About, Services, Contact, FAQ, Privacy and Terms pages - Individual section regeneration - Template-based site sections - Business modules including booking, quotes, ordering, catalog, reviews and chat - Website preview/builder interface - English and Spanish UI - User/project database structure - Credits and plan logic - Billing/admin UI structure - Published-site renderer - Booking integration structure - Custom-domain proof-of-concept - Cloudflare Worker/domain-routing work The existing Lovable codebase and repositories will be available for review. Current Infrastructure / Technologies The project currently involves or is being migrated toward: - React / TypeScript - Next.js - NestJS - PostgreSQL / Supabase - Prisma - Clerk authentication - Anthropic Claude API - Stripe - Vercel - Cloudflare / Cloudflare Workers - GitHub I am open to architectural recommendations, but any significant rewrite must have a clear technical reason and must be approved before implementation. Maximum reuse of existing working code is the goal. What I Need The objective is to take the existing CorvixAI application and get it independently hosted, stable, secure, and ready for real customers. Primary work includes: Existing-Code Audit Review the current Lovable application and migration repositories. Identify: - What works today - What can be reused directly - What needs minor modification - What genuinely must be rewritten - What is incomplete - What is unnecessary for launch I want this assessment before committing to a large development estimate. AI Website Builder Preserve and complete the existing: - AI interview - Site-generation pipeline - Section regeneration - Multi-page generation - Template/module system - English/Spanish support Connect the production system properly to Anthropic Claude with usage/cost tracking and appropriate failure handling. User Accounts Complete production authentication/account handling using Clerk. Users must only be able to access their own projects and data. Projects & Builder Users should be able to: - Create projects - Complete the AI interview - Generate a website - Preview all generated pages - Regenerate individual sections - Configure relevant business features - Publish the website The existing builder UX should be reused wherever practical rather than redesigned unnecessarily. Publishing Users need one-click publishing. Published sites should initially support a CorvixAI subdomain. Existing custom-domain/Cloudflare work should be reviewed and reused where possible rather than automatically rebuilt. Stripe Billing Complete production billing including: - Subscriptions - Plan upgrades/downgrades - Stripe Checkout - Customer Portal - Webhooks - Credit purchases - Renewal handling - Failed-payment handling - Monthly credit allocation Credits & AI Cost Protection Complete server-side credit enforcement. Requirements include: - Atomic credit deductions - Transaction history - Refund credits when AI generation fails - Usage limits - Rate limiting - AI token/cost tracking Admin Admin functionality should include: - User list - Plan - Credit balance - Subscription status - Project count - Credit adjustments - Plan override - Suspend/reinstate user - AI usage/cost visibility Production Launch Complete the remaining work required for a safe launch, including: - Deployment - Environment configuration - Error handling - AI timeout handling - Security review - Basic monitoring - Stripe production testing - Authentication testing - Publishing testing What I Do NOT Want I am not looking for someone to take screenshots of the existing product and recreate it from scratch. I am also not looking for someone to automatically replace working code because they prefer another framework. If something needs to be rewritten because of a genuine architectural incompatibility, explain: 1. What currently exists 2. Why it cannot reasonably be reused 3. What needs to replace it 4. Estimated hours 5. Benefit of the change First Milestone — Paid Technical Audit Before awarding a large block of development hours, I want a senior developer to review the existing repositories. The first deliverable should be a concise migration/completion report showing: Existing feature → current condition → reuse/port/rewrite → reason → estimated remaining hours I will use that report to approve the remaining milestones. Do not quote this as though you are building an AI website-builder SaaS from a blank repository. When Applying Please include: - Examples of SaaS products you personally built or migrated - Experience taking over AI-generated/Lovable codebases - Next.js experience - NestJS/backend API experience - PostgreSQL/Prisma experience - Clerk experience - Stripe subscription/webhook experience - Anthropic API experience - Vercel experience - Cloudflare Workers/custom-domain experience Most importantly, answer this question: If an existing SaaS already has working product logic, UI components, AI prompts, database design and publishing functionality, how do you determine what should be reused versus rewritten during migration? I value developers who can simplify systems and preserve good existing work—not developers who create unnecessary hours by rebuilding everything. This can become an ongoing development relationship after launch for the right person.