Title: If the pain is not quantified, it’s not real

Read time: 3.5 min

Today I want to talk about something that’s showing up a lot right now with founders going to market, running calls, and trying to validate what they’ve built, but not getting the signal they expected.

They’re having real conversations. Buyers are engaging, they’re acknowledging the problem, and it can feel like we’re driving the deal forward.

But nothing happens after.

I’ve been selling a long time and I can tell you deals don’t usually fall apart, they just never take shape. Follow-ups feel like a chase. The urgency isn’t there. The buyer goes back to their day, and this becomes one of ten things they’re thinking about, not actively pursuing.

When you really look at it, it’s not a product issue and it’s not a market issue.

It’s that the problem, or the failure to prove out a business case never became real enough to act on. You never tied the pain and quantified the pain to a real business case that drives internal buy in.

A buyer gives you something important, something that should carry weight, and it gets acknowledged instead of unpacked. The conversation moves forward, but the moment that actually mattered is already gone.

That’s where deals die. In this issue I’m going to teach you how to better quantify pain and tie it directly to a business case.

In God We Trust. All Others Must Bring Data.

~W. Edwards Deming

Where the Conversation Falls Short

Most conversations feel productive because there’s agreement. The buyer recognizes the problem, and there’s alignment that something should be better.

That’s not enough.

Agreement without depth doesn’t create pressure to change anything. It just confirms that something isn’t perfect, which is true in almost every business.

The gap is in what happens next.

If the problem stays broad, it never becomes something the business has to prioritize. It stays in that category of “we should probably fix this at some point,” which is where most deals quietly die.

Nothing feels broken on the call, but nothing gets built either.

What Building the Business Case Actually Looks Like

This is where the call needs to slow down and the conversation needs to get more deliberate.

A buyer might say something like:

This process is very manual and laborious, and honestly the customer experience isn’t great because of it.

That’s a layup.

But what usually happens is it gets acknowledged and the call moves on.

What should happen is this:

You stay there.

You: When you say manual, what does that actually look like day to day?

Buyer: We’re handling everything manually across tickets and calls.

You: Roughly how many tickets or calls are we talking about in a week or month?

Buyer: Around 8k a month.

Now the problem starts to take shape.

You: And how many people are involved in handling that volume today?

Buyer: We’ve got about 12 agents covering it.

You: If that volume grows, does that mean adding more people to keep up?

Buyer: Yeah, that’s basically what we’ve been doing.

Now we’re getting somewhere.

You: What happens on the customer side when things get backed up? Are response times slipping or SLAs getting missed?

Buyer: Yeah, response times slow down and we miss SLAs more than we’d like.

Now the impact is visible.

At that point, you bring it together:

You: So it’s not just that the process is manual. It’s that the manual work is forcing you to add headcount as volume grows, slowing down response times, and creating more risk on the customer side. That’s what’s making it hard to scale without costs increasing. Is that fair?

That’s a completely different conversation.

Now there’s something real.

This is where most people move too fast.

The instinct is to keep the call moving, cover ground, get to the demo, show value. But if the problem hasn’t been built out, none of that lands the way it should.

The work is in staying in that moment long enough to understand it properly.

Not just what the problem is, but how big it is, how often it shows up, and what it creates across the business. What’s the downstream impact? Once that’s clear, everything else becomes easier to connect.

You’re no longer talking about features or capabilities in isolation. You’re tying them directly to something the buyer already understands and feels.

That’s where the conversation shifts from “this is interesting” to “this is something we need to figure out.”

The One Thing That Breaks It All

At a certain point, the issue isn’t what we know, it’s how we handle what shows up during the conversation.

A buyer gives an answer that sounds acceptable, but it lacks color. There’s no real specificity behind it, no clear sense of impact. That’s the moment where the conversation needs to slow down and get more precise. Instead, it’s easy to keep things moving, assume it’s good enough, and continue forward.

That decision carries more weight than it seems.

When something important is left unclear, the problem never fully takes shape in the buyer’s mind. Without that clarity, there’s no urgency tied to it. The conversation can still feel productive, but it doesn’t create the pressure needed for a decision.

What follows later usually reflects that gap. The buyer needs more time, priorities shift, or the deal loses momentum altogether.

The adjustment is straightforward, but it requires discipline. When a response feels incomplete, stay with it. Ask for a concrete example. Ask what it looks like in practice. Ask what it’s costing them today. The goal is to move from a general statement to something specific and real.

That’s where decisions start to form. Recognizing when to do that comes from experience. The more time spent in real conversations, the easier it becomes to identify what actually matters and act on it without hesitation.

Key Takeaways

Most deals don’t stall because something went wrong. They stall because the problem never became strong enough to move.

A vague pain point will not compete with every other priority on the buyer’s plate. It has to be unpacked, quantified, and tied to a clear business case before the company feels any real pressure to act.

That’s the work Rampd helps teams build.

We help founders and sales teams turn founder-led sales from reactive conversations into a repeatable operating system. That means knowing where to slow down, how to ask better follow-up questions, how to turn vague problems into real business impact, and how to make every sales call a feedback loop for sharper execution.

Once the pain is clear, the business case is real, and the next step has weight, deals move with a lot more clarity. We can help.

That’s it for today, peeps.

See you all next week!

Darren




P.S. If finding PMF and scaling to $1M in ARR through founder-led sales is on your radar, book a call with me here

💡 How We Can Help

Title: You can’t think your way into better sales

Read time: 2.5 min

Today I want to talk about a trap I see a lot founders and early sales teams fall into when trying to get better at selling. It feels like they’re doing all the right things. They’re learning, consuming, studying, trying to sharpen their thinking.

But when it comes time to actually run a call, something doesn’t translate.

At Rampd, we see this over and over again. The people who feel the most prepared are often the least effective in real conversations. They know what a great sales process should look like. They understand frameworks. They can explain what good discovery sounds like.

But… They haven’t spent enough time actually doing the thing.

Earlier in the year we worked with a founder who had read everything. Sales books, frameworks, playbooks, all of it. He’d been reading this newsletter for months. Opening certain issue 20+ times. He could walk you through exactly how a deal should be run from start to finish. On paper, he looked like a killer.

When it came to actually applying what he learned that was different beast altogether.

First thing we did when he came on was listen to his calls.

He was missing almost everything. The structure was there, but the killer instinct was not. He knew what to do, but in the moment, he wasn’t doing it

You cannot read about war in a book and think you’re going to be effective on a battlefield. Nor can you read about working out, get fit and strong, and not lift weights.

They say knowledge is power. This is partially true. Knowledge is power when it is applied, not theorized.

He didn’t need more information. He needed more reps.

It Never Gets Easier.You Just Go Faster.

~Greg Lemond (3x Tour de France winner)

Reps > Info

Right now, it’s incredibly easy to confuse learning with progress. Everyone is a coach or a guru on LinkedIn, and there is an endless amount of content to scroll through. The majority of it is written by people who are not operators, and you can usually tell by the content itself. It is optimized for likes, not application. They are not doing the thing. I would be careful not to spend hours consuming “quality” content and walk away feeling like you’ve actually improved.

Because what you’ve actually done is delay the moment where you have to perform.

Sales is not something you understand your way into. It’s something you earn through repetition. Steel is forged in fire. There are nuances in real conversations that you will never pick up from content. You have to experience them directly.

You have to recognize hesitation without it being said. You have to feel when a deal is drifting. You have to learn how to stay in a moment longer than is comfortable and figure out what’s actually going on.

That level of awareness only comes from reps.

Procrastination Masquerading as Production

We see a lot of founders get caught in the trap of staying in preparation mode longer than they should.

They spend time refining what they’re going to say instead of putting themselves in situations where they have to say it. They convince themselves they need to feel more ready before increasing volume. This is what I call procrastination masquerading as productivity.

There will always be more to learn. If you wait until you feel fully prepared, you’ll spend most of your time on the sidelines. It feels productive, but you’re avoiding the thing. You have to do the thing.

Avoiding reps creates inconsistency. You’ll have one call where things click, where the conversation flows and the buyer engages. Then the next call feels completely different. You hesitate. You miss things. The conversation ghosts.

Inconsistency will always show up in your results. Deals stall without a clear reason. Buyers seem interested but don’t move. You’re left trying to figure out what changed.

What changed is not the buyer. It’s your lack of sparring.

The Reps Breakdown

If you actually want to get better, you need a system that forces improvement through repetition.

Start by increasing the number of real conversations you’re having each week. Not activity for the sake of activity, but actual conversations where you are responsible for moving something forward. If that number is low, nothing else matters.

After each call, take a few minutes to break down what actually happened. Focus on specific moments. Where did the conversation lose momentum? Where did you hesitate? What did you hear but not act on?

If possible, record your calls and review them. This is where things become clear. You’ll start to see the gap between how you think you show up and how you actually do. Tone, pacing, control, all of it becomes visible.

From there, narrow your focus. Pick one thing to improve on the next call. Go deeper on answers. Slow the pace. Stay in moments longer. Then run it again and apply it immediately.

That cycle, reps followed by reflection and adjustment, is what builds real skill.

The One Thing That Breaks It All

At a certain point, the issue isn’t what we know, it’s how we handle what shows up during the conversation.

A buyer gives an answer that sounds acceptable, but it lacks color. There’s no real specificity behind it, no clear sense of impact. That’s the moment where the conversation needs to slow down and get more precise. Instead, it’s easy to keep things moving, assume it’s good enough, and continue forward.

That decision carries more weight than it seems.

When something important is left unclear, the problem never fully takes shape in the buyer’s mind. Without that clarity, there’s no urgency tied to it. The conversation can still feel productive, but it doesn’t create the pressure needed for a decision.

What follows later usually reflects that gap. The buyer needs more time, priorities shift, or the deal loses momentum altogether.

The adjustment is straightforward, but it requires discipline. When a response feels incomplete, stay with it. Ask for a concrete example. Ask what it looks like in practice. Ask what it’s costing them today. The goal is to move from a general statement to something specific and real.

That’s where decisions start to form. Recognizing when to do that comes from experience. The more time spent in real conversations, the easier it becomes to identify what actually matters and act on it without hesitation.

Key Takeaway

Most deals don’t fall apart at the end, they fall apart in the moments where we accept surface-level answers instead of getting to something real.

Clarity drives decisions, and clarity only comes when we slow down long enough to fully understand what’s actually going on.

If the problem isn’t specific, grounded, and felt on the call, there’s nothing strong enough to carry the deal forward afterward.

Reps matter because they train us to recognize those moments in real time and have the discipline to stay in them instead of moving on.

Improvement in sales doesn’t come from knowing more, it comes from handling those moments better when they show up

That’s it for today, folks.

See you all next week!

Darren




P.S. If finding PMF and scaling to $1M in ARR through founder-led sales is on your radar, book a call with me here

💡 How We Can Help

Title: You will never outperform your self-awareness

Read time: 3 min

Today I want to discuss something I see all the time in founder-led sales, and really in sales more broadly. Most people are completely unaware of it, and they don’t spend nearly enough time thinking about it, yet it shows up in almost every deal you win or lose.

It has nothing to do with your pitch or how polished your product is. It’s how you see yourself when you’re in the arena.

I’ve been on thousands of sales calls, and over time patterns become virtually impossible to ignore. Two people can run nearly identical calls, ask similar questions, and walk through the same process, yet the outcome is completely different.

One moves the deal forward with conviction and clarity. The other leaves the call feeling like it went well, but the deal never materializes.

When you really break that down, it’s rarely about what was said. It’s almost always about the level of certainty, authority, and clarity behind it.

Whether you’re aware of it or not, every belief you carry about yourself, your product, and your role in that conversation shows up in how you ask questions, how you handle pushback, and how you guide the buyer.

That’s what buyers are responding to.

The amygdala is a threat detector. It evolved not to make you happy, but to make you cautious.

~Daniel Goleman

What’s Actually Going On

A lot of teams early on think they have a sales problem, which is definitely valid, but when you break it down to its fundamental level they have a pattern problem.

How we were conditioned growing up, how we handled conflict, whether you tend to seek approval or whether you trust your own judgment, all of that comes with you into every call. It doesn’t turn off just because you’re in a sales conversation. This is one of the key elements we coach are clients on. We build very structured processes to follow to help dial down all of these limited beliefs.

