CRIT Studio — personal project
One working record for the studio.
A private studio operations app connecting clients, projects, tasks, milestones, and invoices, built to replace a fragmented freelance workspace.
- Year
- 2026
- Role
- Design + implementation
- Client
- CRIT Studio — personal project
- Surfaces
- Studio workspace
- Stack
- Next.js, TypeScript, Drizzle ORM, Postgres, Better Auth, Tailwind CSS
Freelance work spans the brief, client conversations, delivery tasks, milestones, and invoices. I built Freelance OS into CRIT Studio to keep those commitments connected instead of maintaining separate working records for each.
The private app brings client and project records, tasks, finance, and invoices into an authenticated workspace. Project progress follows its tasks, and the commercial model separates collected payments from unpaid milestones so the same commitment is not counted twice.
These screens use the newer CRIT Studio source with a separate local Postgres-compatible sample database. Every pictured client, engagement, task, invoice, and amount is fictional. The screenshots demonstrate the implemented interfaces and relationships, not actual studio revenue or private client records.
Studio workspace
Studio overview
01 / 04
Connect the work
Keep projects attached to clients, tasks attached to projects, and deliverables attached to their commercial commitments.
Make the next action visible
Bring active tasks and project actions into the overview, while separating work waiting on the client from work ready to do.
Keep the money legible
Use invoice line items and milestone relationships to distinguish what has been collected from what remains in the pipeline.
Capture a private tool safely
Run the authentic interfaces against a new isolated sample database. Do not import private client records into portfolio screenshots.
Next
