CustodyIQ: Solo SaaS Support & Ops

CustodyIQ is a subscription documentation app for parents navigating custody situations. Parents use it to log incidents, track custody exchanges, document medical and school records, and generate organized reports to share with their attorneys.

I built it solo from the ground up and handle all product, ops, billing, and customer support.

During a routine audit, I discovered a critical vulnerability: users could create Supabase accounts without completing Stripe checkout. This meant unauthorized access to the product without a valid subscription.

This wasn't a theoretical risk. It was actively happening.

I rebuilt the entire signup architecture around one principle: no payment, no account.

Restructured the flow so no Supabase account is created until the Stripe webhook confirms successful payment

Eliminated the gap between account creation and payment verification entirely

Built automated tests to ensure the flow couldn't regress

The result: zero unauthorized access from that point forward.

Failed payments are one of the biggest silent revenue killers in subscription SaaS. I built a grace period system based on industry benchmarks from Recurly and ProfitWell:

Days 1–7: Gold warning banner in-app, nudging users to update their payment method

Days 8–14: Account moves to read-only mode (data preserved, but no new entries)

Escalating email sequence via Resend at key intervals

This approach balances revenue recovery with user trust. Users don't lose their data, and most resolve the payment issue within the grace window.

Stripe (billing & subscriptions), Supabase (auth & database), Vercel (hosting), React + JavaScript (frontend), Resend (transactional email), Sentry (error tracking), Anthropic API (AI features), PWABuilder (Android packaging).

This is the kind of work I do as a fractional support & ops partner for SaaS founders: catching billing vulnerabilities before they cost you customers, building systems that handle edge cases gracefully, and keeping the operational side of your product running while you focus on building. I typically dedicate 8–10 hours per month per client, enough to stay embedded without being a full-time hire.