Paydate — construction payment deadline SaaS - Sell Project

Try it https://paydate-zarus1.vercel.app The live demo runs with no database, so nothing you type is sent anywhere — claims stay in your browser. Everything the product is about works: add a claim, read the statutory clock, and generate both documents. Accounts and the email deadline reminders are switched off in the demo; both are in the source and covered by the tests. What it is Paydate tracks the statutory deadlines under the Building and Construction Industry Security of Payment Act 1999 (NSW) — the law that lets an unpaid subcontractor force a builder to pay. The law works fast, but only if the claimant hits a chain of strict deadlines: 10 business days, then 20, then 5, then 10. Miss one and the right to adjudicate is gone for that invoice. Most subcontractors have never been told the deadlines exist. Paydate takes the date an invoice was served, computes every date that follows, names the section of the Act each one comes from, and emails the claimant before each deadline. Why the engine is the asset NSW SOPA carries its own definition of "business day" (s 4): it excludes weekends and public holidays, and also 27–31 December. A generic business-day library gets this wrong, and a claim served in mid-December lands up to a week early on its due date. NSW also does not substitute Anzac Day when it falls on a weekend, unlike most states. Both rules are encoded and tested. The holiday table is bounded — asked for a date past verified data the engine throws rather than guessing, because a confident wrong date costs someone their claim. What is built — Timeline engine covering all four s 17 routes to adjudication. — s 13 payment claim generator and s 17(2) notice generator. Both refuse to emit an invalid document rather than producing something that merely looks official: they block premature service, service after the window closes, unidentified work, and line items that do not reconcile. — Head contractors are warned that serving without a supporting statement is an offence under s 13(7), carrying up to 3 months imprisonment under s 13(8). — Deadline reminders by email at 5 business days, 2 business days, on the day, and once after one passes. Idempotent by design: each send is recorded before the email leaves, under a unique database index, so an overlapping cron run cannot warn twice. — Email and password auth, with claims scoped by owner in the SQL WHERE clause. — Works fully signed out in browser storage, and claims migrate into the account on first sign-in. — A plain-English manual for beginners built into the app. Stack Next.js 16, TypeScript, Drizzle over libSQL (a local SQLite file in development, Turso in production — same code, one environment variable), Better Auth. 5,374 lines of application code, 717 lines of tests, 76 tests passing. No paid dependency anywhere: reminders print to the console until a mail key is set. Honest disclosure — Pre-revenue. No users and no live deployment yet. — The document templates have NOT been reviewed by a NSW construction lawyer. That review is a real blocker before the app goes near a claimant, and the buyer inherits it. — NSW only. Porting to another Australian state, or to Singapore, Malaysia or the UK, means adding a sibling rules module with its own verified holiday table. The architecture is built for it; the work is not done. What the sale includes The full private GitHub repository — all source, tests, database migrations and design documentation, with a clean commit history. There are no third-party accounts to transfer and no running costs.