ClaimFlow has two sides: a portal where contractors submit warranty claims, and a staff portal where each claim is worked through to reimbursement. The hard parts were money and deadlines. Claim windows differ by provider, so the server enforces the status workflow and calculates deadlines itself. Fees and payouts run through Stripe, with every movement recorded in an auditable ledger.
What I built
- Designed and built a B2B SaaS MVP with a contractor portal for submitting claims and a staff portal for managing each claim through to reimbursement.
- Built the app with Next.js 16 App Router, TypeScript, Prisma ORM, PostgreSQL, shadcn/ui, and Tailwind CSS, with shared Zod schemas so client and server validation stay consistent.
- Implemented a server-enforced claim status workflow that calculates deadlines from provider-specific claim windows and shows urgency indicators, so staff work the most time-sensitive claims first.
- Integrated Stripe Payment Intents for submission fees and Stripe Connect transfers for contractor payouts, with webhook handling, an auditable billing ledger, and cent-safe fee calculations.
- Secured PII-heavy claim documents in a private Vercel Blob store, streaming files through an authorized API route instead of exposing signed URLs.
- Implemented JWT auth with NextAuth, route guards, centralized permission checks, Cloudflare Turnstile, and admin-controlled onboarding.
- Automated contractor notifications at each stage of the claim lifecycle with Resend and react-email templates.
- Set up GitHub Actions CI for lint, format, unit tests, and production builds, with focused coverage on money-critical paths like fee calculations and status transitions.