Invoicing is one of those things that sounds simple until you're actually doing it every month. For me the worst parts have always been:
Writing follow-up emails for overdue invoices and trying to figure out the right tone
Context switching from actual client work into "accountant mode" just to send a bill
Clients asking "can you resend that invoice?" because they lost it in their inbox
Manually creating invoices every time I needed to send one to a client. It seemed like every time was the first time.
I'm building something in this space right now and I want to make sure I'm solving real problems, not just my own. So freelancers, agency owners, small business operators what's the one part of your invoicing workflow that drives you crazy? The thing you wish just handled itself?
How does Maven handle tone when chasing invoices that are 60+ days overdue versus just a few days late? That escalation nuance is what usually trips me up. Congrats on launching!
@mcarmonasΒ
Great question β this is something I put a lot of thought into because getting the tone wrong on a follow-up can damage a client relationship fast.
Maven uses a 4-tier tone escalation system: friendly β professional β firm β urgent. The tone is selected automatically based on how many days overdue the invoice is, plus a bonus that factors in how many follow-ups you've already sent.
A few days late? Maven assumes it's an oversight β warm, casual, "just wanted to make sure this didn't slip through the cracks" energy.
60+ days overdue? It shifts to urgent β direct, serious, "this requires your immediate attention" language. If a late fee has been applied, it mentions that too.
The smart part is the escalation bonus β if you've already sent 3 follow-ups on a 2-week-old invoice, Maven won't keep sending the same gentle nudge. Each previous follow-up adds weight, so the tone escalates naturally even if the invoice isn't ancient yet.
A few guardrails built in:
Maven never threatens legal action β that's a hard rule
Every email is capped at 150 words so it stays concise
It pulls in the customer's payment history (like their avg days to pay) to personalize the message β so a usually-reliable client who's late for the first time gets a softer touch than a repeat offender
If the customer's email has bounced, Maven skips them entirely instead of wasting your AI queries
You always get to preview and edit the draft before it sends, so you stay in control.