ContractClaim
Contract generation and graded invoice chasing for solo freelancers — a getting-paid platform that goes where Bonsai's reminder module stops, sold once.
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.
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.
- Due-date monitoring cron
- Tone-graded escalation (3 stage)
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.
- DSO + avg-late-days dashboard
- DSO trending (snapshots chart)
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.
- Contract generation (PDF)
Trending is where the number becomes useful. A single figure says the business waits 47 days. A trend says whether last quarter's decision to escalate sooner did anything.
Trending is where the number becomes useful. A single figure says the business waits 47 days. A trend says whether last quarter's decision to escalate sooner did anything.
Jurisdiction awareness is the part that makes them usable rather than decorative. A generic contract template is a document that reads like a contract; a jurisdiction-aware one carries the terms that region actually expects.
The entry tier covers one jurisdiction and three template slots; the higher tier covers all three regions with unlimited templates.
These are simple contracts. Not a contract-lifecycle platform, no negotiation workflow, no e-signature suite.
You receive this. It ships behind a feature flag and sits on the requires_plan = all plans; jurisdiction_count limit gates UK-only vs multi tier as configured, so it is revenue you can reserve for your own paying customers.
Invoices import by CSV or spreadsheet, so an existing list moves in without retyping.
That schedule is a real requirement rather than an implementation detail: without a cron caller nothing is marked overdue and no reminder fires, and the product's core behaviour quietly stops.
The packet matters because the evidence of having chased properly is what makes the escalation credible to whoever picks it up next.
You receive this. It ships behind a feature flag and sits on the requires_plan = Pro only tier as configured, so it is revenue you can reserve for your own paying customers.
ContractClaim grades the escalation across three stages with fixed, professionally reviewed templates, so the escalation happens on schedule rather than on mood. The freelancer is not composing an awkward email at 11pm and deciding how angry to sound.
You receive this. It ships behind a feature flag and sits on the none (core — must NOT fail-closed) tier as configured, so it is revenue you can reserve for your own paying customers.
The bookkeeper role is scoped deliberately: someone helping with the admin should be able to send the reminder without being able to rewrite what the reminder says.
The platform underneath the product — counted in this product's own source, not claimed from a template. Where a row carries a list, open it to read the names behind the number.
Coinbase
dLocal
Flutterwave
Komoju
Mollie
NOWPayments
Opn
Paystack
ActiveCampaign
Customer.io
Segment
Canny
Amplitude
Custom Head Scripts
Pushover
Twilio SMS
Crisp
Tawk.to
Monday.com
fal.ai
Axiom
hCaptcha
Freshsales
Pipedrive
Pabbly Connect
AWS S3
MuxHover a table to isolate what it touches; click one to read its relationships. The big nodes are what everything else hangs off. organizations is referenced by 44 tables because every single record in this product belongs to an organization, and that is what makes tenant isolation a property of the database rather than something the application has to remember on every query.
all 51 tables, as text
active_boosts · admin_notifications · announcement_dismissals · announcements · api_key_logs · api_keys · audit_logs · automation_log · automation_templates · clients · collections_handoffs · contract_templates · contracts · credit_balances · credit_transactions · currencies · data_exports · data_imports · dso_snapshots · escalation_events · escalation_templates · faq_categories · faq_items · feature_flags · inbound_webhooks · invoices · languages · notification_log · notification_rules · notifications · organization_limit_overrides · organizations · plans · platform_secrets · platform_settings · product_purchases · products · provider_prices · push_devices · report_templates · roles · scheduled_tasks · subscriptions · theme_page_sections · theme_section_library · theme_sections · translations · user_sessions · users · webhook_logs · webhooks
The chassis, and anything particular to this product. 4 required, 1 optional.
No platform lock-in.
Postgres with row-level security, applied by the shipped migration scripts.
The reminders are the product. Without it nothing is chased.
Due-date monitoring and escalation run on a schedule. Without it invoices are never marked overdue and no stage ever fires.
Configured by the operator, not hardwired.
Already built — plug and play
Every provider integration in this list ships wired into the product. You bring your own keys, connect them in the admin, and go live — there is no integration code to write. Nothing is resold through us: the ongoing cost is whatever these providers charge you. Capabilities marked plan-gated elsewhere on this page unlock by plan, not by extra code.
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.