A month ago I wrote about InvoicePedia, my full-stack invoice project, and ended that post with a list of things I wanted to do next. Some of it is done now.
What I Said I Would Do
- Improve the UI and layout
- Add PDF download and export
- Enable recurring invoices
- Build a proper dashboard and analytics
- Fix deployment and ship a live demo
What Actually Shipped
The UI. The whole app got reworked with Tailwind and shadcn/ui. It is clean, responsive, and no longer looks like a form I built in an afternoon.
The deployment. This was the one blocking everything in the last post. The Next.js 15 dynamic route type errors are sorted and it is live on Vercel: invoicepedia-lac.vercel.app
PDF export is in. Recurring invoices and the analytics dashboard are not.
What the App Does
InvoicePedia is an invoice management tool for individuals and small teams:
- Create, view, and manage invoices
- Take payments through Stripe
- Work as a personal account or inside an organization
- Auth through Clerk
Tech Stack
| Tech | Purpose |
|---|---|
| Next.js 15 | App Router, full-stack React |
| Tailwind CSS | Styling |
| shadcn/ui | Components |
| Drizzle ORM | Type-safe SQL and schema management |
| PostgreSQL | Database |
| Xata | Serverless data platform |
| Stripe | Payments |
| Clerk | Auth and organizations |
| Vercel | Deployment |
Still on the List
- Recurring invoices
- A real dashboard with analytics
- Multi-language support, eventually, maybe
Where That Leaves Me
Taking a list I wrote a month ago and being able to strike most of it out is a better feeling than I expected. Half of that list is still open, which is fine. The app works and it is online, which it was not last time.
Go try it and tell me what breaks.