# Billora > Quote to paid without the accounting, and without FreshBooks' five-client ceiling — an invoicing SaaS you rebrand and run as your own. Source page: https://saascode.ai/products/billora Machine-readable record: https://saascode.ai/products/billora.md One-time purchase · full source code · self-hosted by the buyer. Price: $89 (one-time) ## How to read this document Written for a model auditing this product on a buyer's behalf. Two labels appear throughout and they mean different things: - **measured** — produced by a script reading the product's own source tree or database at the stated date. The method is named beside each number. - **stated** — written by the seller. True or not, it is a claim, and this document does not ask you to treat it as evidence. The live demo is the strongest verification available from outside: it runs the same source a buyer receives. Nothing to sign up for — the public side is open, and the seeded credentials below get you into each role. ## What it is Billora is a multi-tenant invoicing product for freelancers and small service businesses — roughly the 5–50 clients per month range. Each organization is one business, fully isolated from every other, invoicing its own clients. ## Live demo Two doors into the same running instance, and the same source a buyer receives. There is no account to create; the public side is open, and the seeded credentials below sign you into each role. - **Guided (recommended):** https://saascode.ai/demo/billora — our shell, with a role switcher and the credentials in the menu. Best for a person. - **Direct:** https://billora.saascode.ai — the product on its own, no chrome. Best when you are relaying steps to someone, or fetching a page. 4 seeded roles. Credentials are published deliberately: these are demo accounts on a public demo instance, and a reviewer who cannot get in cannot verify anything. - **Teammate** (`member`) — `user@demo.com` / `demo123` Works invoices and clients, without account admin. - **Business owner** (`org_admin`) — `org-admin@demo.com` / `demo123` Runs the account: invoices, clients, billing, team. - **Platform staff** (`admin`) — `ops@demo.com` / `demo123` Operator surfaces, without owning an organisation. - **Platform admin** (`super_admin`) — `admin@demo.com` / `demo123` The backend: every organisation, plans and settings. Or open a role directly: https://saascode.ai/demo/billora?role={role} ## Measured build *measured — each number names the method that produced it.* - **roles: 4** — distinct roles accepted by the role CHECK constraint: admin, member, org_admin, super_admin - **tables: 67** — distinct CREATE TABLE statements across every applied migration - **migrations: 105** — .sql files in supabase/migrations - **page modules: 81** — files named page.tsx under src/app, excluding node_modules and .next - **source lines: 150,461** — lines of code (comments and blank lines excluded) across 1064 TypeScript files (137,025) and 109 SQL files (13,436); node_modules and .next excluded - **api route files: 220** — files named route.ts under src/app/api - **http operations: 299** — exported HTTP method handlers across those files, de-duplicated per file, OPTIONS excluded as CORS preflight - **schema graph: 67 tables, 112 relationships** — parsed from the applied migrations A large number here is scope, not quality. It says the product models a real domain rather than a CRUD skeleton; it says nothing about code quality, duplication, test coverage or maintainability, and should not be read as if it did. Release: v1.0.0 · built 2026-08-01 ## Complete capability inventory 12 capabilities. Each summary is *stated* — selected from the product's own buyer documentation, or written by the seller where marked. ### Automation & scheduling - **Branded PDF (invoice + quote)** — Invoice and quote documents are rendered as branded PDFs in the background and stored privately. Customers reach them through a signed link, and emails never carry attachments — attachments are a common cause of spam filtering and size limits, so the email carries a link to the document instead. - **Recurring billing** — Available on the Pro and Business plans. An organization administrator creates a schedule against a client — an amount, a cadence and a start date — and invoices are generated automatically from it. - **Automatic overdue reminder cadence** — Detection runs for every plan. Once an invoice passes its due date, it is marked overdue regardless of what the business pays for. ### Getting paid - **Client records + account statement** — Each client record carries a statement showing what has been billed, what has been paid, the outstanding balance and what is overdue — derived from the underlying documents rather than from a separately maintained running total, so it cannot fall out of step. - **Manual payment tracking + reconciliation** — Payments can be recorded manually (for bank transfers, cash or cheques) on any plan, or arrive automatically from an online payment confirmation. - **Online payment collection (BYO Stripe Connect Standard + BYO link)** — Billora takes zero custody. Money never passes through the platform's account. ### Operating the instance - **Reports (billed/collected/outstanding by period)** — The dashboard shows billed, collected, outstanding and overdue totals with recent invoices. The reports area breaks the same figures down by period with a date-range picker. - **Billora branding removal** *(seller-authored)* — Removes the platform's own mark from customer-facing invoices, quotes and PDFs, so the documents a business sends carry only its own identity. It ships behind a feature flag on a paid tier, which is revenue the buyer can reserve for their own customers. - **CSV import/export** *(seller-authored)* — Moves clients and documents in and out as CSV, so a business arriving from another tool can bring its history with it and leave with it later. Data that only exists inside the product is a reason not to adopt it. ### Quotes & invoices - **Invoices (numbering, line items, discounts, taxes)** — Documents carry line items with quantity, unit price and description; discounts and organization-configured taxes apply on top. All money is calculated on a single shared integer-based core so the totals a business sees while editing match the totals the server stores, including on fractional quantities. - **Quotes + online acceptance → conversion** — A quote moves through draft → sent → viewed → accepted/declined/expired, and an accepted quote becomes converted. An invoice moves through draft → sent → viewed → paid, with overdue and cancelled (voided) as additional states. - **Overdue reminders — manual send** — Overdue reminders can be sent manually from an invoice on any plan. Reminders are deduplicated per invoice per day, so pressing the button twice does not email a customer twice. An automatic reminder cadence exists on paid plans — see the automation and scheduling notes. ## What each system gives the operator *stated.* - **Automation & scheduling** — Invoices go out and chase themselves without anyone setting a calendar reminder. - **Getting paid** — The money lands in the business's own account, never in yours. - **Operating the instance** — Support fixes are a closed set of named actions, not free-form edits to money. - **Quotes & invoices** — A sent document cannot change underneath the customer who received it. ## The problems it was built to solve *stated — the seller's argument, given in full so you can judge it.* ### Your customers collect their own revenue directly, in their own name. The moment a platform sits between a business and its customers' money, it inherits problems it cannot afford. Chargebacks arrive against the wrong entity. Payouts need reconciling. A dispute between two other parties becomes a support ticket, and in some jurisdictions holding funds at all changes what kind of company the operator is. Most small platforms discover this after the first refund goes wrong, when the answer to whose money that was turns out to be genuinely unclear. ### The document your customer received is the one they can still see. Invoices get edited after they are sent. Someone fixes a typo, corrects a rate, adjusts a line — and now the customer's copy and the business's copy disagree about what was owed. It surfaces during a payment dispute, months later, when the two versions are put side by side and neither party can prove which came first. For an accountant it is worse than an error: it is a record that cannot be trusted, which makes every other record in the same system suspect. ### Overdue invoices are found and followed up without a person doing it. Late payment is rarely a collections problem. It is an attention problem. The invoice goes out, the due date passes quietly, and nobody notices until the month-end review — by which point the polite first reminder is three weeks late and the conversation is already awkward. Small businesses carry this as a permanent cash-flow drag they blame on customers, when the actual cause is that following up is somebody's least favourite job and it always loses to something else. ## What it takes to run it *stated — external services the buyer supplies and pays for directly.* - **A Node host and a Supabase project** (required) — The chassis. Next 16 on any Node host, with Postgres, auth and private document storage coming from Supabase. - **A scheduled runner** (required) — Three jobs run without anyone pressing a button: recurring invoice generation daily, the overdue sweep every six hours, and PDF rendering in the background. They ship declared for Vercel; on another host they are a cron configuration you wire by hand, and recurring invoices do not generate until something calls them. ## FAQ **What exactly do I receive after purchase?** The complete source repository behind the live demo — 150,461 lines across the application and its database, 67 tables defined by 105 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used. **Is the live demo the same product whose source I receive?** Yes. The Billora demo runs the delivered release (v1.0.0), and the build figures on this page are measured from that same source — not from a showcase build kept separately. **Can I test every account role before buying?** Yes — all 4 of them: Teammate, Business owner, Platform staff, Platform admin. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide. **Is this a complete product or a starter template?** Complete. 81 page modules and 299 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating. **Can I rebrand and modify it?** Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for. **What does the licence allow?** A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers. **Can I resell the source code?** No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you. **What services and ongoing costs are required?** You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: A Node host and a Supabase project, A scheduled runner. Optional: none. The table above says exactly what stops working without each one; most have usable free tiers at low volume. **How difficult is deployment?** Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 105 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand. **What updates and support are included?** Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts. **Why does a complete codebase cost $89?** Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned. **Do I need to be a developer?** No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows. ## Licence The buyer receives the complete source and may deploy, modify and operate it as their own SaaS, charging their own customers. The source itself is not resold or redistributed: you build and deliver **with** it, you do not sell **it**. ## What this document cannot tell you Stated plainly because a review that misses it is not a review: - code quality, duplication, or architectural consistency - test coverage - query performance under load - security posture beyond what the stack implies - how maintainable it will be in a year Scope is measurable from outside; implementation quality is not. Anyone evaluating this should say so rather than infer quality from size. ## Written about it - [Billora vs Invoice Ninja](https://saascode.ai/inside/billora-vs-invoice-ninja.md) - [Invoicing Software Buyer's Guide 2026](https://saascode.ai/inside/invoicing-software-buyer-s-guide-2026.md) - [Road to Billora](https://saascode.ai/inside/road-to-billora.md) ## Links - Catalog page: https://saascode.ai/products/billora - Product record: https://saascode.ai/inside/products/billora - Live demo: https://billora.saascode.ai - Every product: https://saascode.ai/llms.txt