Building Fusso: A Job Application Tracker You'll Actually Keep Using

Fusso is a job application tracker I built and run as a live, monetized SaaS product. It solves a 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.

What makes it different

Most trackers are just lists. The thing that makes Fusso stick is the pipeline: every application moves through defined stages, so you always know the next action. That structured approach is the same mindset that makes game systems and frameworks maintainable — define the flow, keep it clean, and instrument everything so you know what’s working.

The stack, deliberately chosen

The stack is intentionally modern and productive. Next.js and TypeScript give 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. Each piece plays a specific role:

• Lemon Squeezy for payments — subscription billing with a clean checkout flow and automatic receipt handling. It handles the tax, invoicing, and merchant-of-record concerns so I can focus on the product rather than payment plumbing.
• Resend for transactional email — interview reminders and application follow-ups.
• PostHog for product analytics — to understand how users actually move through the pipeline.
• Sentry to catch runtime errors in production before they become user-facing problems.
• Vercel for deployment, with preview deployments for every branch.

The engineering takeaway

Building Fusso is a different kind of engineering challenge than 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. As a live, monetized product, it’s also the 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.