If you avoid tension or being direct in your personal life, you’ll avoid it on calls. If you second-guess yourself in other areas, you’ll feel it when it’s time to take control of a conversation. If you don’t fully believe in your authority, you’ll hesitate when it matters most.

None of this is obvious in the moment. It just feels like the call didn’t quite land, or the buyer needs more time, or the timing isn’t right.

But those outcomes are usually symptoms of something deeper.

Buyers can feel when someone is certain and when they’re not. They can feel when they’re being guided versus when they’re left to figure things out on their own. When you convey a lack of conviction or there’s any uncertainty on the call, it almost always slows the deal down.

Why This Is So Hard to Fix

This is where we tend to get stuck, and most of the time we don’t even realize it’s happening.

We assume we have a sales problem. Something in the call didn’t land, the deal ghosted, so we start looking outward for answers. We tweak how we communicate, adjust how we run the conversation, try to improve execution.

That all feels productive, but it keeps us operating on the surface.

What’s actually happening can be way deeper than that. It’s the patterns we bring into the conversation without being aware of them.

You see this outside of sales all the time. Someone moves from one shitty relationship to another, and the details change, but the outcome is consistently bad. The same patterns and frustrations show up and the same breakdowns happen. Eventually, it forces a much harder question, that we try to avoid.

Is it really the other person, or is it something we’re carrying with us?

How we communicate. What we avoid and tolerate. What we believe we deserve.

Sales works the same way.

We don’t leave that wiring behind when we get on a call. It follows with us in every interaction in life and it’s usually amplified when selling, because for most, selling is uncomfortable. If we tend to avoid tension, we’ll feel it when it’s time to go deeper. If we care too much about being likable, we’ll bend the knee when more clarity is needed. If we don’t fully trust ourselves, we’ll hesitate when the conversation needs direction.

There’s real psychology behind this. And sales, my peeps, is nothing but human psychology. Our brains are wired to protect us, not to make us wealthy or happy. They steer us away from discomfort, tension and anything that feels like risk. Even when that’s exactly where progress lives. This is one of the reasons if feels so good to close business.

That’s why we can know what to do and still not do it. The difference between knowing, doing and applying it is where most deals actually fall apart.

Until we start paying attention to that, we’re not really fixing the problem, we’re just deceiving ourselves.

What You Can Start Doing Differently

This does not change by learning another framework or refining your pitch. It changes when you start paying attention to how you behave in real time.

Start with a single moment in your next call. Focus on where you normally feel a bit of tension, maybe when a buyer gives you a vague answer or when the conversation begins to drift. Stay in that moment longer than you usually would. Instead of moving on, slow it down and ask one more question.

Try something simple like, “Can you walk me through that a bit more?” or “What does that actually look like day to day?” The goal is not perfection it’s interrupting your default pattern.

Silence is another place to work. Most people rush to fill it since it feels uncomfortable. Don’t do this, because people do not like silence. Think about how awkward it is in an elevator with a bunch of strangers. Ask your question, then give the other person space to think. Let the pause sit. That silence often leads to better answers than anything you could add.

Clarity matters when something does not fully make sense. If a response feels surface-level or incomplete, address it directly.

Easiest way to do that is, “I might be off here, but that sounds like something you’d want to improve, not something that has to change right now. Is that fair?” That kind of statement helps both sides get aligned quickly.

This is not about being aggressive. It is about staying present enough to recognize what is happening and choosing a better response.

Confidence builds through repetition. It comes from doing the harder thing in real time, enough times that it no longer feels unnatural.

Key Takeaway

Most of what shows up in your sales calls has very little to do with your talk tracks and a lot to do with how you think. The patterns you’ve built over time don’t disappear when you enter a sales conversation. They show up in how you handle pressure, how you respond to uncertainty, and whether you step forward or pull back when it matters.

What feels like a sales problem is often just a repeated pattern. The same hesitation, avoidance and need to keep things comfortable. It looks different on the surface, but the underlying behavior is consistent.

Awareness is the turning point. Once you can see where you hesitate, where you soften, and where you avoid going deeper, you can start to change it. Until then, you’ll keep solving the wrong problem.

Progress does not come from knowing more. It comes from doing the uncomfortable things in real time. Repeatedly. Staying in the moment a little longer. Asking the question you would normally avoid. Holding the line when something is unclear.

Confidence is built through action, not thought. It develops through repetition, through choosing a better response over and over again until it becomes natural.

When you start to become more aware and work through it, everything downstream improves. Conversations become clearer. Buyers feel more certainty. Decisions happen faster.

That’s where real progress starts, on the other side of uncomfortable.

That’s it for today, folks.

See you all next week!

Darren


P.S. If finding PMF and scaling to $1M in ARR through founder-led sales is on your radar, book a call with me here

💡 How We Can Help

Title: Most sales calls are lost in the first five minutes

Read time: 3 min

Today I want to discuss something most founders underestimate, and in many cases completely overlook.

It’s one of the biggest levers in my career that’s allowed me to close deals consistently over the years, and it has very little to do with the product itself.

It’s conviction. Owning the stage.

The ability to speak with clarity, confidence, and certainty about what you do and why it matters. It comes from understanding your craft deeply and not second-guessing yourself when it’s time to lead.

This is a critical component of selling, because I can truthfully say that most sales calls are decided in the first five minutes.

Not closed, but decided.

What happens in that opening window sets the tone for everything that follows. It determines whether the buyer sees you as someone guiding the process or someone reacting to it. Once that perception is formed, it is very difficult to change.

Today I’m going to help you start fixing it.

Fear Causes Hesitation. And Hesitation Will Cause Your Worst Fears To Come True.

~Bodhi (Point Break)

What Actually Happens On Most Intro Calls

Most of the sales calls I’ve listened to begin the same way. Light introductions/bios, a bit of small talk, then a soft transition into the product. The founder tries to be agreeable, open, and accommodating. They want the buyer to feel comfortable.

Feels like the right thing to do. Wrong. What you’re doing is giving up control of the conversation. Prospects are constantly sizing you up and building a profile of they believe you are. You have to own that shit from the jump.

Otherwise the buyer starts leading. They jump into questions, steer the direction, and dictate the flow of the call. The founder follows along, answering, explaining, and reacting in real time.

It feels collaborative and like your building rapport, but In reality it creates uncertainty.

Now the buyer is controlling the conversation and calling the shots, and is not being guided through a process. They have to piece things together on their own. When buyers feel like they have to figure things out themselves, they slow down.

Not because they aren’t interested, but because they aren’t confident.

The Psychological Component Most Founders Miss

At the core I don’t believe this is a sales problem. It’s a belief problem.

A lot of founders carry an underlying hesitation when they get on calls. They don’t want to come across as pushy, or icky. They don’t want to sound too assertive. They assume that being more accommodating will create a better experience.

What actually happens is the opposite. Your digging hole for yourself.

When you are not clearly leading the conversation, it signals uncertainty, and uncertainty transfers. The buyer begins to mirror it, whether consciously or not.

This is where limited beliefs start to shape outcomes.

If you believe you need to earn the right to guide the call, you will hesitate. That hesitation shows up in how you speak, how you ask questions, and how you position the product. Over time, those behaviors compound and become your experience.

You start seeing longer sales cycles, more indecision, and more deals that ghost dog you.

Why Authority Changes Everything

The strongest sales conversations have a different feel from the beginning.

There is a clear structure. The agenda is set early. The founder establishes how the conversation will run and what needs to be accomplished by the end of it.

This is not about being aggressive. It’s about being decisive and assertive. Big difference.

As mentioned earlier, buyers are constantly evaluating not just the product, but the person in front of them. They are asking themselves, often subconsciously, whether this person understands the problem deeply enough to guide them toward a solution.

When that answer is yes, the whole vibe shifts. The buyer relaxes. It’s one less decision they need to control and they start engaging and answering questions differently. Because now they feel like they are being led by someone who knows what they are doing.

What Founders Should Do Instead

The first shift happens before the call even begins. You need a clear structure for how every conversation will run, and you need to commit to it. That starts with a strong preamble that sets expectations. Instead of easing into the call, define it. Outline what you’re going to cover, what you need from the buyer, and what a successful outcome looks like.

From there, maintain control through your questions. Not by dominating the conversation, but by directing it. Ask questions that move the discussion forward, not ones that keep it open-ended. When a buyer goes off track, bring them back. That is your responsibility.

Equally important is how you position yourself. You are not there to pitch. You are there to diagnose. That shift alone changes how you show up. It allows you to speak with more clarity, because you are focused on understanding and solving, not convincing.

Confidence, in this context, is not something you wait to feel. It is built through repetition. The more calls you run with structure and intention, the more natural it becomes. Over time, your tone changes. Your pacing improves. Your ability to handle objections sharpens.

That’s where the conviction comes.

When you speak with conviction, buyers feel it. It reduces hesitation, accelerates decisions, and creates momentum in the deal.

Key Takeaway

A lot of founders spend their time improving the product, when in reality, the biggest gains often come from how they show up in the conversation early on. No matter how strong the product is, it still has to be understood, trusted, and acted on.

That happens on the call.

The first five minutes aren’t a formality. They set the tone, establish authority, and shape how the buyer engages with you for the rest of the call.

Once that perception is formed, everything that follows either becomes easier or harder.

That’s where conviction comes in. Not just in what you say, but how you lead, how you frame, and how you carry the conversation.

This is a core part of what we work on with founders on at Rampd. Helping them lead with clarity, build trust early, and run conversations that actually move deals forward.

When you control the conversation, you control the outcome.

If your calls feel inconsistent or deals are stalling, there’s a reason.

And it’s fixable. Start today.

That’s it for today, folks.

See you all next week!

Darren


P.S. If finding PMF and scaling to $1M in ARR through founder-led sales is on your radar, book a call with me here

💡 How We Can Help

Title: AI didn’t speed up buying. It complicated it.

Read time: 3 min

Today I want to discuss a consistent problem I’m seeing and hearing on sales calls. Something that goes directly against what most people believe about AI and its ability to close the sales gap faster.

The assumption is that AI speeds everything up. Faster workflows, insights and faster execution. Naturally, that should translate into faster buying decisions.

What we’re seeing suggests the opposite.

Across the conversations we’re having and the deals we’re involved in, AI is not compressing sales cycles. In many cases, it’s extending them.

Oftentimes it’s not because the technology isn’t valuable. It’s because of how buyers experience it. This is a big problem that as they say is separating the wheat from the chaff.

In today’s newsletter I’ll explain why and how we help fix it.

What We Found Is That People Don’t Just Want The Best Product, They Want To Make The Safest Decision.

~Satya Nadella

What People Expected vs What’s Actually Happening

The expectation with AI has been no secret. If a product can automate work, reduce cost, or improve output, the decision to adopt it should be relatively easy. The ROI feels obvious, and the path forward should be clear.

In reality, the buying process has become more complex, because the market is saturated.

Buyers are evaluating multiple AI vendors at once, often with overlapping capabilities and similar positioning. On the surface, many of these products appear interchangeable. Underneath, they behave very differently depending on how they are implemented.

That gap creates friction and indecision.

Instead of quickly identifying the best solution, buyers are forced to compare nuances they don’t fully understand. The evaluation process becomes less about selecting a tool and more about managing risk.

This slows everything down.

What’s Driving Longer Sales Cycles

What’s happening beneath the surface is less about the product and more about the decision itself.

AI introduces a level of ambiguity that traditional software didn’t. It touches workflows, data, and outcomes in ways that are not always predictable upfront. Buyers are not just asking whether the product works, they are trying to understand how it will behave once it’s embedded into their organization.

That uncertainty brings more people into the conversation. Legal wants to understand risk. Operations wants to understand impact. Leadership wants confidence that the outcome is repeatable. Procurement is starting to become a real bottleneck for deals closing fast.

Each layer adds time.

At the same time, the saturation of AI vendors created a crowded landscape. Buyers are seeing multiple solutions that all claim to solve similar problems, which makes differentiation harder. When everything looks capable, the default response is to slow down and evaluate more carefully.

