From the first proposal to the last payment.
Visit the productThe context
Freelancers and small businesses need more than a PDF generator. They need to know what has been agreed, what has been billed, what has been paid, and what still needs their attention.
InvoiceBirds brings client documents, payments, collections, expenses, and reporting into one workspace. The current interface follows that connected workflow, carrying the client and document context from the proposal through to financial review.
My full-stack work covered document creation, invoice lifecycle, client and expense workflows, payment integration, and the reusable interface patterns behind them.
Inside InvoiceBirds
The key workflows, up close.
Current product screens captured in September 2026. The engagement period above describes my contract; the screens show the product as it exists today. Workspace figures illustrate the interface, not business results attributed to my work.
The proposals workspace separates drafts, sent proposals, accepted work, and converted documents. Pipeline value and conversion readiness sit above the list, so the owner can tell what is still being discussed and what can move forward.
Accepted proposals expose a route into contracts. The product keeps progress visible without asking the user to reconstruct it from separate files.
The editor puts a live document between a structured content outline and its design controls. Business identity, client details, invoice dates, line items, taxes, payment methods, notes, terms, and signatures each have a defined place.
A readiness checklist makes missing information explicit. Templates, colors, corners, fonts, and table styles can be adjusted while preview, PDF, and sending actions remain close to the document.
Outstanding, overdue, collected, and billed totals provide context before the user reaches the records. Status tabs, folders, search, sorting, and table or card views support different ways of finding the right invoice.
Each record retains its client, folder, status, amount, and due date. Preview, editing, and PDF access sit beside the record instead of becoming separate navigation journeys.
Collections turns unpaid invoices into a prioritized follow-up view. Days overdue, amount due, urgency, and last contact help the owner understand which conversation needs attention next.
Reminder configuration and collection health sit alongside the queue. Follow-up and preview actions keep the evidence close to the decision, while upcoming cash and recent reminder activity provide context.
Expense profiles group spending by team, department, person, or project. A summary of total spending, transactions, and categories gives the owner a starting point before opening a specific profile.
The profile list connects individual records to the wider business picture. This gives expense review a consistent structure alongside the document and payment workspaces.
The tax workspace separates revenue, tax collected, estimated tax owed, and net after tax. Monthly reports carry their own filing status, with a chart and breakdown to help users understand the period they are reviewing.
Settings expose the selected region, filing cadence, and accounting basis. Estimated amounts are labeled as estimates; the interface does not turn a projection into a claim that a filing has happened.
The received-invoices workspace adds the supplier side of the workflow. Supplier, invoice number, issue and received dates, format, and amount remain searchable as structured records.
The current product exposes import controls for supported electronic invoice formats. This complements outgoing billing without forcing supplier documents into an ordinary PDF-only archive.
Behind the interface
Draft, sent, paid, and overdue states determine the useful next action. Shared controls keep that model consistent across lists and the editor.
Stripe integration, manual payment context, and invoice state need to converge on a durable record. A visual success state cannot replace payment confirmation.
Next.js interfaces, NestJS application logic, and Supabase records connect customers, documents, line items, expenses, and reporting context.
My work on InvoiceBirds
Enterprise Fleet Analytics
Have a product
that needs this kind of care?