Contents
PoliteDue — The Freelancer's User Manual
Get paid on time, without chasing clients.
| Product | PoliteDue |
| What it is | Polite SMS and email payment reminders for freelancers |
| Document | User Manual & Whitepaper, v1.0 (October 24, 2026) |
| Stage | Early Access |
| Audience | Early-access users, freelancers evaluating PoliteDue, partners |
| Web | politedue.com (production) |
A note on honesty: The full PoliteDue product is onboarding early-access users now. Everything in this manual marked Available now is live and usable today. Everything marked At launch is in active development and carrier registration. We don't describe capabilities that don't exist.
0. Executive Summary
The biggest hidden cost of freelancing isn't finding clients. It's getting paid.
85% of freelancers get paid late at least occasionally. The average freelancer is owed about $6,000 at any time. Chasing payments costs roughly 102 hours a year — three working weeks spent on follow-ups instead of billable work. And the tools that exist today either target finance teams (Chaser, from $259/mo) or send robotic emails that get buried (built-in QuickBooks reminders).
PoliteDue's answer: dunning, done politely.
Three product principles:
- SMS first. Email gets buried; texts get read in minutes. Every number is 10DLC-registered so reminders aren't filtered as spam.
- Human, not robotic. Warm phrasing clients appreciate. Many reply to say thanks. The relationship survives the reminder.
- Compliance built in. TCPA, 10DLC, Regulation F, and CAN-SPAM rules are enforced by the product itself — you never have to become an expert in debt-collection law to use it.
This manual covers the product, quick-start paths, the full compliance guide, pricing, and the roadmap.
1. The Problem: The Freelancer's Collections Problem
1.1 The double cost: money and time
| Metric | Figure | What it means |
|---|---|---|
| Paid late | 85% of freelancers | The norm for most, not the exception |
| Average owed | ~$6,000 | Two months of revenue sitting in someone's inbox |
| Annual time chasing | ~102 hours | At $75/hr, roughly $7,650 in lost billable time |
| Knock-on effect | 42% | Freelancers who miss their own bills because of cash-flow gaps |
Late payment is rarely malice. It's an attention problem — your invoice is drowning in your client's inbox. Collecting is, at its core, a competition for attention. And SMS wins that competition.
1.2 Why existing tools fall short
| Option | Price | The problem |
|---|---|---|
| Spreadsheets + calendar alarms | Free | All the execution cost is still yours: remembering, wording, sending, following up |
| QuickBooks / Xero built-in reminders | Bundled | Email only; robotic tone; doesn't solve the "buried inbox" problem |
| Chaser | $259–1,169/mo | Built for finance teams with SaaS-era pricing |
| Nudge | $9.99–19.99/mo | Right direction, but built for trade contractors — not freelancers working at a desk |
The gap: a collections tool designed for one person who does the work *and* sends the invoices — with an SMS channel and a human voice. That's the gap PoliteDue fills.
1.3 The psychological cost
More expensive than the money is the dread. Rewriting the same text eleven times so it doesn't sound mistrustful. Waiting three days for a reply that never comes. Finally writing it off — freelancers quietly abandon a meaningful share of receivables every year.
PoliteDue's design goal: turn "chasing payment" from an emotional event into an automated process.
2. The Solution: What PoliteDue Is
PoliteDue connects to your invoices, learns your due dates, and sends the right nudge at the right time — in your voice — by text or email. The moment a client pays, the reminders stop.
Configure once. Then do nothing.
2.1 The core loop
Connect invoices → Set your tone → PoliteDue follows up → Client pays → Reminders stop2.2 Design philosophy: why "PoliteDue"
The name says the whole model. Polite is the strategy — reminders stay warm and human, never threatening, because a freelancer's clients are a referral network, not a debt portfolio. Due is the object — the invoice that's owed, the payment that's late. PoliteDue is politeness applied to what's due.
PoliteDue does the opposite of the collections industry: politeness as a collection strategy. Every message keeps the tone of "just making sure this didn't slip through," and hands the decision back to the client, gently. In practice it works better — clients don't get defensive, so they act faster.
2.3 Three differentiating capabilities
- Registered 10DLC sender. Your texts land in inboxes, not spam folders — read within minutes (full compliance details in §5)
- Your voice, not a template. Three tone levels × two channels × automatic escalation by days overdue. Preview and edit any message before it goes out
- Built-in guardrails. Send windows, frequency caps, and opt-out handling are enforced by the product — you can't accidentally cross a legal line
3. Product Features
3.1 Feature overview and status
| # | Feature | Status | Notes |
|---|---|---|---|
| 1 | Free late-payment message generator | Available now | See §3.2 — usable today |
| 2 | Invoice connection (QuickBooks / Xero / FreshBooks / CSV) | At launch | Automatic due-date import |
| 3 | Three tones × Email/SMS channels | At launch | Full system in §3.3 |
| 4 | Automatic tone suggestion by days overdue | Available now (in the generator) | Fully automated in-product |
| 5 | Automatic late-fee calculation | Available now (in the generator) | Activates past 14 days overdue |
| 6 | "Sent with PoliteDue" signature | Available now (in the generator) | Toggle on/off |
| 7 | Automated scheduling and follow-up | At launch | Sends on schedule, stops on payment |
| 8 | Stripe pay links in reminders | At launch | One-tap payment |
| 9 | Aging report | At launch | Who owes what, for how long |
| 10 | 10DLC-registered sender | At launch | We handle registration |
3.2 Available now: the free late-payment message generator
Where: politedue.com/tool.html
A fully client-side tool — every message is generated in your browser. No client data ever leaves your machine (privacy design, §5.4).
What it does:
- Three tones: Friendly nudge → Firm follow-up → Final notice
- Two channels: Email (with subject line) and SMS (length-optimized)
- Two variants per tone per channel: 12 message combinations — no "blast" feel
- Automatic tone suggestion: Enter the due date; the tool calculates days overdue and recommends a tone (0–3 days: friendly / 4–14: firm / 15+: final notice)
- Automatic late-fee math: Enter your contract's late-fee percentage; past 14 days overdue the message automatically includes "our agreement includes a X% late fee on invoices past 14 days — that would add $XX.XX" — finally putting that clause to work
- One-click copy: Copy, paste, send
- "Sent with PoliteDue" signature: Optional toggle. When on, every message carries the signature — clients learn PoliteDue exists, which is how the product spreads
How to use it (3 minutes):
- Fill in: client name, invoice number, amount, due date, your name
- Pick a channel (Email / SMS) and tone (or accept the auto-suggestion)
- Optional: payment link, late-fee percentage
- Preview → Copy → Send
When to use it: you need to send a reminder *now* and can't wait for the full product. It's free forever, no signup.
3.3 At launch: the full product
Invoice connection: Link QuickBooks, Xero, or FreshBooks, or upload a CSV. PoliteDue imports due dates and builds the follow-up queue automatically. You don't change how you invoice.
Tone system: Three levels for three stages of the client relationship. Preview, edit, or switch off any message. PoliteDue sounds like you.
Automated scheduling:
| Timing | Action |
|---|---|
| 3 days before due | Friendly heads-up ("invoice due Thursday") |
| Due date | Friendly reminder + payment link |
| 3 days overdue | Firm follow-up |
| 7 days overdue | Firm follow-up |
| 14 days overdue | Final notice + late-fee clause |
| Client pays | All follow-ups stop immediately |
Scheduling respects the compliance guardrails (§5.3): sends only within 8:00 AM–9:00 PM client local time; at most one touch per invoice per week.
Stripe pay links: Every reminder can carry a one-tap payment link. The easier you make paying, the faster you get paid.
Aging report: All open invoices bucketed 0–30 / 31–60 / 61–90 / 90+ days. One glance tells you who owes what and for how long. Ready for tax season and cash-flow planning.
10DLC-registered sender: We complete US carrier registration for all sending numbers, so your texts aren't filtered (§5.2).
4. Quick Start
4.1 Today (free, 3 minutes)
- Open
politedue.com/tool.html - Generate a reminder per §3.2
- Copy and send
Nothing to install, no account. Bookmark it for the next time a client goes quiet.
4.2 At launch (early-access users)
- Join the waitlist (landing page) → receive your invite
- Connect your invoices (QuickBooks / Xero / FreshBooks / CSV upload)
- Set tone and timing: pick your default tone; confirm send-window preferences
- Optional setup: Stripe pay link, late-fee percentage, signature toggle
- Turn on automation: then forget about collections
- Check the aging report weekly: that's the whole routine
Early access is $9/mo, locked for as long as you stay subscribed (public price at launch: $18/mo). You are never charged before PoliteDue is live and actually sending your reminders.
5. The Compliance Guide
This chapter is the line between PoliteDue and bulk "reminder blasters." It's both our internal compliance spec and your guide to collecting without legal risk.
5.1 The legal framework, in plain English
| Regulation | What it governs | What it means for you |
|---|---|---|
| TCPA (Telephone Consumer Protection Act) | Texts and calls | Fines of $500–1,500 per violation. Transactional messages tied to an active invoice carry an implied-consent threshold well below marketing texts — PoliteDue sends only transactional messages |
| 10DLC | US commercial long-code registration | Unregistered numbers get blocked by carriers, full stop. PoliteDue registers everything; users do nothing |
| Regulation F | Time and frequency of collection contact | Applies to *debt collectors*. PoliteDue operates as self-collection — you reminding your own client about your own invoice — which is a fundamentally different legal category. This is why PoliteDue must not be used to collect on behalf of third parties |
| CAN-SPAM | Commercial email | Requires sender identity, physical address, and unsubscribe. Built into every PoliteDue email |
| California SB-988 | Late fees on B2B invoices | Lets you enforce contractual late fees (up to 2× the amount owed) — a selling point for PoliteDue's late-fee feature, not a risk |
5.2 What PoliteDue does for SMS compliance
- 10DLC registration. All sending numbers are registered with US carriers; brand/campaign filings are transactional (account servicing), maximizing deliverability
- Transactional content only. Every text references a real, existing invoice with a genuine business relationship. There is no "marketing blast" capability — the product can't do it
- Transparent identity. Every message identifies you (your name or studio)
- Opt-out honored immediately. A reply of STOP removes that contact from all SMS; email unsubscribes sync automatically
5.3 Frequency and timing guardrails (product-enforced)
| Guardrail | Rule | Enforcement |
|---|---|---|
| Send window | 8:00 AM–9:00 PM client local time only | Hard-coded in scheduler |
| Frequency cap | Max 1 reminder per invoice per week | Hard-coded in scheduler |
| Channel rotation | No same-channel bombardment within a week | Hard-coded in scheduler |
| Payment stops all | Any payment cancels all pending follow-ups | Event-driven |
| Human veto | Preview, edit, or cancel any message | Always available |
5.4 Privacy design
- Client-side generator: the free tool never sends your client data anywhere — generation happens 100% in your browser
- Data minimization: the full product stores only the invoice metadata needed to send reminders (client name, amount, due date, status)
- No data monetization: we don't sell or share user data. Privacy policy public at /privacy.html
5.5 Your two red lines
The product handles the engineering. Two rules are yours alone:
- Only collect your own invoices. PoliteDue is a self-collection tool. Using it to chase debts on someone else's behalf makes you a "debt collector" under Regulation F — a completely different legal regime. Don't cross that line
- Late fees need a contractual basis. Before enabling late fees, confirm your contract or engagement letter actually includes a late-fee clause. Without one, late fees are unenforceable in most states
6. Pricing
| Tier | Price | What you get |
|---|---|---|
| Free tool | $0 | The message generator. Free forever, no signup |
| Early access | $9/mo (price-locked) | Full product. Public price at launch: $18/mo — your rate never increases while subscribed |
| Public | $18/mo | Same as early access |
Why this price is sustainable: a single SMS costs about $0.004 (Telnyx transport); 10DLC registration runs $4–15/mo. A solo freelancer sends tens of messages a month at most — variable costs are trivial, leaving 85%+ gross margin at $9. The $259 enterprise tools carry sales-team and compliance-department costs. PoliteDue carries neither.
Free-trial commitment: a free allowance at public launch, no charge during trial, and zero charges to early-access users until PoliteDue is genuinely sending your reminders.
7. Roadmap
| Phase | Milestone | Status |
|---|---|---|
| Shipped | Landing page, waitlist, free message generator | Live |
| Weeks 1–2 | Permanent domain, Search Console, SEO tool pages | In progress |
| Weeks 3–4 | Early-access rollout in batches; 10DLC registration; Stripe connection | Planned |
| Validation gate | 50 real early-access signups → full investment | Decision criteria |
Our stop-loss discipline (stated openly): if after four weeks of genuine effort fewer than 15 real signups exist, PoliteDue stops absorbing resources and we move to an alternative direction. We don't pretend every project succeeds — this discipline is part of the project's quality.
8. FAQ
Will my clients be annoyed by text reminders?
No — that's the design premise. Messages stay polite, escalate only with age, and stop the instant they pay. Transactional texts tied to an active invoice land in a different psychological category than marketing texts. The most common client reply is "thanks for the reminder."
Is this even legal — TCPA, 10DLC, all that?
Yes, and you don't need to understand the law to use it. 10DLC registration, send windows, frequency caps, and opt-outs are all enforced inside the product. Your only two obligations: collect only your own invoices, and have a contractual basis for late fees (§5.5).
How is this different from QuickBooks' built-in reminders?
QuickBooks sends email — which gets buried. PoliteDue's core addition is the SMS channel (read in minutes) plus a human tone plus a complete follow-up schedule. They coexist happily: accounting in QuickBooks, collections in PoliteDue.
I already use a tool that sends emails.
That solves sending, not being read. SMS open rates are an order of magnitude above email. PoliteDue layers on top of your email tool; it doesn't replace it.
When can I use the full product?
Early access is opening in batches now. Join the list, receive your invite, connect invoices, switch on automation. No charges until it's genuinely working for you.
Will the free generator stay free?
Yes, permanently. It's PoliteDue's front door and its SEO engine. No signup, no trial clock.
What happens to my data?
The generator runs entirely in your browser — nothing leaves your machine. The full product stores the minimum metadata required to send reminders. Public privacy policy at /privacy.html, and we never monetize data.
Appendix A: Glossary
| Term | Meaning |
|---|---|
| Dunning | The industry term for overdue-payment collection |
| 10DLC | The US standard for registered commercial long-code texting; unregistered numbers are carrier-blocked |
| TCPA | Telephone Consumer Protection Act — governs texts/calls; transactional and marketing follow different rules |
| Regulation F | Fair Debt Collection Practices rules — applies to debt collectors, not self-collection |
| CAN-SPAM | The US commercial email law: identity, address, unsubscribe |
| Self-collection | A creditor collecting their own receivable — a different legal category from third-party collection |
| Aging report | Receivables bucketed by days overdue |
| MoR | Merchant of Record — a compliant global payment model |
Appendix B: Contact & Support
- Product & early access: politedue.com
- Free tool: /tool.html
- Privacy policy: /privacy.html · Terms: /terms.html
- Partnerships and press: via the contact form on the site
User Manual v1.0 · October 24, 2026 · Written for the early-access stage. Feature statuses reflect actual capability at publication; regulations and platform rules change — verify before relying on any specific rule.