React + Supabase Developer for SaaS

React + Supabase Developer Needed — Wedding Photography SaaS | Pre-Launch Through Long-Term I'm the founder of The Framework (app.getframeworkapp.com) — a SaaS platform built specifically for wedding photographers. Photographers use it to manage clients, send digital intake forms to couples, and build structured wedding day timelines. The app is live with Stripe payments active and a public launch imminent. I'm not looking for someone to fix one thing and disappear. I'm looking for a developer who wants to be part of this from where it is right now — through the launch — and grow with the product long term. This is a relationship, not a gig. The product is mostly built. I need someone to come in, read the codebase carefully, fix what's broken, build what's missing, and then stay on as the go-to engineer as we scale. --- THE TECH STACK • React 18 + Vite + TypeScript + Tailwind CSS • React Router v6 — this is a Vite SPA, NOT Next.js, no SSR • Supabase (Postgres, Row Level Security, Auth, SECURITY DEFINER RPCs) • Stripe (live mode — subscriptions, webhooks, full payment lifecycle) • Resend (transactional email) • Google Maps Places + Routes API • Vercel (hosting + serverless /api functions) Skills: TypeScript — essential, the whole codebase is TypeScript Node.js — for the serverless API functions PostgreSQL — Supabase runs on Postgres RESTful API — for the Vercel API endpoints Database Architecture — covers the Supabase/RLS work SaaS — signals the type of product --- WHAT NEEDS TO BE FIXED (bugs) • Step 6 of the couple intake form is broken • Timeline tab visible to couples before it should be • Intake answers not connected to timeline generation (the core product feature) • No error monitoring (Sentry needs installing) • No staging environment — deploys go directly to production • Stripe webhook signature verification needs confirming • No rate limiting on email endpoint • No email bounce handling • Couple intake progress saves to localStorage instead of database • Subscription timeout behavior undefined WHAT NEEDS TO BE BUILT (new features) • Client portal — post-submit experience where couples can view/edit their info and approve their timeline • Photographer settings page — profile, logo upload, change password, billing self-service via Stripe Customer Portal • PDF export of finalized timelines (react-pdf) • Vendor share link — read-only timeline URL for coordinators, venues, and DJs • Dashboard improvements — resend intake link, sort by wedding date, copy portal link • Email reminders for couples who haven't submitted intake • Intake answers driving the auto-generated timeline draft (the product's core differentiator) Full engineering handoff document provided to serious candidates. Every bug and feature is documented, numbered, and prioritized with complexity estimates. --- WHAT I'M LOOKING FOR ✅ Strong React + TypeScript — comfortable reading and extending a large existing codebase ✅ Supabase — specifically Row Level Security and SECURITY DEFINER RPCs. If you haven't worked with RLS before, this is not the right project ✅ Stripe — subscriptions, webhooks, full lifecycle, and the Stripe Customer Portal ✅ Vercel serverless functions ✅ Someone who reads before they write and communicates clearly with a non-technical founder ✅ Available and responsive during the launch window — hundreds of signups expected from influencer outreach and bugs will need fast turnaround --- THE ENGAGEMENT This is a three-phase relationship: Phase 1 — Pre-Launch Sprint (starting now) Fix critical bugs, install monitoring, build the top-priority features. Estimated 40-60 hours over 3-5 weeks. This is where we establish trust and make sure the product works before photographers start signing up. Phase 2 — Launch Window (on-call support) When influencer outreach begins, I need someone available within 2-3 hours for urgent issues — including evenings and weekends during the first two weeks. This is the most critical period. The right developer understands that and is prepared for it. Phase 3 — Long-Term Retainer (ongoing) 15-20 hours per month. Ongoing bug fixes, new features, and product growth as paying photographers scale up. I want one developer who knows this codebase deeply, not a different contractor every time something needs to change. Rate: open to proposals — I'm looking for the right person, not the cheapest option. --- TO APPLY — answer both questions or your proposal will not be reviewed: 1. Have you worked with Supabase Row Level Security before? Explain in plain English what RLS does and give a specific example of how you've used it. 2. Describe your Stripe experience beyond basic checkout — specifically webhook event handling for subscriptions (grant, update, cancel, failed renewal) and the Stripe Customer Portal. If this sounds like the kind of project you want to be part of, I'd love to connect.