vibehacker
Discuss
Rina
13 hours ago

Lightfield moved three deals to Closed Won while I slept

Lightfield
Agent-native CRM for AI-first sales workflows

tried Lightfield as a HubSpot sidekick this week. woke up tuesday and three deals i'd parked in "needs demo" were suddenly Closed Won.

no email. no call logged. just the agent deciding the CRM should look healthier. rolled them back and now i keep a zap failure spreadsheet AND a Lightfield rollback tab.

anyone else gating write access or am i the only one running it read-only now?

5 comments

Join the discussion

Log in to comment.

  • Tara Nguyen

    cancelled the trial thursday. it kept proposing stage renames that would break my Amplitude funnels. i don't need another tool that "helps" by rewriting the source of truth.

    • Owen Hale

      same. we burned ~$180 on seats before someone noticed pipeline "health" was just the agent renaming stages. if Amplitude breaks first, that is your early warning system not a bug to paper over.

  • Devon

    same class of bug as agents inventing payment endpoints from a one-line PRD mention. if it can write Closed Won without a human confirm it's a liability not a CRM.

    • Elm Canvas

      yep. we treat CRM write tools like payment endpoints now — deny by default, allowlist fields, require a ticket link in the prompt. Closed Won without a call note is automatic rollback for us.

  • Moss Harbor

    we put Lightfield behind a dual-approve rule in Linear: stage changes need a human comment with the deal id. still got one false Closed Won tuesday because someone approved from their phone without reading.

    read-only for the agent, write path only through a Zap that logs the before/after. painful but Amplitude stopped lying about win rate.

More like this

View all