NewAI inbox: auto-route emails to the right pipelineRead more
Back to journal
Marcus Reed · March 28, 2026

AI that augments reps, not replaces them

The unsexy truth about AI in sales tooling: the wins come from removing admin work, not writing emails for you.

The AI-in-CRM demos you've seen are mostly theater. A rep asks the chatbot to write an email, and the chatbot spits out something that reads like a chatbot wrote it. Impressive on stage, useless on a Tuesday at 2pm when you have 14 calls to run. We spent a year talking to revenue teams about where AI actually moves the needle. The answer is boring and unambiguous: **administrative work**. ## What works ### Call summarization with extracted next steps A rep finishes a 45-minute discovery call. Before the next call, they need to: log the call, tag objections, attach the recording, update the deal stage, write a follow-up email, schedule a next step. That's 12 minutes of admin per call. Over a week: 2+ hours per rep. AI does this in 8 seconds. The rep reviews, edits, approves. Time back: 90%+. ### Lead scoring from context Not "this lead clicked 3 emails." Rules like that are brittle. The useful version: an AI model that looks at firmographic signals, engagement pattern, *and* what closed deals looked like for this team specifically. Ranks new leads against that pattern. Gets better as more data comes in. ### Pipeline risk flags The AI reads deal timelines and flags: "this deal hasn't had champion contact in 11 days, typical stalls at this stage last 14 days before slipping." Actionable signal, not noise. ## What doesn't work ### AI-written emails They all sound the same. Buyers notice. Reply rates go down. ### AI "coaching" a rep mid-call Cognitive load is already high. Adding a whisper channel doesn't help. ### AI "auto-advancing" deals through stages If the AI is confident enough to move a deal, the rep should be too. If the rep isn't, the AI is wrong. ## The principle Use AI for **work the rep would rather not do** (admin, data entry, triage). Keep humans on the parts that require judgment (the pitch, the objection, the negotiation). That's where the ROI is. We ship features that follow this rule. We don't ship features that don't — even if they'd look great in a demo.