All work

Axiom

Freelancer management SaaS platform.

Status
Live · maintained
My role
  • Product workflows and interface
  • Shared operational data model
  • API and deployment
Stack
Next.js, Prisma, Supabase, React
Axiom product landing page

The problem

Freelancers struggle with proposal generation, invoicing, and client document management across multiple tools.

Freelancer operations usually live across disconnected tools, which makes handoffs between proposals, projects, and billing unnecessarily messy.

The approach

Built a system-first platform with reliable data flow between proposals, projects, and invoices.

Designed structured workflows for proposals, projects, and invoicing with scalable APIs.

Defining decision

Model proposals, projects, and invoices as connected stages of one workflow instead of isolated product features.
The tradeoff

A shared operational model requires stricter state transitions, but removes duplicate data and makes handoffs predictable.

How it works

Step through the system. Each stage lists the safeguard that keeps it trustworthy.

Lead

Client context begins as a structured opportunity rather than an isolated document.

Safeguard

Avoids duplicating client data across disconnected tools.

1 of 4

Architecture notes

  • Proposal, project, and invoice flows share one structured data model.
  • APIs were designed around predictable handoffs between core operational states.
  • The product favors repeatable workflow clarity over one-off feature sprawl.

Operations proof

Built and working

  • Proposal-to-project handoff flow
  • Operational visibility across delivery stages
  • Billing and invoicing tied to project execution

Engineering signals

  • Deployed on Vercel
  • Supabase PostgreSQL
  • Scalable API workflows

What’s next

Tighten the project-to-invoice workflow and add clearer operational reporting for active client work.