Category: Uncategorized

Alright, Gary Miller here, logging in from what feels like the seventh internal meeting this week. If you’re a sales professional, you know the drill. You wake up, check your calendar, and there it is: a gauntlet of internal calls, “sync-ups,” “strategy sessions,” and “pipeline reviews” stretching out before you like an endless, grey tunnel.

They say time is money, especially in sales. Every hour you spend in a meeting is an hour you’re not talking to a customer, not building pipeline, and not closing deals. For the Average Sales Guy, this isn’t just an inconvenience; it’s a direct hit to the attainment percentage.

Take yesterday, for instance. My calendar was a beautiful, almost empty canvas for half an hour. Then, BAM! It filled up faster than a free pizza table at a sales kick-off.

First, there was the Mandatory QBR Prep Session. We had our actual Quarterly Business Review last week. This was apparently to prepare us for next quarter’s QBR. I’m pretty sure it involved a lot of slides about synergy and optimizing KPIs, none of which changed the fact that I needed to make more calls.

Then came the Weekly Team Stand-Up. Always a classic. It’s supposed to be quick. It never is. Everyone gives their updates, which invariably involve a long-winded explanation of why that one deal is still stuck in “Discovery” or how a customer almost replied to an email. I mostly just nod, occasionally unmute myself to say “green” when asked about my top deal, and pray no one asks me a specific question about my other top deal, which I forgot to update in the CRM (see last post!).

The pièce de résistance, though, was the Cross-Functional Alignment Meeting: Marketing & Product Collaboration on Q3 Initiatives. This one was a gem. Marketing presented a new campaign for a product feature that isn’t even on the roadmap yet (see that post too!). Product then countered with data on adoption rates for a feature launched three years ago that nobody uses. I tried to interject with, “Hey, can we talk about that specific integration Feature X that three customers have asked for?” I believe my comment was noted down as “Sales input: random ideas.” The meeting ended with an agreement to schedule a follow-functional deep dive. I suppressed a groan.

By the time I emerged from the digital meeting room, blinking like a mole rat hitting sunlight, half my day was gone. My call list looked accusingly at me. My pipeline was static. My brain felt like a sponge that had absorbed too much corporate jargon and not enough actual productive thought.

I get it. We need to communicate. We need to align. We need to be on the same page. But sometimes, as the Average Sales Guy, it feels like we’re spending all our time talking about selling instead of actually doing it. It’s like a chef endlessly discussing recipes and kitchen layouts instead of cooking a meal.

So, here I sit, mentally preparing for the next block of back-to-back squares on my calendar. I’ll make my coffee. I’ll try to look engaged. And I’ll dream of that glorious, elusive window of time where I can just… call a prospect. Because that’s where the real work happens.

Alright, fellow grinders, Gary Miller here. We’ve talked about weird deals, baffling roadmaps, and even that one time I got lucky. But today, let’s get into something truly universal, something that unites us all in a shared groan of existential dread: the CRM.

Ah, the Customer Relationship Management system. The supposed single source of truth. The platform that’s supposed to make our lives easier, our pipelines clearer, and our forecasts accurate. In reality, for the Average Sales Guy, it often feels less like a helpful assistant and more like a perpetually hungry beast demanding sacrifices of our time and sanity.

My CRM and I? We have a complicated relationship. It’s a love-hate thing, mostly hate. Every morning, I log in, bracing myself for the inevitable. It’s like stepping into a ring where the opponent is made of dropdown menus, mandatory fields, and a search function that seems to actively resist finding what I’m looking for.

Take, for instance, updating an opportunity. Sounds simple, right? Change the stage. Maybe tweak the close date (which, let’s be honest, is usually a wild guess anyway). Add a quick note. But no, not in my world. My CRM demands a lineage. It wants to know: “What specific activity led to this stage change? Was it a call? An email? A dream I had last night?” And then, “Please select from a list of 47 activity types, half of which seem identical, and none of which perfectly describe my actual interaction.”

