Full-Stack Developer to Build MVP for FinTech/EdTech SaaS Platform (Next.js + Supabase + Stripe)

About the project Our project is a financial education and decision-support platform built for sales teams — a free calculator tool paired with a membership content platform. I have a working prototype (a self-contained HTML/JS tool covering 11 financial calculators) and need it rebuilt into a real, production web application with accounts, a database, and payments. What already exists (I’ll share this with you) • A fully-functional prototype of the core tool — 11 working calculators (vehicle buy/lease/finance decisions, tax strategy, real estate analysis, and more), currently built as a standalone HTML file with in-browser storage. • A full copy deck / content plan and brand style guide (colors, fonts, layout direction) so the visual direction is already defined — this is not a design-from-scratch project. What I need built 1. Real user accounts — sign-up/login (email + password or magic link), replacing the prototype’s local-only storage. 2. A production database — store each user’s saved calculator inputs/outputs so they persist across sessions and devices. 3. Free vs. paid membership gating — some tools/content free, some behind a paid subscription. 4. Stripe subscription billing — monthly membership tier, including a working checkout flow, billing portal for users to manage/cancel, and webhook handling so access updates automatically on payment status changes. 5. Port the existing 11 calculators into the new app, preserving their logic exactly (I’ll provide the current file as the source of truth). 6. A simple CMS-backed blog/content section — I need to be able to publish written articles myself without touching code (Sanity, Notion-as-CMS, or a similarly simple headless CMS is fine — your recommendation is welcome). 7. Video/recording hosting for member content — rep interviews, tutorials, and recorded content need their own home. This is a separate problem from the blog CMS above (please don’t quote it as if a text CMS solves it) — I need members to stream video content, gated to paid subscribers only, without me paying a fortune in bandwidth as it grows. Please recommend and set up whichever of these fits best for a bootstrapped budget: Mux, Cloudflare Stream, or a gated/unlisted Vimeo Pro or Business plan integrated with the membership gating in #3. Include your reasoning on which you’d pick and why. 8. Basic admin visibility — a simple way for me to see signups and active subscribers (a Supabase dashboard view or lightweight admin page is enough, doesn’t need to be fancy). Preferred stack (open to your recommendation if you have a better-supported alternative for a non-technical founder to maintain) • Frontend: Next.js (React) • Backend/Database/Auth: Supabase • Payments: Stripe • Hosting: Vercel • CMS: Sanity or Notion-as-CMS • Video/media hosting: Mux, Cloudflare Stream, or gated Vimeo Pro/Business (your recommendation welcome) Important context • I am not technical. I need clean documentation, a Loom walkthrough of how everything works, and a codebase a future developer could pick up without you. Please account for this in your process and communication style. • This is a fixed-scope MVP, not an open-ended engagement — I’m looking for a complete, working, deployed product at the end of this contract, not just code delivered to a repo. • I’m happy to have a short follow-on contract for bug fixes/small iterations after launch, separate from this scope. Budget & Timeline • Budget: (open to discussing based on your proposal and experience — please tell me what you’d propose and why; video hosting setup adds real scope over a text-only build, so factor that in) • Timeline: 4–7 weeks from kickoff to a deployed, working MVP To apply, please include: 1. A link to 2–3 SaaS products you’ve built that include user accounts + Stripe subscriptions (live links preferred over screenshots) 2. Your recommended stack if different from above, and why 3. How you’d structure milestones/payments for a project like this 4. Confirmation you can hand off documentation to a non-technical founder (and a future developer) can actually use