← kelmen.space

LumenBill

Two-sided billing for freelancers and the people who pay them. Money is the object. Every screen has a freelancer side and a client side, and they agree.

What it does

LumenBill handles the paperwork around getting paid: SOWs, invoices, receipts, contract amendments. It treats those documents as the unit of work. Tasks, projects, and contacts exist to produce them.

The thing most freelancer tools miss is that there are two people involved. LumenBill makes the client view first-class — a freelancer marking an invoice paid and a client receiving a paid receipt are the same event seen from two sides.

Why it's shaped this way

• Money-first verbs. The primary actions on every screen are financial: send invoice, mark paid, sign contract, see what's owed. Not "create" or "manage."
• Status is computed. Overdue, paid, signed, draft — all derived from underlying fields. The user never has to keep two status sources synchronized.
• Two sides, one truth. Amber on the freelancer side means amber on the client side. There is no version where one party thinks something is paid and the other doesn't.
• Document-shaped. The artifacts are the things you'd actually mail or print: SOW, invoice, receipt, amendment. Not opaque internal records.

Visit

Live at lumenbill.app. The freelancer side is what you'll see when you sign in; the client side is what your client sees when you send them anything.

Stack

Next.js, Supabase, Drizzle. Deployed on Hetzner with Dokku. Stripe for payments, Resend for email, Plausible for analytics.