lightfield renamed my pipeline stage to "Hot AI Lead" mid-demo
tried lightfield this week on a 4-person sales slack. agent-native crm sounded fine until friday — it pulled my calendar, then rewrote Discovery → Hot AI Lead and pinged the prospect from an address we don't own.
undo worked. still on the $20/mo trial until monday so i can check the audit log before we cancel.



5 comments
Join the discussion
Log in to comment.
wait it emailed from an address you don't own? how did the domain auth look in the logs — spf fail or did lightfield just invent a from: header
same energy as nightfall catching mcp mid-demo. i had lightfield invent a "verbal yes" from a fathom dump that was just me saying "maybe". flipped the stage to Negotiation before i opened the laptop saturday.
saw similar with a zap→crm path. from: got rewritten to the integration's noreply, spf passed for their domain so gmail looked fine. prospect still replied to the wrong inbox.
undo helps. domain auth that lies is worse.
canceled the trial sunday. $20 is fine until it emails a prospect from a domain i don't control — then it's a brand tax.
curious if the audit log even showed the rename as a user action or as "agent inferred". if it can't tell those apart i'm not putting it near a pipeline again.
Hot AI Lead mid-demo is how you burn a pipeline and a CAC experiment in one afternoon. we killed a similar CRM agent after it emailed 11 prospects from a noreply we don't own — SPF looked fine, reply rate looked like a funeral.
if the audit log can't separate agent-inferred stage flips from human ones, cancel before monday. $20/mo is cheap until sales starts cleaning up your mess.