Invoicer: A Focused Invoice Tool Concept Project

Invoicer is a concept project, not a commercial product. We built it as an internal experiment to create a focused invoicing tool for freelancers and small agencies. Our goal was to design and prototype the user interface and features before doing a full product build. In the end, we didn’t launch Invoicer as a product – it was purely a design exploration.

The Problem

Most invoicing tools (FreshBooks, QuickBooks, Wave, Zoho Invoice, etc.) have grown into full accounting platforms because that’s where the money is. In those apps, invoicing is just one feature among dozens. For a freelancer who just needs to send a clean invoice in a couple of minutes, these big platforms can feel like overkill and can be slow to use.

We imagined what a one-purpose invoicing tool would look like: zero-configuration signup, lightning-fast invoice creation, clean PDF invoices, basic payment tracking – and nothing extra. We thought that some users would prefer a tool that does one thing really well, rather than a platform that does ten things so-so.

Key design highlights:

Simple home screen: After you sign in, you land immediately on an invoice editor. There’s no dashboard, analytics page, or setup wizard. We even pre-select your last-used client. The idea was to let users start creating an invoice right away, instead of spending time on a long setup.

One-click, polished PDFs: We wanted the invoice PDF to look professional. Most invoicing tools spit out PDFs that look plain or outdated. In Invoicer, the PDF is a design showcase: a clean serif company name at the top, neatly tabulated line items and totals, plenty of white space, and an optional accent color. We made sure each PDF looked print-quality without any effort from the user.

Payment-focused only: Invoicer is all about invoicing and payment tracking – not full accounting. An invoice can only be in one of three states (draft, sent, or paid) and that’s it. Marking an invoice as paid is just one tap. We did support things like recurring invoices and basic tax handling (sales tax, VAT, GST), but Invoicer was never intended to be a complete billing or tax-filing system.

Narrow scope: We kept Invoicer strictly focused on invoicing. It doesn’t do bookkeeping, expense tracking, payroll, time tracking, project management, client portals, or anything beyond invoicing. Keeping the scope this narrow was a deliberate design choice to stay simple and fast.

What we built:

• A full UI design system covering the invoice editor, client management screens, payment tracking, settings, and account flows.
• HTML/CSS prototypes of the invoice editor and the PDF templates, to see how they would look and feel.
• React components for key interactive parts (for example, the line-item editor, currency selector, and tax calculations).
• Three different PDF template designs (minimal, classic, and modern) to explore different styles.

Why we didn’t ship it:

The invoicing market is already very crowded. It would have been hard to make money from a stripped-down tool at a low price, especially when companies like Stripe and PayPal offer invoicing, and the big accounting platforms often have free tiers. The design exploration taught us a lot, but the product-market-fit math just wasn’t there. We decided to keep the design system as a reference for other focused-tool projects instead of continuing to build Invoicer.

Interested in a similar design exploration?

EtherLabz runs concept design projects to test out UX ideas before committing to a full build. Book a discovery call to see whether your idea is ready for a design-exploration phase or ready to be built out.

Concept project by Sanya, Mradul, and the EtherLabz team. Invoicer is an unshipped concept – not a commercial product.