Existing invoicing solutions have always been less than ideal, some because of their unintuitive UI, most because of database-like invoice management. Most existing invoicing solutions offer a workflow that resembles that of maintaining a database.

In my experience, however, being able to see, say, all the estimates of all clients on one page is much less useful than seeing all the invoices, estimates, and expenses under one client or project.

The dashboard groups various data types under their respective projects, with indications for overdue and not yet sent invoices. This way, the user will not only have a better understanding of the structure of his projects and invoices, but also be able to see what needs attention immediately after logging in.

One of the most distinct features is the ability to automatically create invoices for milestone-based billing: as soon as one invoice is sent, the next is created as a draft. This is similar to recurring invoices, but is based on completion (sent invoice) rather than time.

 

 

The interface is designed around clarity and simplicity. Whenever possible, users are presented with a single action option, and unnecessary elements such as edit buttons are avoided by inline editing.

 

As I iterated on the structure and interface of the app, I built quick prototypes from paper and conducted informal think-aloud usability studies.