Industry
AI employees for sales CRM teams
Tobiloba Odejinmi · 22 Jul 2026 · 6 min · 911 words
Direct answer
An AI employee for a sales CRM team looks up the lead, writes the first note, and flags the ones worth a call. It does not replace the CRM. I shipped Revwit so leads, deals, and follow-ups could live in one place. The employee should sit there, on the stale pile, not in a new tab your reps will ignore by Thursday.
- Work inside the CRM you already pay for. A new login is how follow-up dies.
- The job is the stale lead and the first note, not an autonomous closer.
- Measure replies, meetings, and clean fields. Do not measure messages sent.
- A person still owns the call and the discount. The employee owns the chase.
The CRM is the desk
I built Revwit because sales teams were already losing work between tabs. Leads in one place. Notes in another. Follow-up in someone's head. An AI employee that opens a fourth place is not a worker. It is a leak.
Sit in the CRM you already pay for. Read the record. Write the note. Set the next step. If a rep has to copy your output back in, you have failed the only test that matters.
The stale pile is the product
Most teams do not need a closer that never sleeps. They need someone to touch the lead that landed on Tuesday and is still sitting there on Friday. That is the job.
Look up the lead. Write the first note. Flag the ones worth a call. Leave the discount, the promise, and the awkward negotiation with a person whose name the customer can say.
- First touch on inbound that would otherwise wait.
- A note after the call that actually lands on the record.
- A nudge when a deal has gone quiet, with the last context attached.
- A clean handoff when the case is worth a human.
Activity is not a pipeline
I will not celebrate a thousand drafts. I will ask how many replies you got, how many meetings you set, and whether the next step is visible without asking the rep in Slack.
If the employee makes the CRM noisier, turn it down. Noise is how good leads hide. The whole point of a CRM is that the pile has an order. Do not spend money to destroy the order.
Do not let it invent the account
Sales files fill up with fiction when a model is told to 'enrich' without a source. I treat that the way I treat a guessed field in a credit file. If you cannot point at where the fact came from, it does not go on the record.
At Zeeh, boring APIs won because the data was something another system could trust. Your CRM deserves the same respect. Invented job titles are not enrichment. They are future embarrassment on a call.
Handover has to keep the thread
When the employee flags a lead, the rep should see the original message, the attempts, and why it was flagged. If they have to reconstruct the story, you have only moved the work.
This is the same rule I use in support and clinic ops. Escalation that loses context is not escalation. It is a fresh start the customer did not ask for.
One process, inside the tool you have
Pick the follow-up that slips most often. Map it. Connect to the CRM. Go live in a week with a write-up the sales lead can follow. Measure first-touch and meetings.
If there is nothing worth automating, I will say so on a thirty-minute call. Some teams do not have a pile. They have a pricing problem. A model will not fix that.
What I would not let it do
I would not let it change a price. I would not let it promise a date the warehouse cannot keep. I would not let it mark a deal won because the thread felt warm. Those are how you train a company to lie to itself.
Draft the follow-up. Clean the fields you can point at. Flag the quiet deal. Then stop. A sales lead who cannot say why the pipeline moved is in the same spot as a credit officer who cannot replay a file. I have sat in both rooms. The meeting goes the same way.
Start with one process inside the CRM you already have. Live in a week. Measure meetings, not messages. That is the whole job.
Questions people ask
Should we switch CRMs to get an AI employee?
No. I plug into what you already use. The point is to take work off the team, not add another tab. If the CRM is the problem, say that. Do not hide it inside a model.
What is Revwit?
A sales CRM I shipped so leads, deals, and follow-ups stay in one place. The employee I would put on a team like that does the first pass in that same place.
Can it send email without a person?
It can draft. For anything that can create a promise or a price, a person clicks. Silent outbound is how you inherit a thread you cannot defend.
What should we automate first?
The follow-up that already slipped. The lead that landed and waited. The note nobody wrote after the call. That pile has a shape. 'AI selling' does not.
How do we know it is working?
Time-to-first-touch, meetings set, and fields that stay complete. If the only number that moved is 'AI messages', you bought activity, not a pipeline.
Written by
Tobiloba Odejinmi
Head of Engineering at 10mg Health. I have run engineering at Zeeh Africa and sold Insurpass and Shopl. I still write the code. If you have one process that still runs on people copying things, we can look at it in thirty minutes.
