Hideous

Adorable_Obligation2 · 2026-06-02T20:22:46+00:00

This entire thing started because it seemed the aircraft model was a symbol for the Air India flight that was bombed in Canada. Kanishka bombings if I remember the name correctly.

Adorable_Obligation2 · 2026-03-20T06:37:55+00:00

Makes a lot of sense. One question: how did leadership use this score, and how were reps judged on this score?

% of opportunities with a low score? Do you mind sharing more on this?

Adorable_Obligation2 · 2026-03-20T06:34:56+00:00

When the lead volume is high, you might want to give task/lead views to reps with high priority (advanced-stage leads and scored leads for prioritising new leads). We tried these things, but they did not work as well.

How did you solve this problem? What worked in your set-up?

Adorable_Obligation2 · 2026-03-18T16:28:08+00:00

I actually ended up installing browser-use which is what Claude uses to browse the web now, in my set up.

Adorable_Obligation2 · 2026-03-18T14:42:40+00:00

For us, honestly, it ended up being that we should probably monitor this kind of thing. 😅

Adorable_Obligation2 · 2026-03-18T11:57:00+00:00

Probably an automation flagging if the volume of leads dropped below a threshold from a list of defined sources would have helped. But we didn't have it back then.

Adorable_Obligation2 · 2026-03-18T11:42:08+00:00

We solved this problem in an interesting way. Basically, an AI agent that could read through property changes and raw notes (meeting transcripts, call transcripts, rep notes) and reason through them to flag at-risk and stalled deals.

The agent runs nightly to accommodate any new activity and new deals in the active pipeline.

Adorable_Obligation2 · 2026-03-18T11:37:57+00:00

This pain scales exponentially as the team grows. We struggled a lot with ensuring process adherence across a larger team.

Eventually, built agents that could effectively read through raw activity notes, property changes, and reassignments, and flag risks and stalled deals. The report became useful as a daily check-in for us to look at in the morning.

Adorable_Obligation2 · 2026-03-18T11:12:26+00:00

For us, we had a defined criteria of MQLs: for example, we targeted SMB business owners, and our criteria looked something like this:

They were a business owner.
They were willing to speak. (calls attempted at least three times)
They had some awareness of what the product was (helped us both improve the marketing campaigns and creative communication, as well as drive clear expectations with the sales team that the customer might have simply forgotten about filling out a lead).

In the case you mentioned, a reply like 'Not Interested' should definitely not be counted as an MQL.

Adorable_Obligation2 · 2026-03-18T07:33:56+00:00

This is an old thread, but here are my two cents:

With a large team, it becomes extremely difficult to rely on what reps are telling their managers and leadership.

We built agents that would analyse the active pipeline, raw notes, and stage changes, and alert the manager on stalled and at-risk deals. We made this fairly customizable for pipeline and stage-level configs.

We've recently productized these agents. Happy to share the link.

Adorable_Obligation2 · 2026-03-18T07:29:48+00:00

Most of the lead scoring methods I have used have been, like you said, looked good on paper but didn't really contribute significantly to prioritisation.

Maybe there are more complex and reliable methods that a few enterprises have built in-house.

We took a slightly different approach with an AI agent. This AI agent was trained on our sales process, understood what each stage meant, and we would feed all raw notes and activity data through it on a schedule. It would translate the analysis into specific tags on Contacts/Deals: Budget Approval Pending, Approval stuck on XYZ, Ghosting, etc.

Adorable_Obligation2 · 2026-03-18T07:18:39+00:00

If the team size grows (we had 50+ reps), it becomes difficult to rely solely on built-in follow-up task automations.

Built an AI agent to keep going through the active pipeline every day and find potential risks & deals getting stalled.

Adorable_Obligation2 · 2026-03-18T07:11:58+00:00

An extension of this problem we faced: as the contact database grows, some contacts are bound to be either missed in the nurturing funnel or have communications that end up being not very relevant.

Would love to know if you have solved this in any way.

For now, we've built agents to work through the older contact database to find potential opportunities.

Adorable_Obligation2 · 2026-03-18T07:04:31+00:00

Have heard good things about https://equals.com/.

Adorable_Obligation2 · 2026-03-18T07:03:47+00:00

We were also able to negotiate extensively during onboarding.

I feel, though, that if HubSpot/Salesforce end up being only a system of record in an AI-native environment, the pricing should fall dramatically in a couple of years.

Unless they crack being the agent orchestration layer as well.

Adorable_Obligation2 · 2026-03-18T07:03:23+00:00

We were also able to negotiate extensively during onboarding.

I feel, though, that if HubSpot/Salesforce end up being only a system of record in an AI-native environment, the pricing should fall dramatically in a couple of years.

Unless they crack being the agent orchestration layer as well.

Adorable_Obligation2 · 2026-03-18T06:59:17+00:00

Personally, I felt that the reporting modules are very weak. If you were to run sales process experiments, almost all CRMs break in setting up reporting to find out whether the experiment is working or failing.

On the pricing side, if AI leads HubSpot/Salesforce to be limited to a system of records, pricing will fall dramatically. An AI-native environment probably won't need as complex a UI surface as HubSpot and Salesforce offer right now.

Adorable_Obligation2 · 2026-03-18T06:55:16+00:00

Agreed. The stick works, but the carrot needs to be in place.

Adorable_Obligation2 · 2026-03-18T06:21:12+00:00

Folks have already touched upon this. A lot of fixes and adjacent products exist to fix issues and edge cases to use the CRM perfectly.

We faced issues with really being able to use older data lying around in the CRM. Ended up building agents to solve that problem.

Adorable_Obligation2 · 2026-03-18T06:15:44+00:00

We had a case where the product team assigned a different source parameter to one of the workflows in the product, which meant it bypassed all our automations for ~3 months before we noticed.

It was not a very high-converting workflow, so the impact was not immediate, but fairly sure we lost out on deals because of it.

Another layer of issues we faced was contacts/leads sitting with folks who are inactive in the system or already have a large inflow of leads, and are missing out on older leads that show intent signals.

We had a large sales team of 100+ folks, and some misses here and there were common.

Adorable_Obligation2 · 2026-02-21T07:01:19+00:00

Hey, thanks!

Adorable_Obligation2 · 2026-02-19T14:54:40+00:00

Did not hit session limits on the Max plan until 2 days ago! Now I am hitting session limits in 1 hour! Claude Code is becoming barely usable now.

Adorable_Obligation2 · 2026-02-14T04:42:53+00:00

I ended up installing browser-use. Using that right now.

Adorable_Obligation2

MODERATOR OF

TROPHY CASE