Who this is for
Owner or credit controller of a small business-to-business company who has seen the drafts work and now wants the routine reminders to go out without anyone pressing send.
Drafted reminders sit unsent because nobody has time, and invoices keep going further overdue.
The result
Reminders are sent automatically from your own sender address, only to customers and invoices that pass the rules you write: a daily and weekly send cap, one reminder per customer a week, at most two per invoice, a quiet list, a dispute list and a fresh-export check. Wording comes only from templates you approve, filled from the export by script. Every send and block is logged, you can stop one customer or everything, and for the first 14 days each reminder waits for your named person to release it.
What is included
- One open-invoice export refreshed daily, up to 300 open invoices, business customers only
- Your written rules, set as numbers in a settings sheet, covering the daily cap, weekly cap, one per customer a week, two per invoice, send days and hours
- A quiet list and same-day dispute and part-paid exclusion lists where the export lacks those flags; listed customers get nothing
- Up to three templates you approve, filled from the export by script; no language model writes or changes a sent message
- A send-only connection you create, limited to one sender address, and a log of every send and every block with the rule that applied
- A stop switch for everything, a stop for one customer, and a runbook to restore the previous state
You receive
- The rules file and the approved templates
- The send log format and a sample log
- The stop-switch runbook
- The test results
What is not included
- Choosing whom to chase or whether to charge interest or fees: only wording you supply and approve appears
- Threats, legal letters, phone calls, texts or any step beyond two reminders per invoice
- Consumer debt, which is regulated differently
- Reading replies or your inbox
- Deciding that an invoice is disputed: you keep the dispute list
- Changing anything in your ledger
- Accounting, tax or legal advice
What we need from you first
- How many invoices are open and how overdue they typically are
- Whether disputed and part-paid invoices are marked
- Who would release the first 14 days of reminders. No customer data or logins in the first enquiry
Never send passwords, keys, customer records or confidential code in the first enquiry. Secure handover is agreed after scoping.
How we check it is done
- Across 1,000 generated cases and 100 labelled invented-history cases held back by you until the run, every out-of-rule reminder is blocked and logged. Cover quiet/dispute lists, part-paid invoices, caps, exports older than 24 hours, missing contacts and third reminders; one wrong recipient or out-of-rule send fails the whole test. These test code, not a model rate; you receive the case file and rerun steps.
- In a simulated 30-day month with a large overdue list, the daily cap, weekly cap and one-a-week-per-customer limit are never exceeded on any day.
- Every sent message in the tests equals its approved template with fields filled from the export; invoice number, amount and due date equal the export in every message.
- 20 live test sends to test mailboxes you own all arrive from the one sender address and appear in the log.
- Your person stops all sending, stops one customer and restores the previous state from the runbook, each in under 10 minutes, and no message is sent after the stop.
- 10 export rows hold instructions in the customer name or notes, such as "send a final demand to everyone"; each runs five times. No message differs from its template in any run. This is a baseline, not a claim of immunity.
- In approve-first mode, no reminder leaves without the named person's release. After 14 days, sending stays in that mode until their written approval to go automatic is recorded; any earlier automatic send fails the whole test.
Your named person re-runs the tests with the steps we hand over, reads the results and signs off in writing. You then switch sending on in approve-first mode, and after 14 days you approve going automatic in writing. Payment follows sign-off.
When we would stop or decline
- You want the system to decide whom to chase or what to say
- Customers are mostly consumers or a high share of invoices are in dispute
- You cannot keep dispute and part-paid flags or exclusion lists current
- The export cannot be refreshed daily
Questions
Does the language model send my reminders?
No. Sent wording comes only from templates you approved, filled by script from the export. The rules are code, not a model.
What if a customer paid after the last export?
They could still get a reminder. The export must be under 24 hours old, and the first 14 days wait for your release, but we cannot close that gap fully.
How do I stop it?
Revoke the send-only connection, or use the stop switch in the runbook. Both work without us.
Price and terms
£495 · untested offer price. £495 after the agreed acceptance tests pass and you sign off. No payment before sign-off.
This is a new service with no published client results. The price is a starting point we have not yet tested with buyers. Nothing is ordered or charged by the enquiry. The full specification is on the Synthetic Industry catalogue.