The result is a paradox.

The technology is faster than ever, but the decisions around it are slower than before.

Where Founders Get Jammed Up

A lot of founders assume that a better product will naturally accelerate the sales process. The instinct is to show more capability, highlight more features, and demonstrate the full power of what has been built.

In practice, that often has the opposite effect.

The more surface area a product presents, the more questions it creates. Buyers begin thinking about implementation, edge cases, and what could go wrong. Instead of moving closer to a decision, they start mapping out potential complexity.

You need to tread carefully to not turn excitement into caution.

The issue is not the product itself. It’s how it’s being presented and how the decision is being framed.

What Founders Should Do Instead

If sales cycles are stretching, the answer is not to add more to the product or show more in the demo. It’s to reduce the cognitive load required to make the decision.

Start by anchoring every conversation to a single, clearly defined problem that already exists inside the buyer’s organization. Not a broad capability, but a specific, repeatable issue that has measurable impact. The more concrete the problem, the easier it is for the buyer to evaluate.

From there, control the scope of what you show. Demonstrate only what is required to solve that problem and resist the urge to expand beyond it. When buyers are presented with a contained solution, they evaluate the outcome. When they are presented with a system, they evaluate the complexity.

It is also critical to guide the decision process, not just the product evaluation. Clarify what success looks like, what implementation realistically involves, and what the first step forward should be. The more ambiguity you remove, the faster the buyer can move.

Finally, qualify for urgency early. If the problem is not a priority, no amount of product depth will accelerate the deal. When the need is real, decisions compress. When it is not, they stretch indefinitely.

Key Takeaway

In my experience with our clients and being deeply embedded in this world. AI did not remove friction from the buying process. In many cases, it introduced new layers of it.

The companies that win in this environment are not the ones with the most advanced features. They are the ones that make the decision feel simple, clear, and low risk.

It’s a sales problem, not a product problem.

This is exactly where we focus with founders. We help them tighten their positioning, control the narrative in sales conversations, and build a process that turns complex products into clear decisions buyers can confidently make.

That’s it for today, folks.

See you all next week!

Darren


P.S. If finding PMF and scaling to $1M in ARR through founder-led sales is on your radar, book a call with me here

💡 How We Can Help

Title: AI companies are scaling like services, not software

Read time: 3.5 min

Today I want to discuss the idea of building AI products that indirectly rely on services behind the scenes to actually deliver results.

From the conversations we’ve had, the companies we’ve worked with, and what we’re seeing across the market, we get deep insights into different patterns unfolding. A number of AI companies that are positioned as software businesses are operating much closer to services businesses in practice.

The distinction is not semantic. It fundamentally changes how the company grows, how it prices, and what it takes to deliver value to a customer.

What’s interesting is that this shift doesn’t happen because founders set out to build services companies. It emerges as a byproduct of trying to make powerful but imperfect technology work in real world environments. The product looks clean in a demo, but once it is deployed inside an org, variability shows up quickly. Workflows are inconsistent, data is messy, and the conditions required for the product to perform as expected are rarely present out of the box.

At that point, the gap between what the product promises and what the customer needs has to be closed somehow. In many cases, that responsibility falls back on the team. They step in to adjust outputs, refine how the system is being used, and shape the implementation so that the result aligns with the expectation set during the sales process.

None of this is inherently problematic. In fact, it is often necessary early on. The issue is that over time, this pattern becomes embedded in how the product is delivered. What was initially a temporary bridge becomes part of the operating model.

A Lot Of People Build Something And Then Try To Figure Out How To Sell It. That Almost Never Works.

~Sam Altman

What’s Happening Underneath The Hood

The current AI cycle has made it ridiculously easy to build something that appears complete. Products can demonstrate real capability in a controlled environment, and that capability translates well in early conversations with buyers. The challenge begins once that capability is introduced into the complexity of an actual business.

What we’ve consistently observed is that success depends less on the product functioning in isolation and more on how well it is integrated into an existing workflow. That integration is rarely seamless. It requires interpretation, adjustment, and in many cases, active involvement from the team behind the product.

This is where the model of the business begins to shift. Instead of the product being the sole driver of value, value is delivered through a combination of product and human input. The customer still experiences a solution, but the mechanics behind that solution are different from what a traditional software model would imply.

Over time, this creates predictable constraints in my experience. Each new customer introduces a slightly different set of requirements, and implementation carries its own nuances. Progress sometimes is made, but it is not always linear, and it often depends on continued effort from the company delivering the product.

Why This Matters More Than It Seems

The reason this matters is not because services are inherently bad. Many great businesses are built on services. The issue arises when there is a mismatch between how the business is described and how it actually operates.

When a company believes it is building software but is effectively running a services model, decisions around hiring, pricing, and growth are made on the wrong assumptions. Margins behave differently, and timelines typically stretch. Scaling requires more coordination than expected.

This disconnect tends to surface gradually. It shows up in longer onboarding cycles, heavier customer involvement, and the need to stay close to each account to ensure outcomes are delivered consistently. None of these are immediate failures, but they compound over time, and can definitely neg you out.

What I’ve seen at the core of this pattern is a simple reality. AI systems are pretty sick, but they are not yet universally reliable across all contexts without some level of adaptation. Real-world environments introduce variables that are difficult to fully anticipate during product development.

As a result, teams compensate. They intervene where the system falls short, refine how it is used, and ensure that the customer ultimately sees the value that was promised. This approach works, but it introduces a dependency that is easy to underestimate.

The longer that dependency exists without being addressed, the more it defines the business, and jams up predictable sales.

Why? Because what often follows is a form of unintentional complexity. The product continues to evolve, but it does so alongside a layer of human-driven processes that are not always visible externally. The company grows, but the underlying system becomes harder to standardize.

At that point, the question is no longer just about improving the product. It becomes a question of whether the product can eventually stand on its own without the same level of support.

What Founders Should Do Instead

So what is the workaround in my opinion. I think one is to start with clarity. Founders need a precise understanding of how value is delivered today, not how it is intended to be delivered. That means mapping the full journey from first interaction to successful outcome and identifying where human involvement is required to make that outcome possible. This is why sales and building predicatble proceseses are so important.

Once that is clear, the next step is not to eliminate those touchpoints immediately, but to prioritize them. Which parts of the process are essential because of the problem being solved, and which exist because the product is not yet complete? That distinction determines where effort should be applied.

I believe, progress comes from systematically reducing reliance on manual intervention in the areas that matter most, and that does not happen all at once. It happens through tightening the use case, narrowing the conditions under which the product is sold, and reinforcing the scenarios where the system performs consistently.

Equally important is discipline in what is sold. If delivering value requires significant customization, that should be treated as a signal about the product, not an opportunity to stretch it further (read last weeks newsletter where I discussed this). The more consistent the conditions under which the product operates, the easier it becomes to move toward something that is truly repeatable.

Key Takeaway

The takeaway here is not that services are a problem. It is that understanding the nature of your business is critical to building it correctly.

If a product depends on ongoing involvement to deliver results, that is worth recognizing early. It provides clarity on where the product stands today and what needs to change to reach the level of scalability most founders are aiming for.

At Rampd, this is a conversation we have often with founders. Not to point out flaws, but to help them see the system as it actually operates, tighten the core use case, and move toward something that works predictably without constant intervention.

Once that shift happens, the business begins to behave very differently. What are you waiting for?

That’s it for today, folks.

See you all next week!

Darren


P.S. If finding PMF and scaling to $1M in ARR through founder-led sales is on your radar, book a call with me here

💡 How We Can Help

Title: The real reason most discovery calls go nowhere

Read Time: 3.5 min

Today, I will show you how to use what I coined the "One by One or One by Two Framework" to better identify the root cause of prospect pain on a discovery call.

Prospects typically will give you surface level answers to questions. It’s your job to peel back the onion and identify where the heart of the problem lies. This framework doesn’t just make you a better communicator; it positions you as a real pro who truly understands and cares. People don’t care how much you know until they know how much you care. You convey you care by asking well thought out questions. The only way you do that correctly is by listening.

Most people stop at the first question, leaving valuable details on the table—or fire off too many unrelated questions, overwhelming the prospect and derailing the conversation. Don’t do this. Even worse, their follow-ups fail to address the specifics of what was just said—conveying to the prospect that they’re really not listening.

People Don’t Buy A Quarter Inch Drill. They Buy A Quarter Inch Hole.

~ Theodore Levitt

In Issue 77, I discussed the framework we use with our clients to run discovery calls. In this issue, we’ll explore Step 2 of the discovery call process: identifying BANT.

Questions, for the most part, will be arbitrary based on your product and market you service, but these examples will cover the majority of info you need to understand.

Let’s take a look.

Current Process

Initial Question:
Great! I’d love to start by understanding how you’re currently managing [their workflow or process]. What systems or processes do you use to [specific task, e.g., consolidate revenue data, align teams on KPI tracking, automate customer touchpoints]?

• Follow-Up 1:
  You mentioned [specific detail they shared, e.g., that you’re using spreadsheets for tracking KPIs]. How has that method worked for your team? Are there any frustrations or inefficiencies that stand out?
  

• Follow-Up 2 (Optional):
  What happens when [describe a potential challenge they hinted at, e.g., you have to update reports manually or collaborate across departments]?

Challenges

Initial Question:
What are your biggest challenges when it comes to [specific pain point, e.g., integrating data from multiple sources, reducing manual errors, or ensuring real-time reporting]?

• Follow-Up 1:
  You mentioned [specific challenge they brought up, e.g., delays in getting accurate data]. Could you walk me through a recent example where this caused an issue for your team or your decision-making?
  

• Follow-Up 2 (Optional)
  What’s the impact of this on your team’s ability to [specific goal they’re trying to achieve, e.g., hit deadlines, scale processes]?”

Efficiency & Scalability

Initial Question:
“As your business grows and you handle more [specific factor, e.g., data points, accounts, customers], how are you ensuring your processes can scale without adding extra manual work?”

• Follow-Up 1:
  You mentioned [specific method or process they use, e.g., relying on a small team to manage growth]. How has that approach held up as your business has scaled? Have you encountered any bottlenecks?”
  

• Follow-Up 2 (Optional)
  What would happen if [specific scenario they’re concerned about, e.g., your data volume doubled or you expanded into new markets]?

Budget

Initial Question:
“Our typical customers allocate a budget ranging from [budget range] annually, based on factors like [volume of data, number of integrations, level of customization]. What kind of budget do you have set aside for [specific solution, e.g., workflow automation, data centralization]?”

• Follow-Up 1:
  You mentioned [specific budget constraint or flexibility]. How do you usually evaluate whether a solution is worth the investment?
  

• Follow-Up 2 (Optional)
  Are there any areas where you’ve found it difficult to justify spending, even if the ROI is clear?

Decision-Making (Authority)

Initial Question:
“Can you walk me through how decisions are made when adopting new solutions like [Your Company Name]? Who else is involved in the decision-making process?”

• Follow-Up 1:
  Can you walk me through how decisions are made when adopting new solutions like [Your Company Name]? Who else is involved in the decision-making process?
  

• Follow-Up 2 (Optional)
  Have there been any past challenges in getting alignment across stakeholders for similar decisions?

Timing (Urgency)

Initial Question:
“If we’re a good fit, what does your timeline look like for rolling out a solution like ours? Are you looking to implement something soon, or is this a longer-term project?”

• Follow-Up 1:
  You mentioned [specific time frame or dependency, e.g., aligning with your Q1 goals]. What’s driving that timeline??
  

• Follow-Up 2 (Optional)
  Is there any flexibility in the timing if we can deliver faster results for [specific pain point they mentioned earlier]?

Key Takeaways

• Drills Deeper: Your follow-ups are directly tied to what they’ve just shared, encouraging them to elaborate on key points and giving you more actionable insights and conveying you care.
  

• Shows Listening: By referencing their specific words or ideas, you demonstrate that you’re actively engaged in the conversation, building trust.
  

• Clarifies Priorities: Follow-ups like these help uncover what really matters to the prospect, enabling you to position your solution more effectively.

The "One by One or One by Two Framework" makes your discovery calls far more effective and conversational by focusing your follow-ups on their specific responses.

