@GeorgeKurdin@usemonk Great practical use-case for LLMs
A system that reasons rather than applies rigid rules
Congrats to the team on the release
Good news for businesses who want to get paid faster
LLMs need context to function
Orchestration layer seems powerful!
The average dunning email gets ignored. You are literally sending "please ignore me" messages to customers who owe you money.
Playbooks - our workflow system for intelligent collections - is now live on the @usemonk platform.
A system that reasons, not just reminds.
We filmed a 60 second video showing you an experiment between @zhou_squared and @francescocoacci collecting $100K.
Finance, biz-ops and post-sales teams should not be spending time chasing customers.
Many spend 10+hrs/week doing what Joe did in this video:
- context switching between tools (slack, gmail, quickbooks, google sheets)
- breaking flow from deep work
- sending reminders because the average dunning email is ignored
But agentic collections are not enough. Every customer relationship is different.
Some need white-glove treatment and others a nudge. Thatโs why we built playbooks, giving every business a customizable collection workflow.
With playbooks you can:
- create triggers and workflows specific to a customer segment (tone shift, conditions, escalations to sales/customer support)
- auto-resolve AP questions with context from relevant email threads
- pause automatically when product questions or upsells opportunities come up
Playbooks is how you get paid while you sleep.
And we do it with professionalism and empathy that your customers deserve.
Heading into Q1 with a gap between signed ARR and actual cash? Watch the video.
And if you want to see bloopers from Frank/Joe filming, comment โpaydayโ + tag a teammate and we will send you bloopers from the shoot.
@davidfowl When code requires clarification, I use descriptive method names to explain its unconventional behavior and underlying reasoning. This helps callers understand the code without having to reference additional documentation.
@rahulballal7@unclebobmartin@KentBeck once gave a good exercise how to practice TDD: write your production code, write your test, delete the production code, delete the test. Now your brain saw the production code and test and it will be easier to implement the deleted functionality applying TDD
@verkeerscentrum@Stad_Antwerpen de linker rijstrook is al enkele weken/maanden afgesloten (ring sportpaleis richting NL) Werken aan de weg zelden te spotten, veroorzaakt wel files. Wanneer komt dit in orde aub?