Nexigo

Problem

The original need came from small businesses that were generating many invoices and needed a faster way to create them while keeping invoice history, customer data and financial information organized. The goal was to make everyday invoicing simple without losing control over permissions, security or reporting.

Key features

Technical approach

I built Nexigo as a full-stack application with React and TypeScript on the frontend, Express and MySQL on the backend, and JWT-based authentication. I implemented the two-factor authentication flow myself rather than relying on an external authentication provider. Sensitive information is protected, and editing or deleting invoices is restricted to the owner or authorized users. The invoice workflow was deliberately kept to four steps so a typical invoice could be created in only a few minutes.

What I’d improve

Nexigo was a major step forward from my earlier projects in both code organization and application structure. If I continued developing it today, I would further separate authentication, permissions and invoice-generation logic into clearer modules, strengthen automated testing and expand the reporting layer before adding more invoice templates or department-level access.