That’s it for today!

See you all next week.

Darren

P.S. If you’re a venture backed SaaS company interested in coaching book a call here.

💡 How We Can Help

Title: Listening to customers is killing your startup

Read time: 3 min

Today I want to discuss something that goes directly against the advice most founders are given, and I’m going to prove why it’s wrong.

I believe listening to customers too early is killing a lot of startups.

There is a widely accepted idea in the startup world that you should be relentlessly customer focused from day one. Talk to users, collect feedback, and build what people ask for. In theory, it sounds like the most rational path forward.

In practice, it’s where a lot of teams get jammed up.

What begins as a clear hypothesis on what you’re trying to validate quickly turns into a moving target. Early conversations produce a steady stream of requests, suggestions, and conditional interest. Each one feels like signal, or progress. Over time, they accumulate.

The product expands. The scope broadens, and the original use case becomes less defined.

Instead of solving one problem deeply, the product begins to address several problems superficially. Slowly you turn into the frog in boiling water. It’s where I’ve seen a lot of early-stage products lose their edge.

In my experience, markets do not reward optionality early on. They reward clarity. When clarity begins to erode, lack of traction follows.

Focus builds companies, not flexibility. AI will amplify this dynamic. The ease of building makes it even more tempting to respond to every request.

That temptation is what pulls most founders off course.

People Don’t Know What They Want Until You Show It To Them.

~Steve Jobs

What’s Actually Happening In Early-Stage Startups

Most startups begin with a hypothesis. There is a belief that a specific problem exists for a specific type of customer, and that it can be solved in a meaningful way.

The next step is obviously validation.

Founders go into the market and start having conversations. Early feedback is often positive. People recognize the problem, express interest, and offer suggestions on how the product could be improved.

This is where interpretation becomes critical.

Not all feedback you will hear, especially on product discovery calls carries the same weight. Early conversations tend to surface preferences, not priorities. People describe what would make a product more useful, but not necessarily what would make it essential.

The distinction is important. Preferences expand scope. Priorities define direction.

When those two are treated the same, the product begins to drift, and you get jammed up building and shipping these one off edge cases.

Why Customer Feedback Becomes Dangerous

Customer feedback is often treated as a direct input into the product roadmap. The assumption is that more feedback leads to a better product. In my experience this is not true, early feedback is fragmented.It comes from different types of users, operating in different contexts, with different constraints. Each perspective is valid in isolation, but taken together they rarely point in a single direction.

If every request is incorporated, the product becomes a collection of partial solutions rather than a complete one.

This creates a second problem.

The more surface area the product tries to cover, the harder it becomes for a buyer to understand what it actually does.

Clarity decreases. Positioning weakens. Sales convos become more complex.

At that point, the issue is no longer product capability, it’s product identity.

The Real Signal Founders Should Look For

There is a difference between interest and demand. Interest shows up as ideas, suggestions, and conditional statements.

Demand shows up as commitment.

A customer asking for additional features is not a reliable signal of demand. A customer willing to move forward with the current solution is.

This is where I see founders misread the market. They treat requests as validation, when in reality they are often deferrals. The product is close, but not compelling enough yet.

Instead of narrowing focus and strengthening the core use case, they expand the product in an attempt to satisfy more scenarios.

That expansion delays the one thing that matters most. Proof that the product solves a problem people are willing to pay to remove.

The Mistake Many Founders Are Making

The most common mistake is allowing feedback to override the original hypothesis too early. The initial product is designed to solve a specific problem. That problem should be tested, refined, and validated before anything else is added.

Instead, many teams begin layering additional functionality before the core use case is fully proven. This creates complexity without certainty.

A more effective approach is to treat the early stage as a process of elimination. The goal is not to build broadly, but to narrow in on what matters most.

That requires discipline.

It means saying no to requests that do not directly strengthen the core value proposition. It means resisting the urge to generalize the product too early. And it means accepting that not all feedback should be acted on immediately.

What Founders Should Do Instead

If you want to avoid this trap, anchor everything to a single use case.

Write down the exact problem you believe you’re solving, who it’s for, and what outcome it drives. Then take that into real conversations and pressure test it. You need shots on goal. A lot of them. Ask how they solve it today, what it costs them, and what breaks if it doesn’t get fixed.

From there, build the smallest version of a solution that removes that pain and try to sell it as is.

If they move forward, you have signal. If they stall and start asking for more features, don’t default to building. Go back and figure out whether the problem is actually painful enough or if you’re solving the wrong thing.

Use feature requests as input, not direction. Only build what reinforces the core use case. Everything else is a distraction. Once the problem is clear and validated, expansion becomes obvious.

Until then, adding more only creates noise.

Key Takeaway

I would say the key takeaways here are simple. Requests are not demand, and interest is not commitment.

Most important is feedback, especially early, is often misinterpreted.

The founders who get this right stay focused on proving one thing.

Does this product solve a real problem that someone is willing to pay to fix right now Everything else comes after that.

At Rampd, this is where we spend most of our time with founders. Helping them tighten the problem, validate the use case, and build a sales motion that proves demand early before the product starts to drift.

Because once you get that right, everything else gets easier.

On a related note, I’ll be speaking at Harvard Business School next week on this exact topic, how founders can validate real demand before overbuilding. Looking forward to sharing more there. You can grab tickets here. 

That’s it for today, folks.

See you all next week!

Darren


P.S. If finding PMF and scaling to $1M in ARR through founder-led sales is on your radar, book a call with me here

💡 How We Can Help

Title: The AI extinction event is coming

Read time: 3 min

Today I want to discuss something that might ruffle a few feathers. That’s ok, I tell the truth, and clients pay us a lot of money to do so.

I believe most AI startups should not exist.

Right now we’re living through what feels like a gold rush. Every week there’s another AI product launching, another company announcing funding, another demo showing how a model can automate some task. It looks and feels like innovation is exploding.

When you look a little closer, something else becomes obvious.

A massive percentage of these companies are not building real businesses. They’re building wrappers around APIs, and models. Wrappers around capabilities that every other company can access too, and most of them are solving problems nobody urgently needs solved.

The result is an ecosystem full of technically impressive products that no one feels compelled to buy. That’s a dangerous place to build a company, because markets do not reward interesting technology, they reward urgency.

And when urgency is missing, companies slowly begin to disappear.

If the last decade taught us anything, it’s that hype cycles create far more startups than markets can support. AI will be no different. I believe the next 24 months are going to look like an extinction event for AI startups. It’s already happening.

A Rising Tide Lifts All Boats. It’s Not Until The Tide Goes Out Do You See Which Ones Are Swimming Naked.

~Warren Buffett

What’s Actually Happening In The AI Market

Right now it’s easier than ever to build a product. You can spin up infrastructure in minutes, access world-class models through an API, and ship something functional in weeks. This is incredible progress.

But it has created an unintended side effect, building is no longer the bottleneck. Validation is.

When everyone can build quickly, it somewhat levels the playing field. The market fills up with products that were never pressure-tested with real customers. Many founders start with the technology and then search for a problem.

They experiment with use cases, refine the UI, and continue adding features, but they rarely stop to ask the only question that matters.

Is this a problem someone urgently needs solved?

If the answer is no, the product may still be interesting. It just won’t become a business.

Why Most AI Products Feel the Same

Another dynamic showing up right now is sameness.

If you look across many AI categories, the differences between products are surprisingly small. One tool summarizes documents. Another summarizes documents slightly differently. One tool automates outreach. Another automates outreach with a slightly different workflow.

Underneath the hood, many of these companies are using the same models and the same infrastructure.

Which means the actual product advantage (moat) is thin.

When that happens, buyers stop evaluating technology and start evaluating something else entirely. They ask which vendor understands their workflow best, which one feels easier to implement, and which one actually understands their problem.

In saturated markets, the companies that win are rarely the ones with the most features. They’re the ones with the clearest understanding of the customer use cases, and how painful they are.

The Real Reason Startups Will Disappear

Startups don’t die because the technology stops working. They die because the problem wasn’t painful enough.

A product can be impressive and still fail. It can have great design, powerful automation, and even early users, but if the problem it solves isn’t urgent, adoption slows down quickly.

Buyers get distracted. Budgets shift. Projects get deprioritized. Eventually the product becomes something people thought about using, but never truly needed.

This is the graveyard of startups. Not in dramatic collapses, but slowly, through indifference. Prospects are just not interested.

The Mistake Many Founders Are Making

The most common mistake I see right now is starting with the technology.

A new model appears, a new capability becomes possible, and founders immediately begin building products around it. The most successful companies start in the opposite direction.

They begin with a painful problem. Something expensive. Something inefficient. Something organizations are already struggling with.

Only after the pain is clear do they build the solution.

This approach feels slower at first, but it produces companies that survive. Because if the problem is real, what I call a broken leg problem, buyers don’t need to be convinced.

They are already incapacitated, they’re searching for relief immediately. This is the T (timing) in BANT, or the I (identify pain) in MEDDPICC. The more pain, the more motivation. The more motivation, the higher the probability is they close.

What Founders Should Do Instead

If you want to avoid becoming another AI company that quietly disappears, start with the problem, not the technology. Talk to customers long before your product feels finished and spend time understanding where they are losing time, money, or operational leverage today. Look for the problems that already have budget attached to them, the ones teams are actively trying to fix right now. Sometimes this process takes years to really get it dialed in.

Then build the smallest possible solution that removes that pain and try to sell it early. If people are willing to pay for it before the product is perfect, you are probably solving something real. If they are not, you just saved yourself months of building the wrong thing.

When the problem is real, companies move fast. They find budget. They bring in the right stakeholders. They prioritize the solution.

And when the problem is not painful enough, something else happens, the product gets pushed to next quarter. Projects stall, or the buyer loses interest.

The AI Extinction Event

Over the next couple of years the market will sort itself out. Thousands of AI products will launch, but most of them will struggle to find real demand.

Some will pivot. Some will get acquired for talent. Many will quietly shut down.

A smaller group will survive.

Those companies will share a few things in common. They will solve problems that actually matter. They will understand their customers deeply, and they will build technology that removes real pain instead of simply showcasing capability.

The AI boom is creating an incredible wave of innovation, but waves eventually break.

When this one does, the companies that survive will not be the ones with the flashiest demos or the most features. They will be the ones solving problems people truly need fixed, and a well oiled machine to predictably close revenue and scale.

That’s it for today, folks.

See you all next week!

Darren


P.S. If finding PMF and scaling to $1M in ARR through founder-led sales is on your radar, book a call with me here

💡 How We Can Help

Title: Why Your AI Demo Is Probably Showing Too Much

Read time: 3 min

Today I want to discuss something I have been noticing in a growing number of AI sales conversations.

The AI demo has become the new pitch deck.

Back in 2020-24, founders believed the path to closing deals ran through a beautifully designed slide presentation. Teams obsessed over the right narrative arc, the perfect screenshots, and a carefully curated set of product slides. The idea was that if buyers could see everything the product could do, the value would become obvious.

This is what we call selling. Throwing mud against the wall, hoping something sticks. We don’t want to sell. We want to solve. Big difference. You cannot solve unless you identify.

Over time that approach lost favor because the decks were terrible, and talked about them and how cool their product was, so founders gradually shortened their decks or abandoned them altogether. Yet the instinct that produced those decks did not disappear. It simply moved somewhere else.

Today it shows up in the product demo.

Instead of walking buyers through twenty slides, founders now walk them through twenty features. They open dashboards, run prompts, trigger automations, and demonstrate the full technical scope of their systems. The goal is the same as it was during the pitch deck era: prove the product is powerful.

This seems reasonable. AI products are genuinely impressive, but also look alikes of other wrappers. When founders see those capabilities operating in real time, it is easy to assume buyers will feel the same excitement.

Yet the pattern I have been seeing suggests something different is happening.

In many cases, the more product founders show, the harder the buying decision becomes.

When The Needs Are Great Enough, They Will Find Budget, Loop in The Right Stakeholders, And The Timing Will Be Immediate.

~Yours Truly

What Happens During Most AI Demos

A typical AI sales call begins with brief intros before the founder moves quickly into the product. Within minutes the screen is shared and the demo begins. The founder clicks through different tabs, triggers workflows, and demonstrates how the system generates outputs or automates a task.

