Fusso

Fusso is a job application tracker I built and run as a live, monetized SaaS product. It solves the problem I kept running into across my own hiring loops: scattered notes, email threads, and spreadsheet rows that never gave me a clear picture of where each application stood. So I built a tool that treats job hunting like a real workflow — with a structured pipeline for every application, interview, and follow-up. The product is in soft-launch today, but the architecture is designed to grow with a proper user base.

On the monetization side, I integrated Lemon Squeezy for payments — subscription billing with a clean checkout flow and automatic receipt handling. That decision kept the commerce layer lightweight: Lemon Squeezy handles the tax, invoicing, and merchant-of-record concerns so I can focus on the product rather than payment plumbing. The billing lifecycle is wired into the app so a new subscriber gets immediate access, and I have the hooks in place to add more tiers as the product matures.

The stack is intentionally modern and productive. Next.js and TypeScript give me a typed full-stack foundation, Supabase provides the Postgres database and auth, and Tailwind handles the styling so the UI stays consistent without fighting a design system. I use Resend for transactional email — interview reminders and application follow-ups — and PostHog for product analytics to understand how users actually move through the pipeline. Sentry catches runtime errors in production so issues surface before they become user-facing problems. Each piece plays a specific role, and the whole thing deploys to Vercel with preview deployments for every branch.

Building Fusso has been a different kind of engineering challenge than my game work — shipping a hosted service with real auth, real billing, and real user data instead of a client binary. It’s the same structured mindset: define the pipeline, keep the architecture clean, and instrument everything so I know what’s working. As a live, monetized product it’s also my most direct test of end-to-end ownership — from the database schema up through the checkout page and into the analytics that tell me whether it’s actually useful.