Should an AI agent update my CRM and track client payments?
Short answer
Yes, but have it propose changes before it writes them. When we checked my inbox for leads, only 3 of 35 candidates were real, so my agent now asks in a DM before adding anyone. For payments, it reads Stripe, sees who's on autopay and on what date, and tells me the day after a payment is missed.
I'm losing so many people because I don't know where to put them. An AI agent I can just brain dump to, that then does what it's supposed to do, works better for me than one more dashboard.
How should the agent update records?
By restating the change and asking yes or no. I say what I want. The agent writes back: here's what I'm going to do. I'm going to change this status, mark this date, and here's the comment I'm going to put in the note for this company. Are you good with this? I say yes, and it does it.
That keeps the speed of just talking, with a quick check before anything gets written.
Should it add new leads automatically?
That's what I wanted at first. Have the agent read my email and call transcripts, add people to the list without asking, and just tell me. If I disagreed, I'd say so and it would remove them. I needed to lower the friction for me.
Then we looked at the actual emails.
"There were only 3 out of 35 that were actual leads."
A bunch were current customers, which is fine. Plenty were just friends reaching out to get on a call. With numbers like that, auto-adding makes a mess. Now the agent sends me a DM: I found this email from this person, it looks like a lead for this, do you want me to add it?
Should sales and clients live in the same CRM?
I'm separating them. The service CRM holds clients. Outreach is its own thing, and it should be really simple: a cold list of people from bought lists, cold emails and LinkedIn. Someone moves into the main CRM for hot leads only when they get warm and could actually close.
Can an agent chase late payments?
Yes, and that kind of thing would be very, very helpful. What I'd love is a message like: I believe this client's payment is usually due on the 7th. It's the 8th and it didn't go through. Do you want me to send them an email?
The key is not hard-coding anything. I don't want to set up a new plan by hand every time I add a client. The agent should read Stripe, see who's on autopay and what date they're supposed to pay, and notify me the next day if they don't. No grace period. Just fire when it's due.
Scope it on purpose. This is only for consulting clients. The cheap software subscriptions and one-off sales don't need to be in there. For those clients, the CRM should mirror Stripe: when they paid, when they're due, what they pay each month.
What's the bigger lesson?
Get one agent working before you add more. After about three months of agent setup with little to show for it, I paused five other agents so I could get real value out of one first. Three months of effort with that little to show is nuts. The answer was to narrow down, not to add more agents.
Answered by TJ Larkin. From Local Media HQ podcast conversations, client and partner calls, and my own AI chats, 2025-2026. Last updated .