Technically, it is impressive.

But if you pay attention to the buyer’s reaction, something interesting happens as the demonstration continues.

Early questions tend to focus on the problem. Buyers ask about how the product fits into their current workflow or whether it can handle a specific task their team deals with regularly.

As the demo progresses, those questions begin to change.

Instead of discussing the problem, buyers start asking about implementation. This is where a deals start to get lost.

• How long does setup take?

• What systems need to be connected?

• How accurate is the model in production?

• How much oversight does it require?

These questions reveal a shift in thinking.

At the beginning of the call the buyer is evaluating whether the problem is worth solving. By the middle of the demo they are evaluating how complicated the solution might be.

Believe when I tell you that changes the whole dynamic.

Why AI Demos Create Friction

AI products introduce a unique dynamic into sales conversations because they expand both perceived opportunity and perceived risk at the same time.

When buyers see powerful automation or analysis happening on screen, they understand the potential upside immediately, most of them will begin to speculate, imagine the hours of work it might eliminate or cost savings etc.

But adjacent to that excitement buyers begin imagining the operational effort required to make the system work inside their org.

They wonder who will manage the implementation. They think about data integration, process changes, and internal ownership. They imagine the consequences if the model produces incorrect results.

Every new feature shown during the demo adds another layer of potential complexity.

From the founder’s perspective, each feature strengthens the product’s value. From the buyer’s perspective, it expands the scope of the decision they must make.

Eventually the product stops feeling like a solution and begins to feel like a project.

Projects require planning. Planning requires meetings. Meetings slow decisions.

This is how impressive demos sometimes produce deals stuck in purgatory.

The Mistake Most Founders Make

The core mistake is simple. Most founders demo the product instead of the problem.

They show dashboards, automation flows, model outputs, integrations, and reporting capabilities. Each feature receives a few minutes of explanation before the next one appears.

This is what I call a tour of the system.

Buyers do not purchase tours. They purchase outcomes.

What buyers need to see is not the entire platform but the removal of a specific pain point they already recognize. If the demo does not remain anchored to that pain/use case, the product begins to feel abstract.

When that happens, buyers typically leave the conversation impressed but uncertain. And uncertainty rarely leads to confusion, indecision, stalled deal momentum and eventually death.

A Simpler Way to Run AI Demos

The founders we coach who run the most effective AI sales calls follow a much simpler structure.

They begin with the problem and stay there longer than most teams do.

Instead of rushing into the product, they ask detailed questions about the current workflow. They want to understand how much time is being spent, how often the problem occurs, and what it costs the team to handle it manually. The first two slides of our product deck are (1.) Current situation and (2) key objectives. We spend a lot of time before ever demoing the product on those two slides.

Once the pain is clearly defined, they demonstrate only the part of the product that removes that pain.

Nothing more.

Rather than walking through the entire system, they show a single workflow that replaces the task the buyer just described. The buyer watches the process run and sees the output appear.

The goal is to get the founders to pause and ask a simple question.

If this worked the way we just showed it, would it remove the manual work your team is doing today?

That question reframes the conversation.

The buyer is no longer evaluating a complex technology platform. They are evaluating the removal of a specific problem.

Making The Demo More Effective

For most AI products, three demonstrations are enough.

Each should correspond to a problem the buyer described earlier in the conversation. Each should show a single feature that addresses that problem. And each should end with a discussion about the outcome rather than the technology.

This structure keeps the conversation anchored in value instead of drifting into technical complexity.

When demos follow this pattern, the tone of the conversation begins to change. Buyers stop asking detailed implementation questions and start asking practical ones.

• How quickly could we roll this out?

• What would pricing look like for our team?

• Could we start with a smaller deployment?

These questions signal something important. The buyer has shifted from evaluating the product to considering adoption.

That shift is where deals begin to move forward.

The Real Purpose of a Demo

It is tempting to believe the purpose of a product demo is to showcase the sophistication of the technology.

In reality, the most effective demos I’ve seen and been on do something much simpler.

They help the buyer imagine their problem disappearing. That’s really it.

When the demonstration focuses too heavily on capability, buyers leave thinking about how complex the product appears to be. When it focuses on the problem being solved, they leave thinking about what life might look like without that problem.

AI products are powerful tools, but in sales conversations, power alone is rarely persuasive. Clarity is.

The founders who close the most deals are not the ones who demonstrate the most features. They are the ones who show exactly what matters, and then stop. Try it.

That’s it for today, folks.

See you all next week!

Darren


P.S. If finding PMF and scaling to $1M in ARR through founder-led sales is on your radar, book a call with me here

💡 How We Can Help

Title: The Feedback Loop That Drives Product–Market Fit

Read time: 2 min

Today, I will discuss the three-step process we use as a feedback loop to help clients reach 1 Million in ARR as quickly as possible.

The goal of our engagements is to do two things. (1) validate the hypothesis of what it is we built with our minimum viable product (MVP) and (2) find indications of product market fit (PMF) by actively asking people to buy your product. The byproduct of executing these two things will lead to finding indications or PMF and scaling to 1 million in ARR.

Achieving these outcomes is not about setting goals. It’s about building systems. The systems will help you achieve your objectives. This issue is designed to help you understand this system.

The most important thing to do if you find yourself in a hole is to stop digging.

~Warren Buffett

We’ll unpack three areas today. If you follow these closely and understand the execution behind each, you will be far ahead of the pack.

The 3 steps of the process are:

1. Theory

2. Application

3. Feedback loop

1. Theory (processes)

   Theory is about understanding the processes that need to be fleshed out at each step of the sales process, which has five steps. Let’s look at each step, and it’s objective.
   
   Step 1 = Generating consistent leads. Primary customer acquisition channels that are economical and will scale are email, LinkedIn, and content. This is by far the most important because of two reasons. (1) you need the reps and (2) without prospects to sell to, you won’t be in business for long.
   
   Step 2 = Discovery call and qualifying deals from leads into revenue opportunities. The idea of a discovery (qualification) call is to identify use cases and understand whether or not you have a solution to solve them. This is done through the BANT process.
   
   Step 3 = Demo. A demo shows the prospect how your product can solve the pain points they conveyed to you on the discovery call. It’s showing them life before and after using your product. You present pricing and propose an offer to get them onto a paid proof of concept (POC). The offer you present should be guaranteed to deliver results, and if you cannot deliver, you will refund the price of the POC. The cost should be between 5-10% of annual contract value (ACV).
   
   Step 4 = Scoping. The goal of the scoping call is to drill down on the success criteria they want to see validated during a POC. It’s designed to benchmark clear success metrics on the POC so that, at the conclusion, there is a clear path to closing the deal.
   
   Step 5 = Closing. Closing is not something that happens at the end of the POC, it is a byproduct of all the steps that precede the close being executed correctly. Once the POC has concluded and all the success metrics discussed on the scoping call have been achieved, you will be ready to close. There can be some negotiations and concerns that need to be addressed at this point. It is critical to understand how to negotiate correctly to ensure you don’t lose the deal.
   
   This is the process or theory of sales fleshed out in five steps. There’s a nuance to this process where it can be condensed or increased. It’s contingent on vertical, deal size, market and how techinical the product is etc. But the above process is a good rule of thumb.
   
   

2. Application (execution)
   The process is applied by going out and executing on calls. You will typically have three types of calls (maybe four): discovery, demo, and scoping. If you are selling B2C, you will also have cold calls. The idea here is building the muscle through repetition. Repetition comes from new calls generated from outbound lead generation efforts (cold calling, email, LI, conf/events etc). This is why having top of the funnel (TOFU) dialed is imperative to the success of your process. You need many “shots on goal” to make the corrections and find indications of PMF.
   
   

3. Feedback (loop)
   The feedback loop involves recording all of your calls and reviewing them. We will tell you what you are doing right, what you are doing wrong, and what we need to do to iterate on the product based on what the market is telling us. This is how you get things dialed in quickly.

Between the theory, application, and feedback, it creates an immersive feedback loop that allows you to ramp up quickly, find indications of PMF, and begin scaling. It is a science, but most importantly, it’s a system. You have to systematize your sales efforts very early on. If you do not, I assure you that your customer acquisition cost (CAC), churn, and burn rate on cash will be very high. What I’ve shared with you here today is the antithesis of that. Apply this system.

That’s it for today, folks.

See you all next week!

Darren


P.S. If finding PMF and scaling to $1M in ARR through founder-led sales is on your radar, book a call with me here

💡 How We Can Help

Title: AI Pricing That Scales And Close Deals

Read Time: 3 min

Today, I’ll show you how to think about structuring and presenting prices to potential customers.

The idea here is to think about how most people buy products and to set up your pricing in a way that reflects it. There are three primary things consumers are looking for when buying. (1) Value. (2) Options. (3) Cost.

In this issue, I will break down how to convey this in a repeatable way with more predictable results.

Low prices attract cheap customers with luxurious demands.

~ Mac Duke

There are 4 areas you want to think about when structuring and presenting price. Let’s unpack each.

1. Features

2. Tiers

3. Pricing

4. Presentation

Features
This is where you present the value of what each tier/plan will encompass. You want to clearly delineate the features to provide transparency and allow customers to make informed decisions based on their needs and budget. For example, a basic tier might include essential features such as access to the core product, basic customer support, and limited usage limits. As you move up to higher tiers, your features should scale accordingly, offering benefits like premium customer support, advanced analytics, customization options, higher usage ceilings, etc. This progression not only justifies the price difference between tiers but also demonstrates the added value customers will receive at each level. A good rule of thumb is your basic (first) plan should not have what most customers will need. The idea is to drive them to the middle plan, where 99% of the features will encompass the workflow they're looking to optimize. The premium plan is for customers who want the extra bells and whistles.

Tiers
The idea behind tiers is that people like variety, options, and choices. You structure the value in tiers so customers can see what they’re getting and match their needs with price and value. As explained earlier, consumers are conditioned to buy products in a specific way; anytime you deviate away from that conditioning, it can create bottlenecks or delays in your sales cycle. The ideal amount of tiers/plans is three. You can name them (standard, professional, premium) or whatever floats your boat. If you’d like to add an enterprise plan where the call to action is “contact us,” I’m ok with that, but I don’t think it’s necessary. Three plans, in my experience, is the perfect number.

Pricing
Pricing your SaaS is the tough part. You want to consider a couple of things. (1) is to obviously look at competitor pricing and be in the same neighborhood. (2) is to leverage psychological pricing strategies such as what I call “charm pricing” (e.g., $99 instead of $100) to make your prices seem more attractive, use price anchoring by placing a higher-priced tier next to a lower-priced one to enhance its appeal, and employ decoy pricing with a strategically placed middle tier to guide customers toward your most profitable plan. In other words, the goal is to be competitively priced vs your competitors, provide way more value in the features section, and drive them toward the middle plan. There is a lot of nuance in pricing, and it’s a process of testing.

Presentation 
How you present pricing is equally as important as the pricing itself. It needs to be done strategically. For example, you want to go through each feature and tier and make a recommendation. Watch and listen to my example here. 

Usage Based Pricing
Many readers of this newsletter are selling technical products, such as dev tools, that incorporate a usage-based pricing model, which can be tricky to convey. The idea is to set up tiers, features, and pricing in the same way as mentioned above. The only difference is that you would put ceilings in each tier with usage. For example, you could add something like 100 API calls/month and $0.10 per additional API call to each tier.

Below is an example of how to structure features, tiers, and pricing.

That’s it for today!

See you all next week.



Darren

P.S. If finding PMF and scaling to $1M in ARR through founder-led sales is on your radar, book a call with me here

💡 How We Can Help

Title: Closing different stakeholders during the sales process

Read Time: 2 min

Today I’m going to discuss how to close different stakeholders and decision makers who oftentimes join calls deeper into the sales process. This is a big one and is very much applicable with larger enterprise deals.

Whenever there are multiple decision makers (DM’s) involved in the buying process (which is 95% of the time), it is imperative that you identify who the DM’s are and their titles. Otherwise you will not effectively address the needs and concerns of all the stakeholders involved in the buying process.

