MCP-first invoicing for freelancers. Tell your AI what you did, and the badger writes the invoice, tallies your hours and badgers clients to pay, while you get on with the work.
No reviews yetBe the first to leave a review for Invoice Badger
Maker
📌
Hey, I'm a freelancer and I hated that invoicing tools make you stop working, open a tab, and fill in a form for stuff you already know. So I built InvoiceBadger around MCP: I connect it to Claude and just say "log 90 mins on Acme for the API fixes" and it's on the invoice at the right rate. There's a simple dashboard too for when I'd rather click.
I know invoicing through an AI agent isn't a new idea, and I wasn't trying to do anything clever. I just wanted invoicing that's genuinely simple and that I didn't have to spend an afternoon setting up. You add a client with their rate, and you're invoicing. That's the whole thing.
Free to start, Pro's a fiver a month. I'd genuinely love feedback, especially on the connect-your-agent flow. Roadmap's public at invoicebadger.com/roadmap
Report
@dalemooney Really like the practical approach here. I gave it an upvote because removing friction from invoicing is something freelancers appreciate every day. One question I had is how does the MCP integration handle confirmation before an AI agent creates or updates an invoice to prevent accidental entries?
Report
Maker
@spotch_founder Thanks, really appreciate the upvote and the question!
It's handled in two layers. First, the MCP client itself does the confirming. In Claude, every action shows up for you to approve before it runs, so the agent never silently writes anything. You see "log 2 hours on Acme for the API fixes" and OK it, the same way you'd approve any tool call.
Second, InvoiceBadger is built so a mistake is never high-stakes. Every invoice starts as a draft, lines get added to that draft, and nothing reaches your client until you deliberately share the link. If the AI misreads something you just edit or delete the line, or bin the whole draft. And once an invoice is marked sent or paid it locks, so a finished one can't be changed by accident without you setting it back to draft first.
So the client asks before acting, and the tool keeps everything reversible until you choose to send. Genuinely good question though, and tightening the server-side guardrails further is exactly the kind of thing I want to keep doing as more people wire agents up to it. Happy to go deeper on any of it!
Report
Honestly the MCP approach is clever, I told it about a client call and it pulled together the hours and a follow up nudge without me touching anything. Would love a bit more control over the email tone though.
Report
Maker
@corbin_yeo Love that it clicked, that's exactly the feeling I was going for.
One honest note on the follow-up: right now that email is your AI drafting it in the chat from the invoice data, rather than InvoiceBadger sending it itself. Which is actually good news for your question, because it means you already have full control over the tone. Just tell it "keep this friendly" or "make it a bit firmer" and it rewrites on the spot.
Automatic sending of those chases, with a proper tone setting baked in (friendly, neutral, or firm), is the next big thing on my roadmap. So it's really useful to hear that tone control is what you'd want. Noted, and building toward it!
Report
Love the MCP angle, this feels like how invoicing should actually work now. One thing that would make it stick for me: a quick weekly summary the AI can send me showing unbilled hours across clients so nothing slips through before month end.
Report
Maker
@ladygaga "Before month end" is exactly when stuff slips, so I completely get why you'd want this. Right now you can ask it to pull your open drafts across all your clients, but an unprompted weekly "here's your unbilled time" is a much nicer version, and honestly might be the next thing I build. Cheers for the nudge.
Report
Love the MCP angle, this feels like where invoicing is headed. One thing I'd love to see is a built-in way to set up recurring invoices through a simple chat prompt, like "bill Acme Corp $2k on the first of every month" and the badger just handles it. Would save me from having to manually schedule anything.
Report
Maker
@valerie_spencer Recurring and retainers are already on my list, and you've basically written the spec for how it should feel, just say "bill Acme 2k on the first" and it's handled, no scheduling faff. That's the whole reason for doing this chat-first. Really looking forward to shipping it!
@dalemooney Really like the practical approach here. I gave it an upvote because removing friction from invoicing is something freelancers appreciate every day. One question I had is how does the MCP integration handle confirmation before an AI agent creates or updates an invoice to prevent accidental entries?
@spotch_founder Thanks, really appreciate the upvote and the question!
It's handled in two layers. First, the MCP client itself does the confirming. In Claude, every action shows up for you to approve before it runs, so the agent never silently writes anything. You see "log 2 hours on Acme for the API fixes" and OK it, the same way you'd approve any tool call.
Second, InvoiceBadger is built so a mistake is never high-stakes. Every invoice starts as a draft, lines get added to that draft, and nothing reaches your client until you deliberately share the link. If the AI misreads something you just edit or delete the line, or bin the whole draft. And once an invoice is marked sent or paid it locks, so a finished one can't be changed by accident without you setting it back to draft first.
So the client asks before acting, and the tool keeps everything reversible until you choose to send. Genuinely good question though, and tightening the server-side guardrails further is exactly the kind of thing I want to keep doing as more people wire agents up to it. Happy to go deeper on any of it!
Honestly the MCP approach is clever, I told it about a client call and it pulled together the hours and a follow up nudge without me touching anything. Would love a bit more control over the email tone though.
@corbin_yeo Love that it clicked, that's exactly the feeling I was going for.
One honest note on the follow-up: right now that email is your AI drafting it in the chat from the invoice data, rather than InvoiceBadger sending it itself. Which is actually good news for your question, because it means you already have full control over the tone. Just tell it "keep this friendly" or "make it a bit firmer" and it rewrites on the spot.
Automatic sending of those chases, with a proper tone setting baked in (friendly, neutral, or firm), is the next big thing on my roadmap. So it's really useful to hear that tone control is what you'd want. Noted, and building toward it!
Love the MCP angle, this feels like how invoicing should actually work now. One thing that would make it stick for me: a quick weekly summary the AI can send me showing unbilled hours across clients so nothing slips through before month end.
@ladygaga "Before month end" is exactly when stuff slips, so I completely get why you'd want this. Right now you can ask it to pull your open drafts across all your clients, but an unprompted weekly "here's your unbilled time" is a much nicer version, and honestly might be the next thing I build. Cheers for the nudge.
Love the MCP angle, this feels like where invoicing is headed. One thing I'd love to see is a built-in way to set up recurring invoices through a simple chat prompt, like "bill Acme Corp $2k on the first of every month" and the badger just handles it. Would save me from having to manually schedule anything.
@valerie_spencer Recurring and retainers are already on my list, and you've basically written the spec for how it should feel, just say "bill Acme 2k on the first" and it's handled, no scheduling faff. That's the whole reason for doing this chat-first. Really looking forward to shipping it!