惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Y
Y Combinator Blog
The GitHub Blog
The GitHub Blog
云风的 BLOG
云风的 BLOG
Engineering at Meta
Engineering at Meta
Google DeepMind News
Google DeepMind News
aimingoo的专栏
aimingoo的专栏
Recent Announcements
Recent Announcements
A
About on SuperTechFans
U
Unit 42
MyScale Blog
MyScale Blog
J
Java Code Geeks
博客园_首页
Blog — PlanetScale
Blog — PlanetScale
D
Docker
Microsoft Azure Blog
Microsoft Azure Blog
博客园 - 司徒正美
量子位
月光博客
月光博客
G
Google Developers Blog
V
V2EX
博客园 - 聂微东
宝玉的分享
宝玉的分享
IT之家
IT之家
Vercel News
Vercel News

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Why your invoices get paid late (it's usually not the cli...
Giuseppe Tumino · 2026-06-15 · via DEV Community

Giuseppe Tumino

When an invoice goes unpaid, the easy story is "bad client." Sometimes that's true. But after tracking mine for a year, I think the bigger culprit is usually closer to home: inconsistent timing and weak wording.

The timing problem

Most freelancers chase invoices "when they remember", which, realistically, is when cash is tight, around day 12+. By then the invoice is old news in the client's inbox, the nudge feels apologetic, and it's easy to ignore.

The clients who pay fast aren't nicer. They're the ones who got a calm, prompt reminder before the invoice went stale. Speed signals that you track this, and people pay attention to people who pay attention.

The cadence that works

Apply the same schedule to every invoice, no decisions required:

  • +3 days late → friendly nudge ("did this slip through?")
  • +10 days → firm reminder ("second reminder, please confirm a date")
  • +20 days → final notice (with consequences and, if applicable, a late fee)

Consistency is the whole trick. When it's automatic, you never wonder "is it too soon?", and you never let one slide for a month.

The wording problem

"Just checking in!" is the most ignorable sentence in business. A calm, specific ask is not:

Hi [Name], invoice [INV-014] for $1,200 was due on May 30, I haven't seen it land yet. Could you check on it this week? Thanks!

Specific invoice, specific amount, specific date, specific ask. No apology, no aggression. That's the template that gets replies.

Take the friction out

If writing these is the part you avoid, that's exactly why I built a free overdue-invoice email generator: pick the tone, it writes the message with the details filled in. No sign-up. And the full system that runs the whole cadence for you, picking who to chase today and which email to send, is Get Paid OS.

But you don't need any tool to start. Adopt +3 / +10 / +20 with specific wording this week, and watch how much faster the "bad clients" suddenly pay.

What's the most effective follow-up line you've used? Drop it below, always collecting good ones.