This is why the qualification call is so important and where most deals are won and lost. The problem I see constantly are founders not identifying who the stakeholders are and how they make purchasing decisions for a solution like yours. Today we’re discussing the “A” in BANT. Authority.

The number one problem we see in early stage startups is founders not talking to users.

~Michael Seibel (former yc ceo/partner)

There are typically 3 stakeholders that are involved in the buying process.

We use they acronym B.U.T. to address each.

1. Buyer (person who writes the check)

2. User (the user(s) of the product)

3. Technical implementer (engineer)

Buyer
The buyer is the person responsible for cutting the check. This is typically the dept head (CTO, CISO, Head of RevOps, etc.) Their goal is to remove bottlenecks for their team and to provide the tools they need to be more effective. They Buyer needs to have buy in from the users that this will be 10x better than their current solution. The buyer’s chief concern is the economics (cost) and security. They need to be sold on how much better their team will be with this tech and how that correlates to predicting and achieving goals, KPI’s and OKR’s a lot faster.

User 
This is the person(s) who will be using your tech. The goal here is to show how much better their workflow would be with your tech. It’s conveying through your demo what life looks like now, and what it will look like after coming onboard. You do this by classifying it in 5 buckets.

1 - Desired outcome: What is their desired outcome when using your product?

2 - Speed: How quickly can you get them to start seeing success?

3 - Efficiency: How much better is your product then their current solution?

4 - Effort: How much effort is required? How heavy is the lift?

5 - Economics: How much is this going to cost; and is it worth it?

Technical Implementer
The technical implementer is responsible for setting up/integrating the tech into their existing stack. The easier and less effort it requires on their part, the better. They’re optimizing for effort and security. When pitching this stakeholder you should always convey, little effort, one on one support, and ease of setting up.

You want to have slides in your demo deck that speak to each one of the stakeholders and how it benefits them.

Key Takeaways

• Always identify all the DM’s and their titles.

• Each different stakeholder is interested in W.I.I.F.M.

• Use the acronym B.U.T. to address the different DM’s concerns.

• Effectively convey speed, outcome, effort, efficiency and economics.

That’s all for today folks.

See you all next week!

Darren

P.S. If you’re a Venture-Backed company interested in coaching, book a call here.

💡 How We Can Help

Title: How the market is exposing weak GTM

Read Time: 3.5 min

Today I want to talk about something that is starting to show up regularly, and why it’s becoming the defining failure mode for early-stage companies heading into 2026.

We’ve been doing this for close to nine years. Over that time, we’ve stayed tightly connected to the startup and venture ecosystem, worked with hundreds of founders, and built long-standing relationships with multiple VC firms. Because of that, we tend to see patterns early.

Over the last 90 days, we’ve been pulled into an unusually high number of portfolio situations where investors are concerned about revenue execution. These aren’t broken companies. Most have pretty strong products, capable teams, and real market interest. The issue is that interest isn’t turning into predictable revenue, and no one inside the company can clearly explain why.

What changed in late 2025 is not the quality of founders or ideas. It’s the tolerance for uncertainty. I believe capital is no longer underwriting ambiguity around how companies grow. If a startup can’t explain how it generates pipeline, qualifies buyers, and converts deals in a repeatable way, it’s now seen as execution risk rather than early promise.

That shift is subtle but decisive, and it’s why many companies that felt stable a year ago are starting to feel the squeeze

AI lowered the cost of building products. It didn’t lower the cost of convincing someone to pay for them.

~ Yours Truly

The environment founders are actually operating in

It’s important to be precise about what’s happening here, because a lot of founders internalize this moment as personal failure when it’s really structural.

Venture money is not drying up, but the way it is being deployed is becoming very different. Boards are more conservative about follow-on capital. Companies are expected to show evidence that they understand their own revenue mechanics before additional capital is committed.

The requirement s for at minimum finding PMF has gotten a lot stronger. Investors want to see control, more repeatable processes in place that work. They want to see that revenue outcomes are the result of a system rather than a series of “hail mary” wins.

Buyer behavior is also changing. Budgets are scrutinized more closely. Sales cycles are longer. Decision-making involves more stakeholders. I’ve written about this, but to reiterate a strong product alone is no longer enough to carry deals across the line. Without a clear sales motion, interest stalls, pilots linger, and deals do not close, predictably. There’s too much AI hype, and it’s difficult to distinguish real operators and products from the wannabes.

The combination of more disciplined capital and more cautious buyers exposes a specific weakness: randomness. When revenue feels unpredictable inside the company, it also looks unpredictable from the outside.

Why the lack of a sales process is now fatal

A sales process is simply a way to remove guesswork from revenue.

It answers basic questions that every serious company needs to answer clearly. Who is the buyer? What problem is urgent enough to pay for? How that buyer evaluates solutions? What conditions must be true for a deal to close? What consistently causes deals to stall or fall apart?

When those questions are unanswered, everything becomes speculation. Pipeline looks healthy but converts poorly. Revenue appears lumpy. Hiring feels risky.

From an investor’s perspective, this makes the company difficult to invest in. If revenue outcomes cannot be explained or predicted, capital becomes harder to justify internally. In the current environment, that uncertainty is no longer tolerated.

This is why companies without a real sales processes fleshed out are being hit hardest. And it’s not because these companies are not good, but because they cannot demonstrate control, repeatability. This is what matters now, more than ever. Just read all the insanity that is posted on LinkedIn and it’ll tell you where we are as a market.

What founders need to do in this market

The response to this moment does not involve more activity. It involves more clarity.

1. First, founder-led sales is non-negotiable at the early stage. Until a company reaches meaningful revenue scale, the founder must be directly involved in selling. This is not about hustle. It is about learning. Founders need firsthand exposure to objections, decision dynamics, pricing friction, and deal failure in order to design a system that works. It makes you a 10x better operator.
   

2. Second, the ideal customer profile must be narrowed. Many struggling teams attempt to sell to too many segments/verticals all at once. This diffuses learning and creates inconsistent outcomes. Depth in one buyer type creates leverage. Breadth creates noise.
   

3. Third, the sales motion needs to be written down, even if it is imperfect. How leads enter the system. How discovery is conducted. How qualification is determined. How decisions are made. Clarity matters more than sophistication at this stage. We use this doc to onboard our clients to understand what the buyer profile looks like who have already bought.
   

4. Fourth, sales hires should not be expected to invent GTM. Sales people are operators, not architects. Without a defined process, hiring sales adds cost without adding control. They will churn, almost guaranteed.
   

5. Finally, GTM should be treated as a system that is tested and iterated over time. Distribution is not a supporting function. It is a core capability.

Key Takeaway

What is happening right now is not a temporary correction. It is a maturation of expectations.

The companies that will succeed in 2026 are not necessarily the ones with the most impressive technology. They are the ones that understand how revenue is created inside their business and can explain it clearly to themselves, their teams, and their investors.

This requires discipline and focus. Letting go of the idea that sales will somehow take care of itself.

That shift is uncomfortable for many founders, but it is also an opportunity. Companies that build control early gain a real advantage in this market.

Where Rampd fits

This is the work we do at Rampd.

We help founders design and implement a clear, founder-led sales motion. We work alongside teams to define buyers, structure discovery, build qualification frameworks, and turn inconsistent pipeline into a repeatable system. The goal is not just growth, but confidence and control.

The increase in VC-driven intros is not accidental. Funds understand that in this environment, product alone is not enough. Execution matters, and sales is the mechanism through which execution becomes visible.

If the pressure feels higher right now, it’s because the goal posts have moved.

That’s it for today!

See you all next week.

Darren

P.S. If you’re a Venture-Backed company interested in coaching, book a call here.

Title: 6 Mistakes That Quietly Sabotage Founder-Led Sales

Read Time: 2.5 min

Today, I will discuss the most common mistakes I hear founders make on sales calls and how to correct them immediately.

On average, my team and I listen to about two dozen calls per week, with about 97% from founders. Over time, I’ve noticed the same patterns repeatedly sabotaging deals and diminishing a founder’s authority. Understand that prospects constantly evaluate you, assessing how you present yourself through your language, tone, confidence, and competence. Everything you say and how you say it signals your strength or exposes weakness. To close deals consistently, you must project authority and eliminate behaviors undermining your position.

The issue we work through with our founders is to identify what they’re doing wrong because they don’t know what they don’t know. The first thing we do when they come onboard is review their call recordings. And, without fail, the same patterns show up in every call. But once we highlight their specific mistakes, everything shifts; almost immediately, their calls start going differently.

The patterns that undermine you are often the ones you’re least aware of, but once exposed, they lose their power over you.

~ Jordan Peterson

Let’s look at six of the most common mistakes I hear.

1. Leading the witness.

2. Being way too agreeable.

3. Selling a product rather than solving a problem.

4. Asking rhetorical rather than open-ended questions

5. Doing Bio’s at the beginning of discovery/demo calls.

Leading The Witness
Leading the witness is giving them the answer before asking the question.

An example would be, "So what are you doing to generate business at the TOFU? Are you doing things like LI and cold outreach?" This is leading the witness. You’re giving them the answer. Don't do this. Ask a question directly, and stop talking. Don’t add commas. An example would be — “What are you doing now to generate TOFU?”

Being Too Agreeable

Saying things like: “aha, ok, yeah, right, I see”, etc.

You're trying to be agreeable, but in fact, you're conveying to the prospect, "Hurry Up And Stop Talking Because I Want To Share," and it's disruptive. Instead, don't say a word or make any gestures. Just listen. Everything you’re trying to convey to the prospect will come naturally if you are quiet while they’re talking, listen, and ask great follow-up questions.

Asking Rhetorical Rather Than Open-Ended Questions
Don't ask questions with yes or no responses. You're trying to extract info to understand. Don’t make it easy for them not to provide context.

Instead, begin questions with, “Help me understand..., Can you walk me through..., What has been your... How do you currently…”

Selling a Product, Rather Than Solving a Problem.
Throwing s**t against the wall and seeing what sticks is not selling. Asking well-crafted questions and unpacking their responses is the path to solving. Don't sell - solve.

The key to successful selling is first identifying the source of pain/frustration. This is done through asking questions and listening (i.e., discovery) Then, you can show them a path out of that pain (i.e., a demo.) If you try to sell them on your product as the right solution without first understanding their pain, it becomes tough to close deals.

Interrupting The Prospect when They Divulge Useful Info.
Don't interrupt prospects when they’re speaking. Let them flesh out their thoughts; often, they give you all the information you need if you just let them talk. There are cases where the prospect can go into left field. In this situation, you get them back on the path by asking a question. That’s how you regain control of the conversation.



Doing Bio’s At The Beginning Of a Call
Bio’s at the beginning of a call are arguably the most significant waste of time. No one cares. If they explicitly ask youabout your background or why you built the company, provide that context. Other than that, it’s completely unnecessary. You have 30 minutes to extract all the necessary information and schedule the demo. Every minute is precious. You have to use it wisely. Prospects are interested in one thing. Can you help me solve this problem so I can stop thinking about it? That’s it. The entire customer buying journey should be grounded in answering the question of how you will do so through a process. Do not share bios unless asked.

Key Takeaway
Correct these if you’re doing any of them. On a sales call, you’re always coming from a place of strength or weakness, whether you realize it or not. Prospects are sizing you up from the first to the last touchpoint. The small, unconscious habits stack up fast and signal competence or insecurity.

You don’t always want to show up like a golden retriever. Sometimes you need to show up like a pitbull. Know which moment you’re in. And if you don’t, get help.

That’s it for today!

See you all next week.

Darren

P.S. If you’re a Venture-Backed company interested in coaching, book a call here.

Title: How to know if your sales effort is actually enough

Read Time: 2.5 min

Today, we are diving into a structured framework for tracking sales progress and optimizing performance at every stage of the pipeline.

A lot of our readers are in the 0-1 stage so you really need to understand what is hitting and what’s not. Mapping and measuring everything early will put you on the path to stronger PMF and scaling ARR.

I’ve managed hundreds of salespeople, and the difference between a top-performing sales team and an average one lies in their ability to track, measure, and optimize their activities. Without clear visibility into what drives results, sales efforts are unpredictable, making diagnosing issues, improving efficiency, and closing more deals a nightmare.

