Billr Case Study: Building a Cross-Platform Invoicing SaaS MVP
Quick answer: Billr is an invoicing and billing SaaS for solo contractors, currently in active development at NeuroStackOS. It runs on React Native with Expo SDK 51 for mobile, Next.js for web, and Cloudflare Workers using the Hono framework for the backend, with Cloudflare D1, R2, and KV for data and storage. It is documented here transparently as a live, in-progress build, not a finished product with customers yet, because that is what it actually is right now, and because the build process itself is the point of this case study.
What Billr Is Solving
Solo contractors and freelancers are underserved by most invoicing software, which tends to be built for small teams with a bookkeeper, not for a single person who needs to send an invoice, get paid, and understand their financial position without hiring anyone to manage it. Billr is being built as a "pocket CFO," a lightweight but genuinely useful financial companion for one-person businesses, rather than a stripped-down version of enterprise accounting software.
Why This Case Study Is Different From the Others
Most of the case studies in this portfolio describe something already shipped and measured. This one does not, and pretending otherwise would be dishonest in a way that eventually costs more than it gains. Billr's UI is running on localhost. There is no live production URL yet. What this case study documents instead is the architecture, the design system, and the technical decision-making behind an active SaaS MVP build, which is directly useful to anyone evaluating whether NeuroStackOS can execute the SaaS MVP Build service tier, because you are looking at the actual process, mid-flight, not a polished retrospective.
Achieve Similar Results
Don't leave your engineering outcomes to chance. Book a technical strategy call with our lead architects today.
Book a Technical Strategy Call →What Is Being Built
| Layer | Technology | Why It Was Chosen |
|---|---|---|
| Mobile app | React Native with Expo SDK 51 | Single codebase for iOS and Android, with Expo's managed workflow reducing native build complexity for a solo-founder timeline |
| Web app | Next.js | Gives Billr a browser-based option alongside mobile, important for a tool people may want to use from a laptop while invoicing |
| Backend API | Cloudflare Workers with Hono | Edge-deployed, low-latency API layer without the overhead of managing traditional server infrastructure |
| Database | Cloudflare D1 | SQLite-compatible edge database, keeping data close to the Workers runtime that queries it |
| File and object storage | Cloudflare R2 | Stores generated invoice PDFs and related files without egress fees |
| Key-value store | Cloudflare KV | Handles fast-access configuration and session-adjacent data |
| PDF generation | Satori with resvg | Generates invoice PDFs from structured layout data without needing a headless browser instance, which keeps PDF generation fast and cheap at the edge |
| Brevo | Handles transactional email for invoice delivery and notifications | |
| Authentication | Firebase Auth with FCM | Handles user authentication and push notification delivery for mobile |
The Design System: Kinetic Precision
Billr's visual identity is built around a design system called Kinetic Precision, anchored on an emerald primary color (#059669) and Geist typography. The name is intentional: "kinetic" for the sense of momentum a solo contractor needs to feel when getting paid faster, and "precision" for the financial clarity the product is meant to deliver. A named, documented design system, rather than ad hoc styling decisions made screen by screen, is what keeps a product's interface consistent as new screens get added during an active build, which matters more in a fast-moving MVP than in a slower, fully-speced enterprise project.
Why Cloudflare Workers Instead of a Traditional Backend
The decision to build Billr's backend on Cloudflare Workers with the Hono framework, rather than a traditional Node.js server, was made for a specific reason: Billr's core use case, a contractor generating and checking on an invoice, is latency-sensitive in a way that benefits directly from edge deployment. A Worker responding from a location physically close to the user is faster than a centralized server, with no infrastructure to provision or scale manually. Combined with D1, R2, and KV, the entire backend runs on Cloudflare's platform without a separate hosting bill or server maintenance burden, which is a meaningful cost and complexity advantage for a product still finding its initial user base.
PDF Generation Without a Headless Browser
Most invoicing tools generate PDFs using a headless browser like Puppeteer, rendering an HTML template and printing it to PDF. That approach works, but it is heavy: a full browser instance per PDF generation request is slow and resource-intensive, which is a poor fit for an edge-deployed Workers backend that is not designed to run a browser process at all. Billr instead uses Satori, which converts structured layout data directly into an SVG, combined with resvg to rasterize that SVG into a PDF. This produces invoice PDFs fast, without a browser dependency, and fits naturally into the Workers runtime's constraints instead of fighting them.
Current Status and What Comes Next
Being direct about where things stand: Billr's UI is functional and running locally, the backend architecture on Cloudflare Workers is built, and the Kinetic Precision design system is defined and applied. What is not yet true is a live production URL, a public user base, or revenue figures, and this case study will not claim any of those until they are real. This is presented as a live-build case study on purpose, updated as Billr moves toward launch, rather than held back until it is finished.
Why This Is the Case Study That Matters Most for SaaS MVP Clients
If you are evaluating NeuroStackOS specifically for the SaaS MVP Build service, at $1,500 to $4,000 depending on scope, Billr is the most directly relevant proof available, precisely because it is happening in real time using the exact process a client engagement would follow: architecture decisions made deliberately, a named design system applied consistently, and a cross-platform stack chosen for cost and performance reasons rather than familiarity. You are not looking at a case study written after the fact to sound impressive. You are looking at the actual build.
Frequently Asked Questions
What stage of development is Billr in?
Billr is in active development. The UI is functional and running on localhost, the Cloudflare Workers backend architecture is built, and the design system is defined, but there is no live production URL yet.
What makes Billr different from other invoicing SaaS tools?
Billr is being built specifically for solo contractors as a lightweight "pocket CFO," rather than a scaled-down version of team-oriented accounting software, with a cross-platform architecture spanning React Native, Next.js, and an edge-deployed Cloudflare Workers backend.
Why use Cloudflare Workers instead of a traditional Node.js backend?
Because Billr's core use case benefits from low-latency, edge-deployed responses, and because Cloudflare Workers combined with D1, R2, and KV eliminates the need for separate server hosting and maintenance during an MVP's early lifecycle.
How is PDF generation handled without a headless browser?
Through Satori, which converts structured layout data into an SVG, combined with resvg to rasterize that SVG into a PDF, avoiding the overhead of running a full browser instance on an edge runtime not designed for it.
What is the SaaS MVP Build service, and how does it relate to Billr?
The SaaS MVP Build service, priced between $1,500 and $4,000 depending on scope, is the exact process being used to build Billr: deliberate architecture decisions, a documented design system, and a cross-platform stack chosen for performance and cost reasons. Billr is that process observed directly, not described after the fact.
Related Case Studies
- MailBurn: another infrastructure-heavy SaaS build, on dedicated cloud infrastructure rather than Cloudflare Workers
- SelfOS: another in-progress, architecture-forward build from the same studio
- Capitalyst and Second Encounter: additional products currently in active development
Work With NeuroStackOS
If you need a SaaS MVP built with the same deliberate architecture and design discipline shown here, this is exactly what the SaaS MVP Build service delivers. Get in touch to talk through scope and timeline for your product.