What if unused seats caused a true-up they didn't expect?

Name the seat math in one sentence and offer a credit path if that's policy, or a later date if it isn't. Don't lecture them about contracts. Founders will fight a surprise true-up while they still own CS. Help them explain it. That's how you get paid without a war.

Should I copy a bookkeeper and the founder together?

If they have a bookkeeper and that's already how this account pays, yes, with a short factual note. If the founder was your only contact, ask who owns AP rather than surprise-adding an email you found on the website. Completeness is good. Ambush CCs are how relationships cool.

Can I pause the sandbox while an invoice is overdue?

Only if the contract says so and you've warned them in writing with a date, especially around the ship week and the bill. Cutting access as a surprise punishment during a failed-card week is how you lose the reference. Warn, date, and still offer to fix the card the same day. Warm and firm can live together.

What belongs in the second reminder to a founder?

The same facts, plus what you already offered to fix, plus a date you'll assume they need a later run unless they say otherwise. Don't add new commercial terms. Don't add emotion. One extra line asking if the card failed is plenty. Then wait.

Is a phone call better than a third invoice email?

If you already have a working voice relationship, a short call that names the invoice ID is kinder, especially around the ship week and the bill. Voicemail should still carry the facts. Don't recap the product. Don't threaten. Ask whether it's the card, seat coding, or a later date, then get off the phone.

Last updated 2026-09-02 · Reviewed by Sales Email Template editors

SaaS · Founder · After Invoice

Follow-Up Email After Invoicing a SaaS Founder

A follow-up after an invoice to a SaaS founder should make payment simple and keep dignity on both sides. Money is already on the table. Put the number, due date, invoice ID, and pay path up front. Assume a failed card, seat coding miss, or runway timing before you assume a snub.

Copy-ready template

Subject

Invoice [Invoice ID]: card, seats, or a new date?

Body

Hi [First Name],

Invoice [Invoice ID] for [Amount] was due [Due Date]. Sharing it in case the card failed or it sat in a billing tab: [Seat Count] seats on [Plan], pay path [Link].

If it's waiting on a new card, a coding change, or a true-up on unused seats, tell me what's missing and I'll fix the backup the same day. If you need a later date, a one-word later is enough.

[Your Name]
[Your Title]

Why this follow-up works

The subject is a commercial question, not a scold, so it survives a forward to a bookkeeper.
Facts sit in the first screen, which is how busy founders actually pay things.
You guess a card or seat-coding stall instead of implying they skipped you.
Same-day fix language makes you a partner to billing, not a collector, especially around the ship week and the bill.
One-word later keeps dignity if runway simply moved the date.

When should I send this to a SaaS Founder?

A polite reminder a few days after the due date, then a firmer operational note if the card still hasn't moved. Don't remind them the morning you sent the invoice, especially around the ship week and the bill. Don't stack daily notes into a ship week. If they named a fundraise, wait until the morning after. Escalate only after a fair chance, and do it with facts, not heat. Avoid Monday ship hour. A midweek morning note is more likely to get a new card. After two operational notes, a single close-the-loop question is enough, especially around the ship week and the bill. Then pick up the phone only if that's already how you work with them, especially around the ship week and the bill.

What this Founder actually cares about

This founder often is AP. They own the card and the seats that created the bill. Write so they can pay without embarrassment. They read it between a customer and a ship. The first two lines have to be the invoice, not a check-in, especially around the ship week and the bill. Don't CC an investor. Don't ping every teammate who uses the seats. Don't convert an unpaid invoice into a product upsell, especially around the ship week and the bill. Their reputation with a thin team is on the line if you make them look sloppy. Protect it. Then stop. A kind, factual note that offers to fix a card or a date is how grown-ups get paid by founders.

How SaaS changes the note

SaaS invoices to a founder stall on cards and runway, not in feelings. Unused seats got coded wrong. The card on file expired during a ship week. A bookkeeper they haven't hired still doesn't exist. Your follow-up has to sound like you have seen those tabs. Rage emails get paid last. Jokes about cash get forwarded as a problem. Put the facts up top. Offer to fix coding. Ask if they need a later date. Warmth is assuming a process issue first. The relationship is real, which is why you don't threaten, especially around the ship week and the bill. Quiet after an invoice is often a true-up fight happening in their head. They are trying to explain why billed seats don't match who activated. Help that explanation. Send the seat map. Don't send a collections script you found online. Commercial calm is how you get paid and still get invited to the next sandbox. If you invoiced wrong, say so and fix it. Don't apologize for asking to be paid when the invoice was right, especially around the ship week and the bill.

Customization tips

Use the real invoice ID, seat count, and due date. Don't paraphrase money.
If unused seats caused the true-up, say that in one line, not a lecture, especially around the ship week and the bill.
Don't CC an investor as surprise pressure.
Attach the PDF they asked for. Don't attach a new quote.
Send a few days after due, not the morning after you issued it, especially around the ship week and the bill.

Common mistakes

Threatening, guilting, or burying the amount under a relationship paragraph.
Apologizing for asking to be paid when the invoice was correct.
Upselling seats in the same note as a past-due reminder.
CCing an investor as surprise pressure.

How this scenario compares

Dimension	For this template
Best send window	A few days after due, then one firmer operational note
Ideal length	Under 90 words, facts in the first screen
Primary ask	New card, coding fix, or a later date
Unlike a proposal follow-up	Terms were accepted. You're in collections-lite, not sales.
Unlike an apology email	Only apologize if you invoiced wrong.

Questions people ask before they hit send

Assume a process issue first. Put invoice ID, amount, due date, and pay path up top, especially around the ship week and the bill. Offer to fix coding or send a new card link. Keep the tone operational. Don't CC an investor. Rage emails get paid last and remembered longest in a small company.

Related templates

Want a custom draft instead? Try the email generator. Word count on this page: 1234.