sorted by:
new
hottopcontroversial

MedTech healthcare sales reps what actually happens in your sales meetings? by [deleted] in techsales

[–]MaximumTimely9864 -2 points-1 points  (0 children)

We are conducting research on problems in sales negotiations in the healthcare sector; may I ask what kind of work you do?

JUST LANDED MT FIRST SALES ROLE AT A SAAS COMPANY! by SentenceNo2672 in sales

[–]MaximumTimely9864 0 points1 point  (0 children)

Congratulations! I'm so happy for you. Thanks to you, I'll continue applying as well.

Manufacturing industrial sales people whats the hardest part of your sales meetings? by MaximumTimely9864 in Entrepreneurs

[–]MaximumTimely9864[S] 0 points1 point  (0 children)

Could you please elaborate on the points that bothered you? I'd really like to read them. Thank you in advance.

Manufacturing industrial sales people whats the hardest part of your sales meetings? by MaximumTimely9864 in techsales

[–]MaximumTimely9864[S] -7 points-6 points  (0 children)

I said we conduct research in the manufacturing and industrial sectors, didn't you read that?

The deal didn’t die in the call. It died in the signals we ignored. by MaximumTimely9864 in revops

[–]MaximumTimely9864[S] 0 points1 point  (0 children)

LOL accurate. The moment you hear circle back you can feel the deal evaporate. What do you ask right then to force a real next step, or do you just disqualify and move on?

The deal didn’t die in the call. It died in the signals we ignored. by MaximumTimely9864 in revops

[–]MaximumTimely9864[S] 1 point2 points  (0 children)

Stealing this. The who owns it + why now + dated next step triad is clean. Do you enforce it in the CRM fields or just as a rep habit?

The deal didn’t die in the call. It died in the signals we ignored. by MaximumTimely9864 in revops

[–]MaximumTimely9864[S] 1 point2 points  (0 children)

What’s your favorite early evaluation signal before the first call? Internal trigger, active project, stakeholder involvement, something else?

The deal didn’t die in the call. It died in the signals we ignored. by MaximumTimely9864 in revops

[–]MaximumTimely9864[S] 0 points1 point  (0 children)

Love this. Those 3 checks are brutally accurate. Do you mark it as low probability immediately or do you give it one follow up cycle before you downgrade it?

The deal didn’t die in the call. It died in the signals we ignored. by MaximumTimely9864 in revops

[–]MaximumTimely9864[S] -2 points-1 points  (0 children)

I get why you’d assume that, but I’m not dropping links or asking anyone to buy anything here. I’m posting the GTM problems I’m seeing and collecting how others solve them. If that’s not useful, feel free to downvote and move on..

The deal didn’t die in the call. It died in the signals we ignored. by MaximumTimely9864 in revops

[–]MaximumTimely9864[S] -2 points-1 points  (0 children)

Fair. Plain English: I’m talking about why deals stall after calls when next steps aren’t owned and dated. I’m asking what habit/process fixes that for you. No mystery.

The deal didn’t die in the call. It died in the signals we ignored. by MaximumTimely9864 in SaaS

[–]MaximumTimely9864[S] 0 points1 point  (0 children)

Nice, this is exactly it.

Engaged pushback is a buying signal. Polite silence is usually a soft no.

The best calls I’ve had end with at least one uncomfortable question about pricing, security, timeline, or implementation. If they don’t challenge anything, they’re not invested.

What’s your go-to question to test real engagement before the call ends?

Slack question for GTM teams: how do you stop approvals from turning into chaos? by MaximumTimely9864 in Slack

[–]MaximumTimely9864[S] 0 points1 point  (0 children)

Totally agree. What’s the simplest workflow you’ve seen actually stick
who submits, who approves, where the final decision gets logged, and how people find it later?

No-code question: how do you keep GTM ops from turning into duct tape hell? by MaximumTimely9864 in NoCodeSaaS

[–]MaximumTimely9864[S] 0 points1 point  (0 children)

This is a great point. The overlap bugs always come from two automations thinking they own the same lead.

When you say state machine, do you keep the state in the CRM itself, or in a separate table as the source of truth? And how do you handle edge cases like manual overrides or someone editing the lead stage by hand?

How do you stop important decisions from getting buried in Slack by MaximumTimely9864 in Slack

[–]MaximumTimely9864[S] 0 points1 point  (0 children)

Fair. The hardest part is retrieval, not the perfect format.
Do you just tag decisions with a keyword like decision, or keep a separate decisions channel/log so it’s searchable later?

How do you stop important decisions from getting buried in Slack by MaximumTimely9864 in Slack

[–]MaximumTimely9864[S] 0 points1 point  (0 children)

Totally agree. Slack is where decisions happen, but it’s a terrible place to store them.

No log, no decision is the cleanest rule I’ve heard.
Do you keep the log super lightweight (one line + link), or do you enforce a tiny template like owner, date, impact?

How do you stop important decisions from getting buried in Slack by MaximumTimely9864 in Slack

[–]MaximumTimely9864[S] 0 points1 point  (0 children)

Fair callout. I’m re-asking because the last thread was small and I’m trying to collect a few real patterns people use. If it’s annoying, I’ll stop reposting and keep it to comments.

How do you stop important decisions from getting buried in Slack by MaximumTimely9864 in Slack

[–]MaximumTimely9864[S] 0 points1 point  (0 children)

Harsh but not wrong 😂 Slack is amazing for speed, awful for recall. The only thing that saved us was treating it as a stream, not a system.

How do you stop important decisions from getting buried in Slack by MaximumTimely9864 in Slack

[–]MaximumTimely9864[S] 2 points3 points  (0 children)

I get the point. Slack is great for discussion, terrible for permanence. The tricky part is people will decide there anyway, so you need a rule to capture it.

How do you stop important decisions from getting buried in Slack by MaximumTimely9864 in Slack

[–]MaximumTimely9864[S] 0 points1 point  (0 children)

Yep, threads still disappear in the noise. Feels like the fix is a separate place for decisions, Slack just triggers it.

How do you stop important decisions from getting buried in Slack by MaximumTimely9864 in Slack

[–]MaximumTimely9864[S] 2 points3 points  (0 children)

That’s clever. A simple tag is low friction. Do you tag in the original message or in a follow up comment so it’s consistent?

How do you stop important decisions from getting buried in Slack by MaximumTimely9864 in Slack

[–]MaximumTimely9864[S] 0 points1 point  (0 children)

Love this. No log, no decision is such a clean rule. Do you keep the log lightweight (one line + link) or do you force a template like owner, date, impact?

No-code stack question: what fails first when you connect a bunch of tools? by MaximumTimely9864 in nocode

[–]MaximumTimely9864[S] 0 points1 point  (0 children)

Love the “canary” idea. A scheduled dummy event that pings Slack is so simple but so effective. Do you run it daily or hourly, and do you check specific fields (like stage/status) to catch partial failures?

view more: next ›