Building FoxyInvoice — Chapter 0: We built an invoicing SaaS, and you can too

This series documents the creation of FoxyInvoice, a real multi-tenant invoicing SaaS that operates live at foxyinvoice.com. The app sends real invoices, processes payments via Stripe, calculates US sales tax, and serves real users. Its enterprise counterpart, invoices.seolith.com, handles the financial books of an actual business.

The guide covers the end-to-end stack and reasoning behind each component. Angular powers the application, .NET handles the API, Postgres stores the data, a worker processes tasks asynchronously, and Docker ensures reproducibility. All of these pieces are chosen for their reliability in production environments.

The series emphasizes multi-tenant data security, ensuring that thousands of businesses can share a single database without any invoice data mixing, all while maintaining security through query layer restrictions and validated through testing. Deployment is automated, with a push to the main branch triggering a live deployment within eight minutes, complete with health checks, secret scanning, and automatic rollback mechanisms.

There is no staging server or dedicated DevOps team; the entire process is managed by a single individual.

The economic model is transparent, detailing the monthly cost breakdown, Stripe fees, the low cost of a free-tier user, and the break-even point for the business. The operating rhythm is also outlined, highlighting a 20-minute daily routine that involves identifying user issues, gathering feedback, turning bug reports into fixes, deploying updates, and communicating with users.

Modern web reach strategies are explored, including how AI crawlers (such as GPTBot, ClaudeBot, and PerplexityBot) cannot see client-side rendered pages, yet the machine-friendly design of the app becomes a growth strategy rather than a hindrance.

The target audience includes anyone with basic coding skills who wants to ship a product. The series teaches all necessary terms as they appear, always linking them to specific incidents within the app. Prior knowledge is encouraged to be skipped; the underlying rationale behind each concept is usually still valuable due to real-world incident-driven insights.

FoxyInvoice does not require a team, investors, a staging environment, or a budget beyond a minimal VPS and a domain. The series operates under three core principles: every claim should be verifiable, numbers and behaviors must come from the production system and its git history, and mistakes are included to provide realistic learning opportunities.

The series avoids glorifying massive user growth and instead focuses on the technical workings and cost implications of building a functioning SaaS, a perspective often overlooked.