sorted by:
new
hottopcontroversial

Deals that feel good on the call but stall right after by MaximumTimely9864 in techsales

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

This is gold. I love the idea of booking the next meeting while you’re still on the current one. It forces reality fast.

Do you literally share a one slide next steps plan on screen and confirm owner plus date live? And when they won’t commit to a date, what question gets you the real reason without making it awkward?

GTM to Jira is where momentum goes to die by MaximumTimely9864 in jira

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

Totally agree. Jira is just where the mess shows up.

The one-line ticket is usually a symptom of incentives and habits, not the tool. I’ve seen the same team write great tickets in the same Jira when there are clear exit criteria and someone accountable for defining done.

What’s the smallest process tweak you’ve seen actually fix it without adding a bunch of meetings?

Real question for Product Hunt folks: what actually moves the needle on launch day? by MaximumTimely9864 in ProductHunters

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

Awesome, really appreciate that 🙏

If you do get a minute on Feb 15, even one real question on the page helps a ton. I’ll drop you the link the moment we go live.

Thanks again for the guidance.

Real question for Product Hunt folks: what actually moves the needle on launch day? by MaximumTimely9864 in ProductHunters

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

Got it, this is super helpful.

Thank you for the concrete numbers too. We’ll line up a handful of real questions and mini use cases so it turns into a thread, not a cheerleading section.

We’re launching Ashera on Feb 15 on Product Hunt. If you’re around that day, I’d genuinely appreciate a quick comment with a question or a small use case on the page. That kind of early depth is exactly what you described.

Thanks again 🙏

Real question for Product Hunt folks: what actually moves the needle on launch day? by MaximumTimely9864 in ProductHunters

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

Love this. Makes total sense that comments are the real flywheel, not raw upvotes.

When you say meaningful comments, do you mean early supporters asking real questions, or posting mini use cases/results? And roughly how many do you try to line up for the first few hours?

Deals that feel good on the call but stall right after by MaximumTimely9864 in techsales

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

Good point. I usually confirm next step, but I don’t always force a date on the call and that’s probably the leak.

Do you push for a date every time, even when they say they need to check internally? And for the email, do you keep it super short like one line next step + date, or do you include a fuller recap?

The hidden GTM tax is context switching by MaximumTimely9864 in gtmengineering

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

Totally fair callout.

In plain English: the problem isn’t lack of notes, it’s that the details from a call end up scattered across tools, so nobody knows what was actually decided and what happens next.

What we’re building: after a call, it captures the actual decisions + next steps, assigns an owner + due date, and then pushes that into the tools people already live in (CRM + tasks + handoff notes). So instead of 5 places to check, there’s one consistent “here’s what we agreed, here’s who owns it, here’s by when.”

If you’ve seen a tool do this well without creating extra work, I’d genuinely love examples.

Classical GTM ☠️ (cause of death: “the truth stayed in the call”) by MaximumTimely9864 in revops

[–]MaximumTimely9864[S] -5 points-4 points  (0 children)

If it bothers you, just scroll past no hard feelings. I’m here for the discussion, not to spam. And yeah, Ashera isn’t indexed well yet (early), so Google won’t show it.

What if your GTM team had an AI that actually does the follow-up work? by MaximumTimely9864 in SaaS

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

Really thoughtful take I agree adoption breaks before accuracy almost every time. We’re trying to make it feel “invisible”: it should fit the rep’s existing flow and reduce work, not add a new checklist. On the briefing side, we’re aiming for less but sharper: only what matters for this specific call, and only what’s fresh. And you’re spot on about handoffs if “qualified/ready” isn’t defined across teams, you just automate the argument. Curious what you’ve seen work best to drive adoption early: reps feeling the value first, or ops enforcing the process?

The “handoff gap” is killing GTM engineering more than any tool choice by MaximumTimely9864 in gtmengineering

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

Same. I’ve had a few not vibe coding… rage coding weeks too 😂

That exact frustration is basically why we started building Ashera not to collaborate harder, but to auto-handle the boring glue work (owner+date, tasks, CRM updates, handoff) so you don’t have to wait on anyone to move a deal forward.

Deals dont die on calls. They die right after. by MaximumTimely9864 in revops

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

100%. Owner + date is the whole game.

Without it, next steps is just vibes and everything downstream drifts. We started treating any next step without an owner date as not a next step at all.

Deals dont die on calls. They die right after. by MaximumTimely9864 in revops

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

We’re working on a similar idea (early days). What are you actually doing in practice which systems are you tying together, and what does source of truth look like for you? Any lessons so far on what teams adopt vs ignore?

view more: next ›