GigFlow

The problem

Freelance and internship-style client work comes with its own quiet admin overhead: which client asked for what, what's actually been invoiced, what's overdue, what the deadline actually is versus what it feels like from memory. Right now that lives across chat threads and memory, which works until it doesn't.

The plan

A straightforward client/project manager: clients, projects, invoices, deadlines, and status, in one place instead of scattered across DMs. Nothing exotic — the value is in it actually getting used, not in the feature list.

Why NestJS + Next.js

NestJS's modular, opinionated structure — modules, providers, dependency injection built in — fits exactly this shape of problem: a handful of related resources (clients, projects, invoices) with real business rules connecting them, which benefits from enforced structure rather than a pile of loose routes. Next.js on the frontend for the same reason most of these projects lean on it: fast to build a clean, usable admin-style UI.

Status

Planned. This one is explicitly downstream of having enough freelance and internship-style client work to justify building it — not a hypothetical use case.