I will share a framework for structured clarity by breaking the sales process into distinct, trackable stages. Instead of relying on speculation or approximation, we measure key inputs, such as outreach volume, meetings booked, and POCs, and connect them to tangible outputs, like conversion rates and revenue growth. 

What gets measured gets managed.

~Peter Drucker

This structured approach allows us to:

• Identify high-impact activities that generate the most engagement and conversions.
  

• Pinpoint friction points where leads tend to drop off so we can adjust strategies accordingly.
  

• Forecast revenue confidently, based on actual data rather than pulling numbers out of our a**.
  

• Optimize resource allocation, ensuring that sales efforts are focused on the highest-return opportunities.

We ensure that every lead is accounted for, every sales action is intentional, and every deal has the highest chance of success.

One of the biggest challenges in founder led sales is the lack of visibility, both in tracking leads and understanding performance bottlenecks. Too often, founders/reps invest significant time in outreach, follow-ups, and presentations, only to see deals stall without clearly understanding why.

This framework solves this by:

• Defining clear sales stages. Every lead and opportunity follows a structured progression, from first contact to closed deal, ensuring nothing falls through the cracks.

• We are implementing standardized tracking. Every interaction, email, call, meeting, and proposal is logged, giving us real-time insights into engagement and conversion.

• Providing actionable insights. By analyzing patterns in our pipeline, we can refine our outreach strategies, improve close rates, and shorten the sales cycle.

By systematically measuring each step, we can answer critical questions:

• Are we generating enough inbound interest?

• How quickly are we responding to new leads?

• Where are prospects dropping off in the sales funnel?

• What’s our close rate at each stage?

This framework isn’t just about tracking; it’s about creating predictable, scalable, and optimized sales processes that lead to PMF and clear paths to scaling ARR.

SALES STAGES AND REPORTING DOC CAN BE FOUND HERE.

That’s it for today!

See you all next week.

Darren

P.S. If you’re a Venture-Backed SaaS company interested in coaching, book a call here.

💡 How We Can Help

Title: The 2026 tactical guide to building your GTM

Read Time: 3.5 min

Today, I will discuss how we think about mapping our GTM for clients. A GTM can be a confusing term. The Acronym gets thrown around a lot, and there is a lot of confusion attached to it.

The simple way we define GTM is a roadmap to get your product into the hands of the right people who are ready, willing, and able to buy it, if you can show how it can solve their problems.

Let me share a use case from a call I was just on with a YC founder at 40k MRR. Her ACV is 15k. All her deals were closed through warm inbound and intros. She has tried cold outbound (LI, email), with no results, and now her inbound channel has dried up, leaving them stuck at 40k ARR. I asked her to walk me through her GTM, and she really didn’t have one. She’s got to this place by hustle and grit without a proper GTM, and now she’s realizing they need to do this right to scale to the next level.

This is not an isolated incident. It’s incredibly common. This is a textbook Rampd client use case.

The mistake we made was thinking that we could just ‘do sales’ when we needed to. In reality, sales is an engineering discipline; it requires building a system that scales.

~ Ben Horowitz

When it comes to GTM, I like to break it up into two sections.

1. Product

2. Sales

1. Product Build.

   • Are you solving a bum knee or a broken leg problem? The latter wins.

   • Can your customer afford your product? If not, price is the objection.

   • Do you know who your customer (ICP) is? This is part of mapping.

   • Are you building in a growing market or a saturated one? The latter is a race to the bottom. The former is how you build a moat.
     
     

2. Sales GTM.

   • How quickly is your “time to wow?” Customers want instant gratification.

   • How much more efficient is your product than what currently exists?

   • How much effort is required to onboard them? The less, the better.

   • What is the cost, and does the value justify the cost?

Now, let’s go a step deeper. For this issue, I’m going to focus on sales GTM. Let’s assume you built and shipped your MVP. There are preliminary things you need to understand as you GTM. Many of these will be speculative, but with a good approximation. We then test these with a sales process to validate if our hypothesis on both product, positioning, and ICP is accurate.

Let’s take a look at those questions and how we map this process out.

Foundations & Preparation

This is designed to establish a strong market foundation by clearly defining your target customers (ICP), their problems, and how you uniquely solve them. It ensures that your positioning, messaging, and marketing collateral are aligned before shipping.

1. Define Your Target Market & Buyer Personas

   • Identify the most valuable customer segments.

   • Understand their pain points, needs, and decision-making processes.

   • Develop customer personas to guide messaging and outreach.
     
     

2. Refine Positioning & Messaging

   • Craft a compelling value proposition that differentiates your company.

   • Address key customer concerns.

   • Develop messaging frameworks tailored to each customer segment.
     
     

3. Develop Core Marketing Collateral

   • Build a website and landing pages optimized for conversions.

   • Create sales one pagers, pitch decks, a quick loom video.

   • Develop thought leadership content (white papers, case studies, posts, blogs).
     
     

4. Establish Competitive Differentiation

   • Research where traditional methods and competing AI (tech) tools fall short.

   • Highlight how your company has a unique advantage in your market.
     
     

5. Set Up Tracking & Analytics

   • Implement tools to measure website engagement, email outreach, and conversion rates.

   • Define key performance indicators (KPIs) to track early traction.
     

Value Props

This is designed to create high-quality marketing and sales collateral that effectively communicates your company’s unique value to potential customers. The goal is to ensure consistent, dialed-in messaging that resonates with the verticals/markets you service.

1. Speed: Faster Execution, Smarter Decisions

   • Automates specific processes that your product improves.

   • Cuts (ask or process) time by X–Y%.

   • Processes (specific data type) in (timeframe), reducing delays and improving efficiency.

2. Accuracy: Reducing Errors & Improving Reliability

   • Reduces manual errors by X–Y%, ensuring high-quality output.

   • Cross-validates data from multiple sources for consistency.

   • Flags inconsistencies in (specific data type), preventing costly mistakes.

3. Compliance & Traceability

   • Provides complete data traceability and source-backed insights for confident decision-making.

   • Ensures compliance with (industry standards or regulations).

   • Generates customizable, editable reports that adapt to your workflow.

4. Security & Protection

   • Complies with (relevant security standards: SOC 2, GDPR, etc).

   • Offers on-prem, private cloud, or hybrid deployment options for data control.

   • Ensures end-to-end encryption to protect sensitive information.

5. Key Differentiators

   • Enables teams to handle X–Yx more (tasks, deals, transactions) without increasing headcount.

   • Identifies (opportunities, risks, and insights) that traditional methods might miss.

   • Delivers deeper, faster insights that provide a measurable advantage.

Customer Acquisition Channels

This is designed to launch and optimize customer acquisition efforts through outbound and inbound marketing channels. The goal is to generate TOFU, engage potential buyers, and drive conversions by executing a well-structured marketing and outbound campaign across multiple touchpoints.

1. Cold Outbound

   • Cold Email & LI Campaigns

     • Build a targeted list of high-value prospects.

     • Craft a mix of cold and personalized messaging addressing key pain points.

     • Implement a multi-touch follow-up sequence.

     • Track open rates, reply rates, and demo conversion rates.

     • Consistently update content by TLI (testing, learning, iterating).
       

2. Cold Calling

   • Develop a call script based on value props and industry pain points. If applicable. For some industries, cc is not suggested.

   • Know the prospect’s objections and how to crush them with rebuttals.
     
     

3. Content & Thought Leadership

   • LinkedIn Content Strategy

     • Post regularly on LI. Discuss industry trends, pain points, etc. You should be posting at least 3x a week.

     • Share white papers, success stories, and industry insights on the company page.

     • Make sure to comment and engage with the audience on your posts.
       

4. Podcasts & Media

   • Get on relevant podcasts.

   • Discuss real-world use cases/ pain points related to what’s happening in your industry.
     

5. Industry Groups & Associations

   • Join and engage in relevant industry groups. These are huge and untapped resources. This is a group of your potential customers.

This is how you begin mapping your GTM. We can unpack each of these and discuss it at length, but you need to be scrappy and go.

Here’s the thing about all of this. Without a repeatable sales process, much of this becomes almost useless because you won’t be able to consistently convert opportunities into paying customers. You might generate interest, book demos, and see engagement here and there from your ICP, but without a structured, scalable sales process, deals will fall through, follow-ups will be inconsistent, and revenue growth will be unpredictable. I see this play out frequently.

Rampd acts as the growth algorithm that takes you from founder-led sales to a predictable, scalable GTM motion. Think of it as shifting from a single-threaded process to a parallelized, multi-channel acquisition system, where outbound, inbound, and partnerships work in sync to drive pipeline velocity. This is how we roll.

If you’re ready, let’s get to work! Book a call.

That’s it for today!

See you all next week.

Darren

P.S. If you’re a Venture-Backed company interested in coaching, book a call here.

💡 How We Can Help

Title: Why pilots don’t close


Read Time: 2.5 min

Happy New Year! Hope everyone had a great holiday season.

Today, I am breaking down why pilots stall, drag, and end up in pilot purgatory. One of the biggest misses we see is skipping the scoping call, so no one is clear on what is being tested, how it will be judged, who owns it, or what happens if you actually deliver what the customer says they want.

Once that is locked, the pilot's objective is to demonstrate alignment with the customer's stated needs to validate. If you have no visibility into their expectations, how could you possibly hit the mark? You can’t. That blind spot is where pilots get smoked.

When we look under the hood, we see the same pattern among many founders. Deals look alive, but are barely moving. The team is grinding on setups and support for teams that have not really committed to anything. We have not identified a real problem, a clear metric, or a date by which the customer will reach greenlight, so it feels busy, but it is not really going anywhere.

When nothing is clearly defined, no one takes ownership. The customer says they’re evaluating. We say we are in a pilot. Nobody has agreed on what success is or what happens if we hit it, and that is how you end up in pilot purgatory.

There are old pilots, and there are bold pilots. However, there are no old, bold pilots.

~ E. Hamilton Lee

We had a client come on board in late October. One of their biggest issues was a bunch of deals that were stuck at the bottom of the funnel. One deal in particular had been running a $40k pilot since early April.

Several people were logging in, but no one was actively engaged. Light activity, no depth. The deal came in through an investor intro; there was never a real scoping call, no success criteria, and no clear owner on their side or ours.

So we reset it. We reached out to the team multiple times to schedule a call and clarify our status. On that call, we treated it like the scoping they should have done on day one. We drilled down into the specifics of the success criteria. If we were able to check all the boxes, were they ready to pull the trigger and commit? Then we set a simple plan: milestones, owners, review dates, and the next step for each box once it is checked.

We ran the pilot using specific criteria and validated it over 45 days. We are now nearing the end, and we’re almost 100% sure they will close.

Ultimately, the purpose of the scoping call is simple is to get painfully clear on what they want, what validation means to them, and then reverse-engineer the pilot around that. Once you know the target, you can design the pilot to lead them directly to that outcome rather than hoping they see the value on their own.

Let’s break down what this looks like.

3 Tactical steps you can use right now

Here’s how you want to think about running scoping calls to ensure success on the pilot.

1. Set the agenda and replay their pain

Open the call with a brief preamble and set the agenda.

For example, you can say the goal for today is to define what success looks like for this pilot, map how you will get there, and lock in next steps if it hits.

Then reiterate what you already know from your previous conversations in a couple of lines, so they hear their own story back.

You might say that last time they shared the main issues and what they are hoping you can help with…

Ask whether that is still accurate and whether anything has changed since you last spoke. This shows you actually listened and gives them a chance to update the picture before you begin discussing the pilot.
 


2. Get clear on success, ownership, and risk

Now, zoom in on the success criteria. Think in buckets. Make sure you nail these.

• Success metric:
  Ask what has to change or improve for them to call this pilot a win.
  

• What they are really validating:
  Ask what they want to prove first, whether that is performance, reliability, workflow, cost, or something else.
  

• Who owns it:
  Ask who owns this pilot on their side and who is on the hook for the result.
  

• How you will run it:
  Ask who is using it, how many people are using it, and what active usage looks like for them.
  

• Check-ins and friction:
  Ask when you should check in and if there is anything that could slow things down, like security, data, approvals, or integration work.