And don’t even get me started on the “next steps” field. That critical little box where you’re supposed to detail what’s happening. My “next steps” often involve waiting, hoping, or maybe just sending another follow-up email that will probably go unanswered. But the CRM needs detail! So I type something vaguely professional like, “Follow up with prospect to confirm next steps post-demo” for the twelfth time. It’s not inaccurate, just… repetitive. Like my life.

Then there are the reports. The dashboards. The mystical numbers our VPs live and die by. I input my data, carefully, painstakingly, trying to make it align with reality. But then, you pull up a report, and the numbers are… different. Off. Wildly inaccurate. Did the CRM have a bad day? Did it decide to interpret “working” as “thinking about working”? It’s a mystery. A frustrating, time-consuming mystery that leads to awkward conversations during forecast calls. “Gary, why does the report say your pipeline is only $1.2M when you just told me $1.8M?” “Well, Bob, it’s because the CRM and I have different definitions of ‘qualified opportunity’ on Tuesdays.”

I know, I know. It’s supposed to be good for us. It helps track, it helps forecast, it helps us be “data-driven sales professionals.” And I believe it does, for some people. The sales killers, probably. For the Average Sales Guy, it’s mostly just another hurdle in the race to hit 70% attainment. A necessary evil. A daily battle.

So, I’ll keep fighting the good fight. I’ll keep trying to make the data align with my gut feeling. I’ll keep grumbling under my breath as I click through endless menus. Because that’s what Gary Miller does.

Alright, fellow road warriors and spreadsheet wranglers, Gary Miller here, back from the sales battlefield. And guess what? Your boy actually closed a deal last week. Yes, you read that right. A closed deal. And not just any deal – a long shot. The kind you leave in the “20% – Hail Mary” column for months, fully expecting it to eventually wither and die like an unwatered office plant.

The Long Shot Setup

This wasn’t one of those deals where I had a champion barking orders or a budget just waiting to be spent. No, this was a prospect we’d circled for ages, a big name in their industry, but consistently unresponsive. My calls went to voicemail purgatory. My emails vanished into the digital abyss. I’d sent so many LinkedIn invites, I was pretty sure their security team had flagged me as a low-level cyber threat. It felt like trying to sell ice to an Eskimo who already had a perfectly good freezer and wasn’t even answering the door.

Honestly, I was about two weeks away from marking it “Closed/Lost – Customer prefers artisanal ice, probably” and moving on.

The Unplanned Masterclass

Then, something shifted. A reply to an old email. A casual inquiry. Suddenly, they were talking. I quickly looped in Sarah, our Senior Sales Engineer. Now, Sarah is a wizard. She understands our product inside and out, can troubleshoot in her sleep, and somehow translates complex technical jargon into something even I can almost grasp.

We had a few calls. Sarah delivered a phenomenal demo. She answered every nuanced, highly technical question with grace and precision. She uncovered use cases I didn’t even know existed within their organization. She basically did all the heavy lifting, connecting dots I hadn’t even seen on the page. Meanwhile, I was mostly there for moral support, asking if anyone needed coffee, and trying not to trip over the ethernet cables.

I did my part, of course. I navigated the initial commercial questions. I did the polite follow-ups. I tried to sound confident when I was just winging it. I sent the proposal. And then, I waited. And waited. And assumed, as is tradition, that it would all go silent again.

The Pure, Unadulterated Luck

But it didn’t. One Tuesday, the contract came back. Signed. Executed. Done.

I stared at it. I refreshed my email. I stared again. It felt like winning the lottery after buying one ticket by accident. There was no intense negotiation. No last-minute feature demand (thank goodness, after last week’s debacle). Just… a contract.

My first thought? “Holy cow, how did that happen?” My second thought? “Don’t ask too many questions. Just update CRM.”

Credit Where Credit’s Due (Mostly to Sarah)

I immediately called Sarah. “It closed!” I practically shouted. Her reaction was a calm, “Oh, good. I figured that demo landed well.” And she’s right. If there was a masterclass, she taught it. She deserves a huge chunk of that commission. Seriously, Sales Engineers are the unsung heroes. They often get the stress of the technical deep dive without the glory of the direct revenue credit.

