A services company was writing every renewal reminder and chasing overdue invoices by hand. We built a workflow that drafts and sends that follow up from the dates already in its systems, and it returned 25 hours a week of manual follow up to the team.
This is how it works, and how to spot the same kind of work on your own team.
Where they started
Every renewal reminder was written and sent by hand, and overdue invoices were chased whenever someone had time, so some slipped through.
The work itself was routine. The trouble was that every reminder depended on someone remembering a date while the rest of the week competed for the same hours.
What we built
We built the follow up around the CRM and email tools the team already used.
- Sequences tied to each customer’s own dates. Renewal and overdue emails start from each customer’s dates, so every customer gets the right message at the right moment without anyone setting a reminder.
- Reminders that stop the moment a payment lands. Nobody gets chased for an invoice they already paid.
- An admin page the team controls. The team edits the content and the timing themselves, without waiting on a developer.
- A log of every message. Anyone on the team can see what went out, to whom and when.
The workflow runs every day. The team reviews the results with us each month and adjusts content or timing from the admin page.
What changed
The team got 25 hours a week of manual follow up back.
In the first 43 days, $100K in overdue and upcoming invoices was recovered or put back into active follow up.
The workflow is live in production and still running.
Why this was the right first workflow
A good first workflow is frequent, a little dull and easy to measure, and follow up tied to a date is all three.
- The trigger already exists. A renewal date or an invoice due date sits in a system you already pay for, so nothing has to be invented to start the work.
- The right message is known. Your team already writes these emails. The workflow drafts what they would have written, at the moment they would have written it.
- The before and after are countable. You can count how long the follow up took last month and how often it slipped, so you can tell whether the hours came back.
Where the same pattern shows up
Most teams have follow up tied to a date. A few examples:
- Property management: lease renewal offers, owner updates and late rent reminders. The workflow drafts and your team approves, and AI stays out of tenant screening and ad targeting, which the Fair Housing Act governs.
- Home services: maintenance agreement renewals, seasonal tune up reminders and overdue invoices. Calls and texts go only to customers who agreed to receive them, as the TCPA requires.
- Professional services: contract renewals, retainer top ups and unpaid invoices.
Your team approves anything a customer sees or anything that moves money until it decides a step can run on its own.
Find yours
For one week, write down every message your team sends because a date came up: a renewal, a reminder, an invoice that went past due. Note who sends it, how long it takes and how often it slips.
Bring that list to a working session. It is free and takes about an hour, and we will look at real cases with the person who does the work most. You leave with written notes and a shortlist of what to build first, and you keep both whether or not we work together.
Questions people ask
Does the workflow send emails without anyone checking?Only once your team decides it should. At first, your team approves each message, and it can let routine reminders run on their own once the drafts are consistently right while keeping approval on anything unusual.
Do we need new software?No. We build inside the CRM, billing and email tools your team already pays for, and you own everything we build.
What happens when a customer pays?Reminders stop as soon as the payment is recorded, so nobody is chased for an invoice they already settled.
Is our customer data used to train AI models?No. Each workflow gets only the access it needs, and your data stays out of model training.