You want to leave this part with a real scoreboard, a real owner, and a short list of possible blockers. If you do not have those, you are not done scoping.

3. Turn it into a simple plan with dates and a decision point

Once success is defined, turn it into a plan they can see and feel.

Restate what you are committing to, both what you are doing on your side and what they are doing on theirs. Agree on the pilot window, with a clear start date, end date, and one or two key milestones in between.

Book two things while you still have them: the kickoff and the decision review at the end of the pilot. Tell them you will send a short mutual action plan that recaps success metrics, owners, dates, and how you will communicate, whether that is Slack, email, or something else they use every day.

When you hang up, nobody should be guessing what happens next or what happens if the pilot works. The path from try it to signed should already be on paper.

Key Takeaways

• Scoping calls exist for one reason: to define what a win actually looks like before anyone touches the product.

• If you don’t drill down on success, it’s very difficult to understand what will move the needle for them.

• You need a clear metric, a clear owner, and a clear timeline before you start a pilot.

• Every pilot should have a start date, an end date, and a decision meeting scheduled before it begins.

• If you cannot identify the boxes that need to be checked before the pilot begins, it’s not ready to kick off.

  
  

The pilots that turn into revenue are the ones where both sides agree up front what a win looks like, who owns it, and what happens when you hit it.

That’s it for today!

See you all next week.


Darren

P.S. If finding PMF and scaling to $1M in ARR through founder-led sales is on your radar, book a call with me here.

💡 How We Can Help

Read Time: 3 min


Today, I want to zoom out and share a year-end review of what we are seeing across early-stage startups, AI and SaaS, and the 79 companies in our own client base.

We have worked with 79 clients this year. Collectively, we estimate they have raised roughly $270M. When you combine that with Y Combinator’s year-end reflections and batch trends, a clear pattern emerges:

Product is no longer a sustainable moat by itself. The real land grab is distribution.

This issue addresses where the market is heading, why great products are being commoditized faster than ever, and what actually creates advantage going into 2026.

Many entrepreneurs who build great products don’t have a good distribution strategy… even worse is when they insist that they don’t need one.

~Marc Andreessen

The old game was simple. Build something impressive, get early traction, and then raise on vision and product quality.

That window is closing. In AI and SaaS, especially, the market has shifted:

Product velocity has been democratized. With modern tooling and AI, it’s never been easier or faster to ship something that looks good.

Differentiation doesn’t last. Whatever clever feature you build gets cloned in weeks, not years.

Investors are scrutinizing distribution. The questions now are:

• How do you repeatedly acquire customers?

• What’s your wedge?

• What’s your channel?

YC’s own patterns and commentary mirror this. More AI companies, more similar-sounding pitches, and more emphasis on real use cases, revenue, and GTM discipline. The bar is no longer “Can you build?” It’s “Can you repeatedly win?”

If you don’t adapt to this shift, you risk becoming the startup with a beautiful product and a shallow moat, easy to copy, hard to scale, and even harder to fund beyond the first round.

A theme I’ve seen a lot this year (and, honestly, I’ve fallen into it myself) is the gap between knowing that distribution matters and how time is actually spent week to week. A few patterns pop up again and again:

• Hiding in product work. Shipping is fun. It feels productive. It’s also much less vulnerable than going in front of customers and risking a “no.” It’s easy to spend more time in Figma and on GitHub than in real conversations with the market.
  

• Bouncing between channels. One month it’s outbound, then it’s content, then maybe some paid experiments. Because focus keeps shifting, no single motion gets enough time to turn into a true acquisition engine.
  

• Making AI the headline instead of the helper. Decks and narratives lean heavily on models, prompts, and AI-powered everything, but sometimes the basics, who we serve, what painful problem we solve, and how we reach them, aren’t quite as sharp.
  

• Handing off GTM a bit early. It’s tempting to hire a salesperson or a marketer to figure things out. But in the early days, much of the messy learning often needs to be founder-led before it can be handed off cleanly.

When those patterns stack up, what you see is a lot of shipping, a lot of activity, but not much compounding advantage.

And in this environment, a good product is not enough. Without a clear plan to repeatedly reach a specific customer segment through a reliable channel, it can feel like you’re running hard on a track where anyone can jump in beside you at any moment.

3 Fundamentals To Building in 2026

If I were building a new AI/SaaS company from zero in 2026, here’s where I’d put almost all my energy:

1. Ruthless ICP clarity and a painful problem. I’d spend as much time as necessary to answer, in one sentence:

   • We help (very specific persona) solve (painful, expensive problem) in (clear context).

   
   I’d validate that statement with actual conversations and closed deals, not speculation. Everything from product to pricing to narrative would be anchored in that clarity.
   
   

2. One primary distribution engine. Before obsessing over every feature, I’d choose one main acquisition channel and commit to it for at least a full quarter:

• Founder-led outbound

• Product-led growth with strong virality or collaboration

• Ecosystem, integrations, and marketplace distribution

• A narrow but powerful content or community wedge

The goal is to build a machine that can predictably turn time and money into pipeline, not chase every shiny growth hack.

3. A GTM operating system as serious as the product one. I would treat GTM like engineering, with weekly metrics and reviews, clear hypotheses and experiments, and fast iteration on messaging, pricing, and positioning.

Instead of saying we are trying a bunch of stuff, it would sound more like this:

Here is what we shipped this week for distribution, what we learned, and what we are doing next.

That is how you build a company where distribution is the product.

2025 In Summary

2025 made one thing crystal clear: (1) Building is easier than ever, and (2) standing out is harder than ever.

We saw it firsthand across our 79 clients and in the broader early-stage, AI, and SaaS ecosystem: capital still flows, but it’s gravitating toward teams with distribution discipline, not just clever technology.

As you head into 2026, ask yourself:

• Do I have a real moat, or just a good product?

• Do I know exactly who I’m for?

• Am I building distribution with the same intensity I bring to product?

This will be the last issue of the year. I’ll be spending the next two weeks with family and friends, recharging, and coming back sharper.

I’ll see you back in your inbox on Saturday, January 10th.

Happy holidays and happy new year to you all!!

That’s it for today.

See you all next year! 🍻


Darren

P.S. If finding PMF and scaling to $1M in ARR through founder-led sales is on your radar, book a call with me here.

💡 How We Can Help

Title: How to turn a verbal yes into a signed agreement


Read Time: 3 min

Today, I’m going to walk you through how to actually close a deal after you get the verbal yes.

We’re going to talk about building micro-closes into each stage of your sales process so deals keep moving rather than drifting into deal purgatory.

The focus here is simple: control, speed, and clarity. Clearly outline the next steps to make it easy for your prospect to follow through.

What I see a lot of is that the founder runs a great call. The prospect commits to moving forward. You hang up feeling pumped. Then a week goes by. Then two. Now you’re refreshing your inbox, wondering why the agreement still isn’t signed.

This happens because time kills deals. The longer the gap between excitement and action, the more likely people are to revert to their default behavior. Other fires show up. Priorities shift. That emotional energy they had on the call fades.

Founders do this with coaching all the time. They know they should get help with sales. They agree it’s important. Then they rationalize their way back into trying to figure it out alone because it feels familiar, even if it doesn’t work.

Your buyers are doing the same thing. If you don’t intentionally guide them from yes to signature, the default outcome is usually nothing.

It’s usually not a closing problem; it’s a next step problem.

They finish a strong call with something like: Awesome, I’ll send over the agreement, and then they hand all the control back to the prospect. There’s no deadline. No scheduled kickoff. No agreed timing.

And if the discovery wasn’t executed correctly, they have no idea what happens internally after the call. They don’t know who signs. They don’t know if legal needs to review. They don’t know how long procurement usually takes. So they’re following up on a process they don’t understand.

And because they don’t want to come across as pushy, they avoid direct questions about decision-making and timelines. That’s exactly how you lose control of the deal.

Remember this. If you let go of the prospect’s hand at any point, they wander off the path. Your job is to keep them on the path with clear, easy next steps.

Heading into 2026, your product won’t win on features alone. It’ll win on how simple, safe, and obvious you make it to buy.

~ Yours Truly

We brought on a client in August with a pipeline full of verbally committed deals that weren’t converting to signed agreements.

When we reviewed his process, we identified two huge gaps. First, there was no clear close at each stage of the funnel. Discovery calls ended with “I’ll send over some info.” Demos ended with “I’ll email you some options.” After the POC, the response was, “I’ll send the agreement tonight.” No scheduled next step. No date. No commitment on timing.

Second, he had zero visibility into the internal process. He didn’t know who needed to approve the deal, what legal or security requirements would apply, or what the typical timeline would be once the agreement was sent.

So we cleaned it up. We defined the close at every stage: disco → schedule the demo, demo → schedule the scoping call, scoping → schedule the POC, POC → schedule the kickoff. After the POC, he stopped ending with “I’ll send the agreement” and started ending with “Let’s lock in your kickoff date.”

We also added a few simple discovery questions to map the internal DM and procurement path up front. Within a couple of cycles, the same types of deals that used to take 45-60 days were now closing in under two weeks. Same deals, same buyers, just a tighter process and more control.

4 Tactical steps you can use right now

Here’s how to apply this immediately:

1. Define the close for every stage.
Don’t let calls end in a vague great conversation. Decide the goal in advance:

• Discovery → schedule the demo

• Demo → schedule the scoping call

• Scoping → schedule the POC

• POC → schedule the kickoff or go-live

If no calendar event is booked, that stage is not complete. Use a simple, low-friction close like:

Before we wrap, let’s lock in time for the next step so this doesn’t fall off your radar.

Then open your calendar and book it while you are still on the call.
 


2. Map their internal process early.
Use discovery to understand how decisions really get made. Add questions like:

Once you decide to move forward, what happens internally?
Who else typically needs to weigh in or approve this?
Have you purchased similar tools before? How did that process work?

This gives you a clear view of how the agreement will move through their system and who you may need to involve.

3. Turn the verbal yes into a dated commitment and connect it to the agreement.
When they say they are in, do not stop at sending the agreement. First, anchor a date:

Let’s lock in a kickoff date so we can get your team live. What day and time works best for you?

Once the kickoff is on the calendar, send the agreement with a clear timeline:

To keep this kickoff date, we will need the agreement finalized by a specific date. If anything does not match what we discussed, please let me know, and we will fix it promptly.

Now the agreement is directly tied to a moment they have already committed to.

4. Use missed dates as a signal, not a nudge to check in.
If the agreement is not signed by the kickoff date, assume there is a real blocker. Do not send a weak just checking in message. Instead, address it directly:

When timelines slip, it usually indicates a concern or internal change we have not yet discussed. What is going on on your end?

That is how you surface the real issue and either re-align or cleanly close the loop.

Key Takeaways

• Time kills deals. The longer a verbal yes sits, the colder it becomes.

• The real problem is usually the lack of a clear next step, not the lack of interest.

• Every stage in your funnel needs a defined close that ends with an invite.

• Verbal yeses should immediately be tied to a specific kickoff or go-live date.

• Agreements should be sent after the kickoff is scheduled, with a clear deadline.

  
  

As we move into 2026, one of the biggest takeaways is this: product alone isn’t enough anymore. Sales and product are not competing with each other, but to your buyers, most tools look the same. The real edge now is the customer-centric buying experience, how easy you make it to understand, evaluate, and say yes. That’s almost impossible to do consistently without a repeatable sales process.

This is exactly what we build with founders inside Rampd: a simple, repeatable playbook that matches how your customers actually want to buy.

We’re scheduling 1:1 cohorts for January. If coaching and building a real sales playbook is on your radar for early Q1, book a kickoff call and see if it’s a fit.

To be blunt: if you’re super early and fully bootstrapped, this may be a stretch. If you’re venture-backed or have real revenue and need sales to stop being a heroic guessing game, you’re probably in the sweet spot.

Sales will be the great equalizer going into 2026. Teams with a clean buying experience will capture an increasing share of the land grab.

That’s it for today!

See you all next week.


Darren

P.S. If finding PMF and scaling to $1M in ARR through founder-led sales is on your radar, book a call with me here.

💡 How We Can Help