The “Win Wire” That’s Making Me Cringe

Of course, management caught wind. And now? They want a “Win Wire.”

For the uninitiated, a “Win Wire” is basically an internal press release. It’s supposed to detail the “strategic sales motions,” the “value realization discussions,” and the “innovative problem-solving” that led to the deal. It’s meant to be a learning tool, a case study for the rest of the team.

And I’m supposed to write it. Me. Gary Miller. The guy who knows, deep down, this was about 20% effort, 30% Sarah’s brilliance, and 50% sheer, unadulterated cosmic luck. How do I phrase, “I kept emailing, they eventually replied, Sarah did magic, and then they just… signed?”

I’ll figure it out. Probably sprinkle in some buzzwords, mention “proactive engagement,” and lean heavily on Sarah’s excellent technical validation. Maybe I’ll even mention “relentless follow-up,” which is technically true, even if it mostly involved me sighing heavily before hitting ‘send.’

Because that’s the reality of sales, isn’t it? Sometimes you hit your number through grit and skill. And sometimes, you hit it because the universe just threw you a bone. The trick is to accept both with equal grace – and maybe a quiet smirk.

Welcome back, fellow travelers on the path of slightly-below-average sales achievement. This week, we’re tackling a topic near and dear to the heart of every sales rep who’s ever looked at a feature list and thought, “… Seriously?”

I’m talking about the product roadmap. That glorious, often-mystical document that promises a brighter future. The thing we’re told will “unlock new markets,” “delight customers,” and “revolutionize the way we sell!” It’s usually presented with a flourish, maybe a webinar, maybe a fancy PDF, definitely a lot of buzzwords.

And then you actually look at it.

See, as sales folks, we have… specific needs. We’re the ones talking to customers every day. We hear the same requests, the same pain points, the same “If only you had X, I’d sign the paper right now!” We meticulously gather this feedback and dutifully submit it. We hope.

What does the roadmap usually deliver?

Oh, it’s full of awesome stuff! Just… awesome stuff that often seems to exist in a parallel universe. A universe where our customers don’t live.

Instead of that crucial integration with the CRM everyone uses? We get a blockchain-powered feature for… reasons? Instead of the desperately-needed reporting that would actually show useful data? We get a UI refresh that moves the “Save” button three pixels to the left. Instead of that one tiny tweak that would unblock a dozen stalled deals? We get a new AI-powered module that predicts… something. (We’re still not entirely sure what.)

The features are often presented like they’re the answer to all our prayers. “Imagine,” the Product Manager says, with a gleam in their eye, “how much more effective you’ll be when you can [insert complex, vaguely-useful feature here]!”

We try to imagine. We really do. We politely nod. We ask clarifying questions. We desperately search for the one use case where this new thing might actually help close a deal.

Meanwhile, in our heads, we’re thinking: “So, about that simple API integration…?”

It’s not that we don’t appreciate innovation. It’s just that sometimes, it feels like Product Management lives on a different planet. They’re driven by… different metrics. They get excited about… different things. They might even talk to customers, but maybe those customers are… theoretical?

The Average Sales Guy learns to adapt. You learn the art of the spin. You say things like, “While we don’t have X yet, our amazing upcoming feature Y will completely revolutionize how you think about [vaguely related concept]!” You sell the vision. You sell the potential. You sell the things that are on the roadmap.

You learn not to ask too many direct questions about the things that aren’t on the roadmap.

And you keep submitting those feature requests, year after year, knowing that maybe, just maybe, one day, they’ll build that simple thing that would actually help you hit quota.

Until then, you embrace the absurdity. You find the humor in the disconnect. You realize that, in the grand scheme of things, the roadmap is just another obstacle to overcome. Another challenge to navigate. Another Tuesday in sales.

That’s just life for the Average Sales Guy.

