# ContractClaim

> Contract generation and graded invoice chasing for solo freelancers — a getting-paid platform that goes where Bonsai's reminder module stops, sold once.

Source page: https://saascode.ai/products/contractclaim
Machine-readable record: https://saascode.ai/products/contractclaim.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

ContractClaim does two things for a one-person business: it chases late invoices through a tone-graded escalation — polite, then firm, then pre-litigation — tied to a metric worth watching, and it generates simple contracts that account for the jurisdiction they will be used in.

## 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/contractclaim — our shell, with a role switcher and
  the credentials in the menu. Best for a person.
- **Direct:** https://contractclaim.saascode.ai — the product on its own, no chrome.
  Best when you are relaying steps to someone, or fetching a page.

2 roles seeded on the demo (of the 4 the schema defines — the build data below counts them all). Credentials are published deliberately: these
are demo accounts on a public demo instance, and a reviewer who cannot get
in cannot verify anything.

- **Freelancer owner** (`org_admin`) — `user@demo.com` / `demo123`
  Chases late invoices: escalations, contracts, DSO.
- **Platform admin** (`super_admin`) — `admin@demo.com` / `demo123`
  The backend: cross-organisation oversight.

Or open a role directly: https://saascode.ai/demo/contractclaim?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: 51** — distinct CREATE TABLE statements across every applied migration
- **migrations: 47** — .sql files in supabase/migrations
- **page modules: 79** — files named page.tsx under src/app, excluding node_modules and .next
- **source lines: 110,606** — lines of code (comments and blank lines excluded) across 810 TypeScript files (101,128) and 63 SQL files (9,478); node_modules and .next excluded
- **api route files: 162** — files named route.ts under src/app/api
- **http operations: 216** — exported HTTP method handlers across those files, de-duplicated per file, OPTIONS excluded as CORS preflight
- **schema graph: 51 tables, 81 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-07-01

## Complete capability inventory

8 capabilities. Each summary is *stated* — selected from the
product's own buyer documentation, or written by the seller where marked.

### Contracts & metrics

- **DSO + avg-late-days dashboard** — Days sales outstanding and average days late, with trending on the higher tier from periodic snapshots.
- **DSO trending (snapshots chart)** *(seller-authored)* — Periodic snapshots turn days-sales-outstanding into a line rather than a number, so a business can tell whether payment behaviour is improving or quietly getting worse. A single figure never answers that.
- **Contract generation (PDF)** — Contracts generate as PDFs from templates that account for jurisdiction — United Kingdom, United States and European Union.

### Invoices & escalation

- **Invoice + client management** — Invoices and the clients they belong to, with due dates, amounts and status. This is a receivables register rather than a ledger — it exists to answer who owes what and for how long.
- **Due-date monitoring cron** — A scheduled job watches due dates and moves invoices into overdue as they pass, which is what starts the escalation clock.
- **Collections handoff packet** — On the higher tier, a handoff packet: the invoice, its history, every reminder sent and when, and the pre-litigation letter, assembled into something a collections service or a solicitor can act on, plus the referral.

### What it is

- **Tone-graded escalation (3 stage)** — Chasing an invoice is a relationship problem before it is an accounting problem. Sending a firm demand too early costs a client; never sending one costs the money.
- **Teammate invite (scoped member)** — One installation, many isolated workspaces. Invoices, clients, contracts, escalation settings and the metric history are private to a workspace.

## What each system gives the operator

*stated.*

- **Contracts & metrics** — You can see how late you are being paid, and whether it is getting worse.
- **Invoices & escalation** — Late payers get chased on schedule without you writing the awkward email.
- **What it is** — Getting paid stops depending on how confrontational you feel that week.

## The problems it was built to solve

*stated — the seller's argument, given in full so you can judge it.*

### Three escalating reminders go out on schedule, in a tone you chose in advance.

Chasing late payment is the least favourite job in a one-person business, and it is the one where hesitating costs the most. The first reminder is easy and gets sent. The second feels rude, so it waits a week. The third never happens at all, because by then the relationship feels strained and confronting it directly is worse than absorbing the loss. The invoice is not written off; it is simply never mentioned again, and the pattern repeats with the next client who pays late.

### One number tells you how long your money actually takes to arrive.

Freelancers rarely know their real payment behaviour. There is a feeling that clients are slow, and there are a few memorable disasters, but no figure — so there is no way to tell an ordinary bad month from a trend that will end the business in six. Decisions that depend on it get made on instinct: whether to take the client who pays at ninety days, whether to raise rates, whether the cash-flow problem is a pricing problem or a collections problem.

### The agreement is a document you generate, not one you postpone.

Small jobs start without paperwork because paperwork feels disproportionate to the size of the job. Then payment terms turn out to be whatever each party remembers, scope was never written down, and the argument happens over messages sent weeks apart. The cost is not usually a lawsuit — nobody sues over an amount this size. It is that the freelancer absorbs the difference, quietly, and calls it the price of doing business.

## What it takes to run it

*stated — external services the buyer supplies and pays for directly.*

- **Node host** (required) — No platform lock-in.
- **Supabase** (required) — Postgres with row-level security, applied by the shipped migration scripts.
- **Email provider** (required) — The reminders are the product. Without it nothing is chased.
- **A cron caller** (required) — Due-date monitoring and escalation run on a schedule. Without it invoices are never marked overdue and no stage ever fires.
- **A payment provider** (required to charge) — Configured by the operator, not hardwired.

## FAQ

**What exactly do I receive after purchase?**

The complete source repository behind the live demo — 110,606 lines across the application and its database, 51 tables defined by 47 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 ContractClaim 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 2 of them: Freelancer owner, 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. 79 page modules and 216 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: Node host, Supabase, Email provider, A cron caller, A payment provider. 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 47 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

- [Getting-Paid Software for Freelancers: A Buyer's Guide 2026](https://saascode.ai/inside/getting-paid-software-for-freelancers-a-buyer-s-guide-2026.md)
- [ContractClaim vs Paidnice — Which Late-Payment Chaser Works Without an Accounting System](https://saascode.ai/inside/contractclaim-vs-paidnice-which-late-payment-chaser-works.md)
- [ContractClaim: contracts and invoice chasing for solo freelancers](https://saascode.ai/inside/road-to-contractclaim.md)

## Links

- Catalog page: https://saascode.ai/products/contractclaim
- Product record: https://saascode.ai/inside/products/contractclaim
- Live demo: https://contractclaim.saascode.ai
- Every product: https://saascode.ai/llms.txt