← Back to Case Studies
Delivery & Build

FreelancerPilot

I designed and built FreelancerPilot, an operations SaaS that consolidates client management, time tracking, and invoicing into one system for freelancers.

Project Type
SaaS Platform
Target User
Freelancers
Role
Architect & Lead Developer
Delivery Mode
Solo end-to-end
View GitHub Repository
Background

Context

FreelancerPilot was built at the request of a company working closely with freelancers. They observed a recurring pattern: most freelancers struggled to manage clients, projects, tasks, time tracking, and invoicing across fragmented tools or spreadsheets.

The goal was to create a single operational system that gives freelancers clarity over their work and finances, while remaining simple enough for daily use. The platform was designed as a SaaS product with potential for additional revenue streams.

What wasn't working

Problem

Client, project, and task data scattered across disconnected tools

Weak connection between work performed and invoices sent

Manual or error-prone invoicing and payment tracking

Limited visibility into deadlines, workload, and income

No shared space for collaboration with clients

These problems create friction and mental overhead, pulling freelancers away from their actual work.

How I led delivery

Approach

I designed the system around operational workflows, not features. I focused first on the relationships between core entities—clients, projects, tasks, time entries, and invoices—so everything connected naturally.

Complexity was centralized in the data model and workflows, while the user experience was kept straightforward. Non-essential features were deliberately deferred to protect clarity and delivery speed.

Key decisions

  • Design around entity relationships first—clients → projects → tasks → time → invoices
  • Centralize complexity in the data model—keep the UI simple
  • Build multi-workspace support from the start—architecture matters early
  • Defer non-essential features—ship usable before perfect
  • Design for extensibility—future features shouldn't require rewrites
What I built

Solution

What I built

FreelancerPilot is a central operations SaaS for freelancers that replaces multiple disconnected tools. It consolidates client management, time tracking, and invoicing into one coherent system.

Client & project management
Task tracking with status workflows
Integrated time tracking tied to billing
Automated invoice generation
Payment status tracking
Workload & income dashboards
Multi-workspace support
Optional client collaboration space

How it's used day-to-day

Freelancers

Manage all clients, projects, and tasks in one place—track time, generate invoices, monitor deadlines and income.

Clients

Optional shared workspace for viewing project progress, tasks, and communication—transparency without tool fragmentation.

Business Operators

Multi-workspace architecture supports agencies or freelancers managing multiple business entities under one account.

Visual proof

Platform in production

FreelancerPilot projects view
FreelancerPilot dashboard
FreelancerPilot task management
Technology

Tech Stack

Frontend

  • Next.js 16 (App Router)
  • TypeScript
  • TailwindCSS
  • shadcn/ui
  • Recharts

Backend

  • Next.js API Routes
  • PostgreSQL
  • Prisma ORM
  • NextAuth v5

Infrastructure

  • Stripe (payments)
  • Resend (email)
  • React Hook Form + Zod
The shift

Before vs After

Before

  • Data scattered across tools
  • Manual invoicing process
  • No time-to-billing connection
  • Limited financial visibility
  • No client collaboration space
  • Mental overhead managing tools

After

  • Single source of truth
  • Automated invoice generation
  • Direct time-to-invoice tracking
  • Real-time financial dashboards
  • Optional client workspace
  • Reduced operational friction
Why this matters

What this proves

You get coherent systems designed around workflows, not feature lists

You get someone who can ship production-ready SaaS platforms end-to-end as a solo operator

You get architecture that supports future extensions without rewrites

You get balanced scope management—ship usable systems without overbuilding

If you need custom internal tools, operational platforms, or someone who can design and deliver coherent systems end-to-end—I can help.

Discuss Your Project