Alright folks, settle in. My name’s Gary Miller, and I’m your host here at the Average Sales Guy blog. If you’re looking for secrets to hitting 300% of quota, scaling your outbound to infinity, or becoming a sales ninja warrior, you’ve probably clicked the wrong link. My goal is simpler: share stories from the trenches that make you think, “Yep, that sounds about right,” or “Okay, maybe my sales life isn’t that weird.”

This week’s installment comes courtesy of a deal I officially waved goodbye to just a few days ago. It was a good one, nothing earth-shattering, but solid. You know the kind – good fit, engaged champion, seemed to understand the value proposition, competitive landscape felt manageable. It was the kind of deal you pencil into the “probable commit” column, maybe even let yourself daydream about the commission check for a solid 30 seconds before shaking your head and remembering Rule #1: It Ain’t Over ‘Til the Paper’s Signed (And Sometimes Not Even Then).

We were there. The finish line was in sight. Legal seemed happy (a minor miracle in itself). Procurement wasn’t raising any red flags (another sign the universe was maybe, possibly, briefly aligning). My internal champion was responsive, asking about next steps for implementation. I was feeling pretty good. Maybe even… confident? (Rookie mistake, I know).

And then it happened. The email landed.

It wasn’t from my champion. It was from someone new they’d looped in – apparently a stakeholder who needed a final look. Their question was polite enough, but it hit like a sudden hailstorm on a sunny day. It was about a feature. A small one. Like, really small. Think the digital equivalent of needing a very specific color of staple remover. Something we honestly rarely get asked about. Something that had never, ever, once come up in the dozens of conversations we’d had over months.

My immediate thought process went something like this: “Huh? That feature? Do we… have that? Surely we do. That seems… basic? Or maybe super niche? No, wait, is that even our product? Is this a competitor spec? Let me quickly check the internal wiki that’s definitely out of date…”

Cue the frantic internal scramble. Pinging the poor, overworked SE who probably gets 50 ridiculous questions from AE’s a day. “Hey, Bob! Feature X! Do we have it? Like, specifically how they’re asking?” Hitting up Product Management chat groups. Sifting through old battlecards. There was a brief, desperate hope it was a misunderstanding. A simple configuration change. A setting toggled in the admin panel.

The reality hit back with the force of a wet noodle. Nope. We did not have Feature X. Not in the current release. Not in the next release. Not even really on the drawing board because, frankly, almost no one asks for the darn thing.

Delivering that news to the customer was… fun. “So, about Feature X… turns out, yeah, that’s not something we currently offer.”

Their response was swift and decisive. “Oh. Well, that’s actually a hard requirement for us now. We, uh, just realized how critical it is for [insert slightly vague, sudden use case here]. Guess we’ll have to go with Competitor Y. Thanks for your time!”

And just like that, poof. Months of work, gone. Not because our core product wasn’t a fit. Not because pricing was off. Not because of a major gap. Because of the digital equivalent of a specific color of staple remover that suddenly became the linchpin of their entire operation the day before signing.

Trying to explain that on the forecast call was… an experience. “Yeah, so, [Deal Name] is a closed/lost. Reason? Missing feature.” Cue the follow-up questions: “Which feature? Was it a known gap? Was it on the roadmap?” Explaining that it was a sudden, last-minute requirement that appeared out of nowhere just earns you the sympathetic, slightly bewildered stares of colleagues who’ve undoubtedly experienced their own version of this particular sales hell.

Look, I’m not going to pretend I wasn’t annoyed. Losing a deal that way stings. It feels absurd. Like the sales gods are just messing with you. But after almost two decades in this game, you also develop a certain… acceptance. This stuff happens. Deals are fragile ecosystems, and a butterfly flapping its wings in a customer’s engineering department can apparently cause a hurricane in your pipeline.

You dust yourself off. You update the CRM (while muttering under your breath). You try to find the slightly dark humor in the situation. And you move on to the next opportunity, knowing, deep down, that it too will present its own unique, probably equally absurd, challenge.

That’s just life for the Average Sales Guy.