Most founders lose revenue not because they priced wrong or built the wrong thing, but because they never followed up. Invoice goes out. Client goes quiet. Founder goes uncomfortable. Days become weeks, weeks become a quarter, and that $18,000 from a signed contract is somehow still just a number in a spreadsheet. This is not a cash flow problem. It is a psychology problem, and it is costing startups more than bad hires do.

At AG Accounting, we see this constantly. Founders who negotiated a term sheet without blinking will sit on a 60-day-overdue invoice because "it feels awkward to push." This piece is about fixing that, and about two tools we have built and use ourselves that make the operational side significantly less painful.

Why Founders Avoid Dunning (And Why That Avoidance Is Expensive)

Dunning is the formal term for following up on unpaid invoices. It comes from 17th-century English slang for a creditor who persistently demands payment. The etymology alone tells you something about the cultural baggage attached to asking for money you are owed.

For founders, the hesitation is layered. There is the relationship anxiety, the fear of souring a client or looking desperate. There is the time cost, because writing a follow-up email that threads the needle between firm and friendly is genuinely hard. And there is the cognitive load of tracking who owes what and when the last nudge went out.

The financial reality cuts through all of that. U.S. businesses write off approximately $825 billion in accounts receivable annually, according to research from Atradius. A significant portion of that is not from clients who cannot pay. It is from clients who were never asked firmly enough, or who simply fell through the cracks of a founder's overloaded week. For a pre-Series A startup, a single uncollected $25,000 contract can represent two months of runway.

What a Dunning Email Actually Needs to Do

The function of a dunning email is narrow: remind the client that payment is due, make it easy for them to act, and preserve the relationship while doing it. The failure mode is two-pronged. Either the email is too soft ("just checking in!") and gets treated as optional, or it is too aggressive and triggers a defensive response from the client's AP department.

The tone that works is matter-of-fact. Not apologetic, not confrontational. Something closer to how a CFO at a well-run company would write to a peer: accurate, direct, with a clear action step.

Getting this right for every overdue invoice, across a portfolio of clients at different payment stages, is where most founders' discipline breaks down. The first follow-up might get written carefully. By the third invoice and the second reminder cycle, the emails get short or they do not get sent at all.

The Tool: Free, Fast, and Calibrated for Founders

JustPaid.ai built a free dunning email generator specifically for this problem: justpaid.ai/tools/dunning-email-generator. As co-founders of JustPaid, we wanted something that a founder could use in 90 seconds without sounding like an enterprise billing department or a debt collector.

The generator produces emails across the full dunning sequence: a polite first reminder, a firmer second notice, a final demand before escalation. Each output is calibrated to the relationship context you provide, so a long-standing client relationship produces a different tone than a newer contract. The emails include all the operational elements that actually move payment forward: the invoice number, the outstanding amount, the original due date, and a direct payment link placeholder.

The reason this exists as a standalone free tool, separate from JustPaid's broader platform, is that we know the problem affects founders at every stage of tooling sophistication. You do not need to be running automated billing to need a better way to ask for money you are owed. The generator removes the blank page problem and the awkward phrasing problem simultaneously.

The Broader Pattern: Finance Operations Should Not Live in Your Head

The dunning problem is one instance of a larger pattern: founders doing the work of a finance function with none of the systems, templates, or infrastructure that a finance function would have.

This is where the second tool matters. JustPaid.ai maintains an open-source library of finance skills at justpaid.ai/tools/finance-skills. These are structured, reusable workflows for the financial tasks that come up repeatedly in a growing startup: revenue recognition, invoice processing, approval routing, payment reconciliation. They are designed to plug into AI-powered workflows and eliminate the need to build these processes from scratch every time a new tool enters the stack.

At AG Accounting, we use these skills in our own client workflows. They are not abstractions. They are operational templates built by people who have lived through the payment infrastructure problems of fast-growing companies, and who got tired of rebuilding the same logic repeatedly.

For founders building out their finance function, the value of open-source skills like these is the same as the value of open-source software generally: you do not have to solve a problem that has already been solved. You can adopt a working pattern, configure it to your context, and spend your energy on the edge cases rather than the fundamentals.

How This Connects to Cash Flow Reality

Across the clients we work with, late payments are almost never random. They cluster around the same friction points. Invoices that went out without payment terms clearly stated. Follow-up emails that were never sent because the founder assumed the client was handling it. Renewal invoices for annual contracts that looked like new charges and got flagged internally at the client for additional approval.

Most of these situations resolve quickly once someone asks directly. The problem is not client intent. It is operational friction on both sides, and founders consistently underestimate how much of that friction they can reduce by putting better systems in place before the first invoice is 30 days overdue.

A clean AR process with consistent dunning reduces your days sales outstanding, which is the average number of days between invoice and payment. For early-stage companies, DSO often runs 60 to 90 days by default, not because clients are slow but because the follow-up is inconsistent. Getting that to 30 to 45 days does not require a full-time AR function. It requires templates, a schedule, and the willingness to actually send the email.

The dunning generator and the finance skills library are not a full accounts receivable system. They are the part of the AR problem that costs the least to fix and delivers the most immediate return on a founder's time. Use the generator to eliminate the friction of writing follow-ups. Use the open-source skills if you are building out more structured financial workflows in an AI-native stack.

The money clients owe you is already yours. The only thing standing between you and it, most of the time, is one well-timed email.

If you want to talk through how this applies to your company, book a call.

Anelya Grant is the founder of AG Accounting Inc. (anelya.net), an accounting firm serving tech startups and healthcare organizations. She is also co-founder of JustPaid.ai, an AI-powered billing and contract-to-cash platform for growing companies.