The Invoice Nobody Chased
Your CSM delivered the work, the contract is signed, and a $48K invoice has been sitting at day 67. Collections is a function. You never staffed it.

Open your accounting tool. Open the aging report. Look at the column labeled 60+ days. You probably have three to seven invoices sitting there, totaling somewhere between forty and two hundred thousand dollars of cash you have already earned.
You know who those customers are. They are not in dispute. The work shipped. The contract is countersigned. Two of them you sent a polite Slack message about three weeks ago. One of them your finance contractor said she would chase last Friday. The other four are open in a tab in your head.
This is the collections function at most Series A companies. It is not a team. It is a founder, a finance contractor who works eight hours a week, and a QuickBooks tab nobody opens between board meetings.
The aging report nobody reads
Pull up your last six months of accounts receivable. The numbers usually look like this. Current and 0 to 30 days are healthy because invoices fresh off the contract get paid by AP teams running their own clock. 30 to 60 starts to drift. 60 to 90 is where the cash leak begins. 90+ is where you start writing things off that you should have collected.
The typical Series A company with two to four million in ARR carries somewhere between fifty and two hundred fifty thousand in receivables past 45 days, on any given day. DSO drifts from a healthy 38 days to a sloppy 62 days over a year and nobody notices until the next cash forecast meeting.
That is not a tooling problem. The tooling is fine. QuickBooks, Xero, NetSuite, Stripe Invoicing, all of them produce the aging report on demand. The problem is that nobody is paid to act on the aging report on Monday morning. The founder is selling, the CSM is delivering, the finance contractor is reconciling. Collections is the work that sits between three roles, owned by none of them.
Why hiring an AR clerk is not the answer
The textbook answer is to hire an AR specialist. Loaded cost in the US lands between sixty and ninety thousand a year, lower in offshore markets. They send the dunning emails, they make the phone calls, they reconcile the partial payments.
At Series A volume, that hire is overpriced for the actual workload. You have maybe forty to eighty invoices a month. Half of them get paid on the standard 30-day clock without anyone touching them. The other half need one to three nudges, a phone call to AP at the customer, and a re-send of the W-9 because somebody at the customer changed vendor management software again.
That is not eight hours a day of work. That is ninety minutes a day of work, spread across the month, that happens to need to be done every day. A full-time hire eats the budget and then spends most afternoons looking for something to do. A finance contractor at four to eight hours a week misses the rhythm and the cash sits.
What you want is the function, on the right cadence, without paying for the seat. That is the shape an AI Ops Department takes for AR.
What a fractional AI collections function does
Take the aging report, the contract, the customer's AP contact, and the email thread history. Hand all of it to an agent that runs every weekday morning. The agent does the work an AR specialist would do, on the cadence the cash needs.
Daily aging pass. Every morning the agent pulls the current aging report, flags every invoice that crossed a threshold overnight, and queues the right action. 30 days gets a first nudge. 45 days gets a second nudge plus a CC to the AP contact. 60 days gets a calibrated escalation email to the original buyer with the contract attached.
Drafted dunning, not templated dunning. Each nudge is written in the voice of the account owner, references the specific deliverable, and quotes the exact net terms from the signed contract. AP teams respond to invoices that read like a human wrote them. Form letters get archived.
Payment friction removal. When AP replies with "we never received the invoice" or "we need an updated W-9" or "can you re-send with our new PO number," the agent handles the re-send, the form, and the resubmission. The CSM never sees the thread.
Partial-payment reconciliation. When a customer pays $11,200 against a $12,000 invoice because of a tax detail or a credit memo, the agent matches the payment, opens the variance, and either resolves it or queues a one-line question for the finance contractor to confirm.
Escalation only when warranted. If an invoice crosses 75 days with no AP engagement, the agent flags it to the account owner with the full thread, the payment history, and a suggested next step. You get one Slack message per real escalation, not a noisy daily digest.

The DSO math, with real ranges
Run the math on your own numbers and the case writes itself.
Cut DSO from 58 days to 42 days on a two-million ARR book. That is sixteen days of revenue moved from the receivables column to the bank column. On a smooth revenue curve that lands around eighty-seven thousand in cash pulled forward, permanently. On a lumpier book with quarterly enterprise invoices, the swing can run higher.
Now layer in the write-off avoidance. Most Series A companies write off between half a percent and one and a half percent of annual revenue in collections that aged past 120 days. On two million ARR that is ten to thirty thousand a year, gone. A function that touches every invoice on day 30, 45, and 60 catches almost all of it before it ages out.
Add the time you and your CSMs spend on collections that you never tracked. Two founders and one CSM each spending forty-five minutes a week on AR threads lands at over a hundred hours of executive time a year. Not the most valuable hundred hours in the company.
Total annual value sits in the high five figures to low six figures of cash plus reclaimed time, against a sprint cost in the low to mid five figures and ongoing cost closer to a single senior contractor than a full hire. The same shape we wrote about for reporting on Sunday nights applies here. Function, not headcount.
What changes after the sprint
Picture the same Monday morning, fourteen days after the 14-day sprint goes live.
You open Slack at 9 AM. The collections summary is already posted. Eleven invoices in active follow-up across three aging buckets. Two escalations that need your eyes, both with the full thread and a one-line recommendation. One partial-payment reconciliation that needs your finance contractor to confirm a $340 credit memo. DSO sits at 44 days, down from 61 four weeks ago.
You have not opened the aging report yourself this week. You have not sent a polite Slack message to a customer's CFO. The invoice that has been on your mind since the last board meeting closed on Thursday. The CSM is back in delivery. The finance contractor is back in reconciliation. Collections is happening because there is a function that owns it, on the cadence the cash needs.
If your aging report is sitting at 60+ with cash you have already earned, the fix is fourteen days away. After that, the only AR work that lands on your desk is the part that needs your signature.
2026-05-27The 6-Hour Sunday
Your COO is spending six hours every Sunday stitching Stripe, HubSpot, and Notion into a board update. That is a function, not a side quest. Here is what to do about it.
2026-06-01The Recruiter You Keep Not Hiring
Your founder runs every interview loop, every sourcing pass, every offer call. That is a hiring function. You never staffed it. A 14-day sprint does.
2026-06-01The 11 PM Support Queue
Your founder is closing tickets at 11 PM because nobody else owns the support function. That is a staffing decision you never made. Fix it in a sprint.