Total Click Solutions

Author: Total Click Solutions

  • Why Your B2B Sales Cycle Is Getting Longer

    Why Your B2B Sales Cycle Is Getting Longer

    B2B sales cycles have been getting longer, and the uncomfortable part is that most teams haven’t noticed. A longer cycle doesn’t announce itself. It shows up as a forecast miss, a deal that was “almost there” for three months, or a pipeline that looks healthy until you look at the dates.

    Across a study of 939 companies, sales cycles have lengthened 22 percent since 2022. A team whose process hasn’t changed at all is closing later than it did three years ago, and that registers as a forecasting problem rather than a cycle problem, because nothing in the pipeline report says the clock moved. It’s a quietly expensive situation to be in.

    Where the time actually goes

    Much of a long cycle is time wasted on deals that should have been disqualified early. Tightening qualification does two things: it shortens the average by removing dead weight, and it speeds up the real deals because you understand what they need to say yes. Most pipelines are full of what you might call optimistic passengers, opportunities that were allowed in before there was enough evidence they belonged there.

    Bad qualification isn’t just failing to ask whether the buyer has budget. It’s failing to establish fit, urgency, authority, decision process, impact, timing, feasibility and risk. A long sales cycle often means the opportunity entered the pipeline too early, before anyone had done the work to treat it as real.

    The second culprit is stakeholder sprawl. Complex B2B buying groups routinely include up to ten decision-makers, which means a single champion is rarely enough to get a deal across the line. And yet plenty of reps spend weeks building a relationship with one enthusiastic contact who turns out not to hold the budget, the authority, or both. The most common source of late-stage delay is discovering in week eight that the person you’ve been selling to can’t actually approve the purchase. By that point you’ve both invested significant time, and backing up is awkward for everyone.

    The structural fixes that actually move the dial

    Map the buying committee early. Engaging all decision-makers simultaneously, a practice known as multithreading, keeps the process moving and prevents roadblocks later. This feels presumptuous to some reps, but buyers who are genuinely serious don’t tend to object. The ones who do are often the ones who were never going to close anyway.

    Be honest about pricing earlier than feels comfortable. Saving it for the proposal stage usually extends the cycle, because prospects who can’t afford your solution will say so quickly when pricing comes up early, whilst prospects who can afford it appreciate the transparency and stay engaged.

    And then there’s what happens after meetings. Delayed follow-up kills momentum and signals operational weakness. If a buyer asks for information and waits days for a response, you’re teaching them what it might be like to work with you. That’s not a minor inconvenience; it actively erodes confidence at exactly the point where confidence is being formed.

    Urgency you don’t have to manufacture

    One of the stranger habits in B2B sales is the artificial deadline: the invented discount that expires on Friday, the quota-driven push that the buyer can see straight through.

    Real urgency is considerably more useful and considerably more honest. It comes from tying your solution to something the buyer already cares about: a contract renewal, a compliance date, a growth target, a problem that gets more expensive every month it goes unsolved. Quantify the cost of waiting, and the timeline tends to take care of itself.

    None of this requires a new CRM, a new methodology, or a company-wide transformation programme. Adding more pipeline to a broken process scales the problem faster, not the revenue. The far more useful question is where your specific cycle actually stalls, and why. Fix that one thing, and the average moves.

  • Stop Relying on One Champion to Close the Deal

    Stop Relying on One Champion to Close the Deal

    The champion is not enough. They might be enthusiastic, politically savvy, and completely sold on what you’re offering, and the deal can still go cold the moment someone from finance asks a question they can’t answer. Every experienced seller has felt this, usually right before a deal slips into next quarter.

    Buying committees have been growing for years and haven’t stopped. Forrester’s 2024 research puts the median at eleven or more stakeholders, up from eight in 2018, and InfoSec, data-privacy, and vendor-risk reviews now routinely add weeks to enterprise deals even at mid-market accounts. The person who invited you into the process almost certainly doesn’t control all of those conversations.

    The logical instinct when you get a warm intro is to nurture that one relationship carefully before expanding. Establish trust first, then broaden out. It sounds sensible, and it’s exactly how deals stall, because while you’re spending six weeks deepening one relationship, the rest of the buying committee is forming opinions about your product from your website, your competitors’ outreach, and whatever your champion happens to mention in passing.

    Why single-threaded deals collapse

    The failure mode is predictable. Your champion goes quiet because they’re busy, pulled onto something else, or managing internal politics you can’t see, and suddenly there’s no momentum. Or they leave the company entirely, which, given how frequently people change jobs, is hardly an edge case. A multi-threaded deal survives that because several other people already understand the value you’re offering. A single-threaded one doesn’t.

    There’s also a subtler problem: the business case your champion builds will naturally cover their area of pain. Finance, IT, legal, and operations all have different concerns, and none of them are going to rubber-stamp a recommendation that doesn’t address theirs. The enemy usually isn’t a rival vendor. It’s internal friction you were never part of resolving.

    What multi-threading actually means in practice

    Multi-threading means building active relationships across the buying committee rather than relying on one person to carry the deal internally. The goal isn’t to flood an account with messages, which irritates everyone, but to make sure each relevant stakeholder hears something tailored to their specific concern, ideally before the formal evaluation stage, when opinions are still forming.

    Sequencing matters. Build a genuine champion first, then use that relationship to map the rest of the committee and get introductions rather than going around your contact cold. By the third or fourth touchpoint you should have names and roles for the economic buyer, the technical evaluator, and whoever is going to run procurement. These are not the same person, and they almost never want the same thing from a conversation with you.

    A practical way to think about it: your champion needs confidence to sell internally; your economic buyer needs a number that justifies the spend; your technical contact needs to know it won’t create new problems; procurement needs to know you’re not a compliance headache. A business case built across five stakeholders quantifies the cost of inaction in multiple functions, which is a considerably more compelling document than one person’s departmental pain.

    The CRM problem nobody talks about

    Despite all the evidence that multi-threaded deals close at materially higher rates, roughly 70% of B2B opportunities still have only one point of contact logged in the CRM. That’s not a coincidence. Single-threading is the path of least resistance: one relationship to manage, one inbox to track, one person to update. Expanding the contact map takes deliberate effort and a willingness to ask your champion to make introductions, which feels uncomfortable when the deal is still fragile.

    But the discomfort of asking for those introductions is considerably less than the discomfort of explaining in Q4 why a deal you had forecast as certain has gone dark because your contact moved to a different company.

    Frequently Asked Questions

    When should I start multi-threading, after the first meeting or later?

    As early as the second or third touchpoint, once you have a genuine champion. The common mistake is waiting until the deal feels advanced, by which point the rest of the committee has already formed views without your input. Use your champion to make warm introductions rather than reaching out cold.

    What if my champion doesn’t want me talking to other stakeholders?

    That’s worth paying attention to. A champion who actively blocks broader access is often signalling that the deal doesn’t have the internal support they’ve implied. It’s not always a red flag, but it’s worth a direct conversation about why, framed around making it easier for them to build the internal case.

  • Why Your Pilot Never Converts to a Contract

    Why Your Pilot Never Converts to a Contract

    A pilot that works perfectly and still doesn’t convert is a particular kind of frustrating, because everyone involved agrees it went well. The product did what it was supposed to do. The users liked it. Someone senior nodded approvingly in the debrief. And then nothing happens, except perhaps a vague conversation about “next steps” that leads to another pilot.

    This is pilot purgatory, and it’s far more common than it ought to be. The product is almost never the problem. The gap is almost always between “it works” and “someone with a budget has committed to buying it.”

    Why pilots stall even when they succeed

    Running a pilot and closing a commercial deal require completely different things from the buyer’s organisation, and most sellers only prepare for the first one. A pilot can be approved by a department head, staffed with a small enthusiastic team, and run on a discretionary budget. A full contract needs procurement, finance sign-off, an IT security review, and sometimes a board line. The champion who ran your pilot may have precisely zero influence over any of those people.

    There’s also a comfort issue that rarely gets named directly: a pilot is reversible. The buyer can run it, get a result, write a happy summary, and walk away having spent almost nothing, changed nothing, and committed to nothing. As long as the conversation stays in pilot territory, no one has to make a real decision. That’s not a technology problem, it’s a momentum problem, and it’s one that sellers inadvertently create by treating the pilot as the goal rather than as the first step towards a contract.

    The mistakes that guarantee purgatory

    The most reliable way to end up with a successful pilot and no deal is to agree to the pilot without agreeing on what success looks like, who decides next steps, and what the commercial path is once you’ve hit the milestones. If those three things aren’t defined before day one, you’ll spend the pilot collecting positive feedback with no clear trigger for conversion.

    A related mistake is choosing the wrong pilot customer. Interest alone isn’t enough. The buyer needs a problem that’s already costing them something real, an operational owner who will actually engage with your product week to week, and a credible path from a team-level trial to a company-level purchase order. Without that procurement pathway already visible, a glowing pilot result simply has nowhere to go inside the buyer’s organisation.

    Then there’s pricing. Many pilots are run for free or at a nominal cost framed as a gesture of good faith, which is often a mistake, partly because it signals that the full product might be negotiable, and partly because free things tend to get treated accordingly. Structuring pilot pricing to mirror your full commercial model, even at a reduced scope, does two things: it tests whether the buyer is genuinely serious, and it makes conversion to a paid contract feel like a natural continuation rather than a new and frightening commitment.

    What to fix before you start

    The conversion conversation should be agreed in writing before the pilot kicks off, not improvised after the results are in. That means getting explicit answers to three questions: What does success look like in measurable terms? Who in the buyer’s organisation has the authority to sign a full contract? And what happens commercially on day 91 if those metrics are hit?

    Those questions feel a bit presumptuous to ask, which is exactly why most people don’t ask them. But a buyer who genuinely intends to buy isn’t put off by them. A buyer who is using the pilot to delay a decision, manage internal politics, or simply get free access to your product for a quarter will find them very uncomfortable, which is useful information to have before you’ve invested three months of delivery time.

    It also helps to translate your results into the buyer’s commercial language as you go, rather than presenting a technical summary at the end. Time saved in a workflow becomes a productivity case. A reduction in error rates becomes a risk argument that finance can follow. The person who ran the pilot may be persuaded already; the people who will approve the contract need the numbers in a form they recognise.

    One pattern that actually works

    The pilots that convert most reliably treat the commercial discussion as parallel to the pilot itself, not as something that begins when the pilot ends. Regular check-ins with the champion track progress against the agreed metrics, and about two-thirds of the way through, someone from your side asks directly whether the results so far are building the case internally, and if not, what’s missing. That conversation surfaces blockers early enough to do something about them, rather than discovering in the final debrief that procurement was never looped in.

    The final review meeting should close with a date on a decision, names attached to accountability, and a clear commercial next step. Left vague, further evaluation almost always extends the uncertainty rather than resolving it.

    If you find yourself running pilot after pilot with the same type of customer and seeing low conversion across all of them, the issue is almost certainly structural: either you’re targeting buyers who lack the internal authority or budget pathway to proceed, or your pilot process is optimised for delivery rather than for commercial conversion. Those are genuinely different things that require different people and different instincts to manage well.

  • Your Discovery Call Is Killing the Deal

    Your Discovery Call Is Killing the Deal

    Most discovery calls lose the deal before anyone mentions price. The rep arrives with a script, works through it dutifully, and finishes feeling like that went well, while the prospect is already half-switched-off and composing a polite “we’ll be in touch” email. The call was technically complete. It just wasn’t a conversation.

    The checklist problem

    The single most common failure is treating discovery like a form to fill in. Reps move from question to question without really processing what they’ve heard, because they’re already thinking about what comes next, and the prospect who came hoping to feel understood ends up feeling processed instead. The questions get answered, the boxes get ticked, and nothing of substance is learned by either side.

    The fix is genuinely simple, if a little uncomfortable: ask a question, actually listen to the answer, then ask a follow-up based on what you just heard before moving on. It sounds obvious, but it’s rarer than it should be, and prospects notice immediately when it happens.

    Pitching before you’ve earned it

    A rep does their research, gets excited about the fit, and can barely contain the urge to show off what the product does. So before the prospect has finished articulating what they actually need, the rep is already talking about features. Engagement quietly evaporates.

    A practical guardrail: commit to asking at least three open-ended questions before you mention a single product feature. Not because three is a magic number, but because it forces a pause long enough to actually learn something. If you catch yourself pivoting to pitch mode, stop and ask another question instead.

    Asking things you should already know

    Asking a prospect how many employees they have, or what tools they currently use, when that information is sitting on their website or LinkedIn, signals clearly that you didn’t prepare. Most buyers have done substantial research before agreeing to a discovery call at all, so arriving with questions about public information reads as lazy at best.

    A twenty-minute look at LinkedIn, Companies House, Crunchbase, and any recent press releases changes the entire tone of the conversation. You can ask about things that actually matter rather than things that are already written down somewhere.

    Not going deep enough when something interesting surfaces

    The prospect mentions something significant, something that might be the real reason they’re looking for a solution, and the rep nods and moves on to the next prepared question. The seed of the real problem gets passed over in favour of completing the script.

    When something interesting comes up, stay with it. “Tell me more about that” isn’t a sophisticated technique, but it works because it gives the prospect permission to keep talking. The causes, costs, and knock-on effects of a problem are almost always more revealing than the problem itself, and that’s where you find out whether you’re genuinely useful to them or not.

    Ending without a real next step

    Vague sign-offs are where qualified deals quietly go cold. “I’ll follow up with some information” isn’t a next step, it’s a postponement. A discovery call should end with a specific, calendar-confirmed action, whether that’s a demo, a proposal call, or a clear decision on whether to proceed at all. Without that, you’re both starting from scratch the next time you speak, assuming there is a next time.

    Summarise what you heard, check your understanding is correct, and propose a concrete next step before the call ends. That summary also shows the prospect you were actually listening, which, given how infrequently it happens, tends to leave a surprisingly strong impression.

    Frequently Asked Questions

    How long should a discovery call be?

    Most effective discovery calls run between 20 and 45 minutes, though the right length depends on deal size and how much ground needs covering. The goal isn’t to fill the time, it’s to leave with a clear picture of fit and a confirmed next step. If you’ve got what you need in 20 minutes, don’t keep going.

    Should I disqualify prospects on a discovery call?

    Yes, and it’s one of the most valuable things discovery can do. Disqualifying a poor-fit prospect early protects your time and theirs. Ask directly about budget, timeline, and decision-making authority. A clear no is a far better outcome than a lingering maybe that blocks your pipeline for weeks.

  • When to Walk Away From a Deal

    When to Walk Away From a Deal

    The pressure to close a deal has a way of warping your judgement. You’ve spent weeks in calls, exchanged dozens of emails, maybe even flown somewhere for a meeting, and now the thing that matters most is getting it done rather than whether it’s actually any good. That slow drift from evaluating a deal to just finishing it is how most bad agreements get signed.

    Knowing when to walk away isn’t a failure of persistence. It’s one of the most disciplined things you can do in business development, and it’s considerably rarer than it should be.

    The sunk cost problem

    The hardest part isn’t spotting a bad deal. It’s spotting one after you’ve already invested three months in it. Research from Kristina Diekmann at the University of Utah found that what a seller originally paid for something distorts both parties’ expectations in a negotiation, even when that original price has no bearing on the asset’s current value. The same logic applies to time: the six weeks you spent on a partnership proposal don’t make the partnership any better, but they absolutely make you less willing to abandon it.

    Harvard’s Programme on Negotiation makes the point plainly: what’s already spent is gone. Your BATNA, your best alternative to a negotiated agreement, should be weighed against what comes next, not what you’ve already put in. If you don’t have one before you sit down to negotiate, you’re essentially negotiating from hope rather than position, and the other party can usually sense it.

    Signals worth taking seriously

    A counterparty that keeps reverting to initial terms after you’ve agreed to move past them isn’t forgetful. They’re most likely testing how much you’ll absorb rather than genuinely trying to find workable ground. Slow responses and withheld information don’t typically improve once you’re actually working together.

    Terms that chip away at your margins in ways that feel small at first are worth adding up properly. A pricing structure that feels borderline acceptable on day one has a habit of becoming genuinely painful by month six, particularly if the deal ties up resource that could go elsewhere. The question isn’t whether you can tolerate the terms today; it’s whether you’d design them this way if you were starting from scratch.

    Desperation on your side is also a signal, even if it’s an uncomfortable one to notice. Deals made under revenue pressure tend to attract onerous conditions, because the other party can usually tell you need it more than they do. If you find yourself arguing yourself into a deal rather than being genuinely convinced by it, that’s worth pausing on.

    What walking away actually looks like

    It doesn’t have to be dramatic. Being clear about your reasons, keeping the door open, and staying professional costs nothing and occasionally results in better terms coming back the other way once the other party realises you meant it. Burning bridges over a deal you turned down is just a waste.

    The practical discipline is to define your walk-away point before negotiations begin, not during them. When you’re in the room and the pressure is on, your sense of what’s acceptable shifts in ways you don’t always notice. A written note to yourself about minimum acceptable terms, made before any conversation starts, is a genuinely useful thing. It doesn’t need to be a sophisticated document. It just needs to exist.

    And every deal that isn’t right for you is time and attention that isn’t going to one that is. That’s the real cost of staying too long at a table that isn’t working.

  • BANT vs MEDDIC: Which One Actually Fits Your Deal?

    BANT vs MEDDIC: Which One Actually Fits Your Deal?

    What each framework actually does

    BANT and MEDDIC are not two ways of doing the same thing. They operate at different stages of a deal and answer different questions entirely, so treating them as interchangeable options in the same debate is a reliable way to pick the wrong one.

    BANT, which IBM developed in the 1950s and which has shown a rather stubborn refusal to go away, covers four things: Budget, Authority, Need, and Timeline. It’s a quick triage filter. The question it’s really answering is whether a lead is worth your time at all, and you can usually work that out in a single discovery call. It was never designed to close complex deals, just to stop you chasing ones that had no realistic chance from the start.

    MEDDIC goes considerably further. It stands for Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, and Champion, and where BANT gives you a yes/no on whether to proceed, MEDDIC maps the entire buying landscape: who controls the budget, how the decision actually gets made, who inside the organisation is championing you, and what measurable outcome the prospect is trying to achieve. It’s less a checklist than a working model of the deal.

    The honest case for BANT

    BANT gets a lot of criticism from people who’ve tried to use it on enterprise deals it was never meant for, which is a bit like complaining that a penknife doesn’t fell trees. For high-volume inbound pipelines, shorter sales cycles, and transactional B2B deals where one person can say yes, it’s still genuinely useful. It’s also easy to teach, and that matters more than it sounds: a framework your whole team applies consistently beats a sophisticated one that only your best reps actually use.

    The limitation is real, though. BANT assumes a single decision-maker with clear authority, and that assumption breaks down almost immediately in any deal involving procurement, a buying committee, or a contract worth talking about. If you’re working a six-month enterprise cycle and asking only four questions, you don’t have a qualification process. You have a polite conversation.

    When MEDDIC earns its complexity

    The extra weight of MEDDIC pays for itself by surfacing the things that kill large deals late, which is always the worst time for them to die. A champion who turned out to have no real influence when the contract reached procurement. An economic buyer nobody had actually spoken to. Decision criteria that shifted halfway through because a new stakeholder joined the committee. MEDDIC forces you to confront these gaps early, when you can still do something about them.

    Teams that use it rigorously also tend to produce more honest forecasts, because “70% confident” stops meaning “I have a good feeling about this one” and starts meaning something concrete: the pain is articulated, the economic buyer is identified, the champion is genuinely engaged. That’s a different kind of certainty.

    Which one to use

    Most teams don’t actually need to choose one and abandon the other. The sensible approach is staged: use BANT early as a lightweight filter to decide whether a lead clears the basic bar, then shift to MEDDIC as the deal grows in size, complexity, and the number of people who have to say yes before anything gets signed. Your qualification standard should rise in proportion to what the deal is going to cost you to pursue.

    If your deals are mostly under £30,000 with one or two stakeholders and a short cycle, BANT is probably sufficient and MEDDIC would be overkill that slows you down without adding much. If you’re selling enterprise software with nine-month cycles and a procurement team in the mix, BANT alone will leave you with a pipeline full of deals that feel promising right up until they don’t.

    And whichever framework you use, the one thing to avoid is picking it because it sounds more impressive, then quietly abandoning it when the questions get uncomfortable. A qualification framework only works if you’re actually willing to disqualify people with it.

  • The Opportunity Cost of Saying Yes Too Often

    The Opportunity Cost of Saying Yes Too Often

    The sunk-cost trap

    Saying yes to every deal that crosses your desk feels productive, even virtuous, because at least something is happening. But filling your calendar with the wrong clients and half-fitted projects is one of the quieter ways businesses stall. The cost never shows up as a single line item. It disperses across missed deadlines, drained teams, and the good opportunities you didn’t have bandwidth to pursue.

    A lot of bad yes-decisions aren’t made at the beginning of a deal; they’re made somewhere in the middle, when you’ve already spent three weeks in conversations and it feels wasteful to stop. That’s the sunk-cost fallacy at work, and it’s remarkably easy to dress it up as professionalism. “We’ve come this far” is rarely a business reason. It’s just reluctance wearing a suit.

    The same logic applies to clients who are already onboard. If someone is costing you more in management time, emotional energy, and team goodwill than they’re generating in margin, that’s a loss, even if the invoice looks fine on paper. A busy pipeline full of low-fit work is not momentum; it’s drag.

    What a bad fit actually looks like

    It’s rarely obvious at the start. The clearest signals tend to be:

    • The scope of what they need sits well outside what you actually do well, and you’d be building something custom you’ll never use again.
    • The margin is thin enough that one revision round or a delayed payment turns the job into a net negative.
    • You find yourself hesitating during negotiation, not because of nerves, but because something about the terms doesn’t sit right and you can’t quite name it.
    • Every answer they need from you is urgent, but every decision on their side takes weeks.

    That last one deserves particular attention. A prospect who creates constant urgency on your side whilst moving slowly on theirs is telling you quite a lot about how the relationship will feel at month six.

    The real price of saying yes too often

    The opportunity cost is straightforward: you’ve already spent the capacity you’d need to pursue something better. When a genuinely good brief arrives, a well-aligned client with realistic timelines and a budget that reflects what the work is worth, you may not have the resource to take it on properly. So you either squeeze it in and deliver something mediocre, or you pass.

    There’s also a quieter cost to your team. Difficult, low-margin, or poorly scoped work tends to be experienced most sharply by the people actually doing it, and that accumulates into the kind of low-level exhaustion that’s hard to diagnose until someone hands in their notice.

    Getting comfortable walking away

    The practical version of this isn’t a complex framework. It’s mostly about deciding, before a conversation starts, what your actual non-negotiables are: minimum margin, the kind of scope you can genuinely deliver on, payment terms you can work with. Once you have those written down somewhere real rather than kept as a vague feeling, declining becomes significantly less fraught, because you’re not making a judgement call in the moment, you’re just checking against criteria you’ve already agreed with yourself.

    Turning something down clearly and quickly is also, counterintuitively, good for the relationship. A prompt and honest “this isn’t the right fit for us” is far less damaging than stringing someone along for a month before the whole thing collapses. People remember how you handled a no far longer than the no itself.

    The businesses that grow well tend to be choosy in a way that looks almost reckless from the outside. They decline things. They finish conversations early. And they have the capacity, when something genuinely good appears, to pursue it properly.

  • Your Pipeline Review Is Just a Status Update

    Your Pipeline Review Is Just a Status Update

    Most pipeline reviews are, if we’re honest, a form of theatre. A manager asks “where are we with Acme Corp?” and the rep reads back what’s already sitting in the CRM, unchanged since last Tuesday, while everyone nods. Nothing gets challenged, no decision gets made, and the deal hasn’t moved an inch by the time the call ends.

    The problem isn’t the people in the room. It’s that the meeting is trying to do three separate jobs at once and doing all of them badly.

    The three jobs a pipeline review keeps conflating

    A proper pipeline review does deal inspection: validating whether opportunities are progressing based on real buyer actions rather than the rep’s optimism. It does risk identification: spotting which deals are quietly stalling before they disappear from the forecast. And separately, it does rep coaching: helping someone think through a difficult stakeholder or a slow procurement process. These need different questions, different participants and a different frame of mind, so collapsing them into one undifferentiated fifty minutes means all three are done poorly.

    The fix isn’t a longer meeting.

    What deal inspection actually looks like

    The questions worth asking aren’t “what’s the status?” but questions the rep can’t answer on autopilot. Who is the economic buyer, and has the rep actually spoken with them, not just emailed someone who forwarded it along? What’s the compelling event that makes this a priority for the buyer this quarter rather than next? What is the agreed next step, with a specific date and a specific person attached to it?

    If any of those answers come back vague, that’s the signal. “They’re evaluating the proposal” is not an answer; it’s a holding pattern. A good manager follows the thread until something concrete surfaces: what exactly are they evaluating, who’s doing it, and when does it end? The discomfort of that kind of follow-up is precisely the point.

    The deals worth your time in the room

    Not every opportunity in the CRM deserves equal attention. A sensible structure focuses the sharpest scrutiny on deals closing in the current or next quarter, anything the rep has flagged as at risk, and recently lost deals, which are worth a brief post-mortem before everyone quietly forgets what went wrong. Genuinely early-stage deals can be noted and moved on from quickly.

    A sixty-minute session might reasonably give around twenty-five minutes to commit and best-case deals that need hard validation, twenty minutes to pipeline deals that need either acceleration or an honest conversation about disqualification, and ten minutes to a couple of recently lost opportunities where there’s something to learn. That leaves a few minutes for pipeline generation, which is easy to skip and shouldn’t be.

    Coaching doesn’t belong in the same meeting

    This is where a lot of pipeline reviews quietly derail. The manager notices a rep struggling with a particular deal and starts working through it with them, which is generous but shifts the whole room into a different gear. Coaching is a conversation about how the rep thinks and behaves; deal inspection is a conversation about what needs to happen next with a specific buyer. Mixing them means neither gets proper space.

    The practical answer is a separate one-to-one, weekly and owned by the rep, so the topics that surface are the ones actually blocking them rather than the ones the manager would think to raise. It’s a small structural change that makes both conversations substantially more useful.

    A note on CRM hygiene

    If the first ten minutes of every pipeline review are spent asking whether close dates are up to date or whether someone remembered to log a call, the system is doing the wrong job. Those checks can happen before the meeting, or be caught by a scheduled CRM audit that doesn’t require the whole team on a video call. The pipeline review itself should start with the data already reliable, so the conversation can be about what to do rather than what happened to have been entered.

    And it’s only worth running at all if the manager knows the deals well enough to challenge the rep’s version of events, and the rep knows that’s what’s going to happen. Without that mutual expectation, it really is just a status update with a fancier name.

    Frequently Asked Questions

    How often should a pipeline review be held?

    For most teams, every two weeks strikes a reasonable balance: frequent enough that deals don’t drift silently, but not so relentless that the team spends more time reviewing than selling. Weekly works for very short sales cycles; monthly is usually too infrequent to catch problems before they cost you a deal.

    What’s the difference between a pipeline review and a forecast review?

    A pipeline review is about individual deals and what needs to happen next with each one. A forecast review is about numbers: is the team on track to hit the quarter, and how confident are we in the commit figure? They can inform each other but work best as separate conversations, usually with different attendees.

  • New Market Entry: Why You Should Win One Deal First

    New Market Entry: Why You Should Win One Deal First

    Most companies planning a new market entry get the order of operations badly wrong. They write the business case, hire a country manager, build the deck, redesign the website, and only then go looking for actual customers. It’s a very tidy sequence, and it wastes an enormous amount of money.

    The problem with going in fully committed

    The instinct to look serious before you are serious is understandable. You want distributors, partners, and prospects to trust you. But what you learn from your first real customer in a new market will invalidate a significant portion of the assumptions in that business case, and it will do so within weeks. The sales cycle turns out to be longer. The procurement process involves a committee you hadn’t accounted for. The pain point you’re solving is real, but not the one you led with. The pricing tier that worked at home creates an odd silence here.

    Sales cycles in new markets commonly run 30-50% longer than domestic ones, which alone can make a six-month revenue plan look optimistic by the end of month two. Purchasing structures, budget priorities, and buying cycles all differ, and the pitch that landed perfectly in your home segment may arrive somewhere new to polite bafflement.

    What a proper pilot actually looks like

    The alternative isn’t timidity, it’s sequencing. Before you build infrastructure, run a deliberate pilot. Pick three to five target customers in the new market or vertical and try to win them before hiring a team. The goal isn’t revenue, not yet. The goal is to validate the positioning, the go-to-market motion, and the unit economics before committing budget to scale.

    In practice, this means closing one deal with a customer you’ve chosen because they’re representative of the broader opportunity, not because they happened to call you. That single customer will teach you more about the sales process, product fit, delivery, and customer success in that market than any amount of desk research.

    Then document everything obsessively: the objections that came up, the parts of the proposal that needed rewriting, the stakeholders who appeared late, the implementation snag nobody anticipated. Once you’ve closed them, nurture that customer towards a case study or testimonial. In a new market, established competitors benefit from long-standing relationships and a new entrant is, fairly reasonably, treated as a higher risk. One genuine local reference dissolves more of that scepticism than any marketing spend.

    The distributor question

    Many businesses shortcut the pilot by appointing a distributor and calling that their market entry. It can work, but it carries its own trap. A distributor accelerates access and compresses margins, trading speed for profit. And without clear accountability, you can end up paying for representation whilst performing the sales work yourself.

    A distributor who already has relationships in your target segment is genuinely valuable. But signing one before you understand the market well enough to brief them, set realistic targets, and hold them to those targets is just outsourcing your ignorance. Appointing a well-connected generalist can actually accelerate the most common go-to-market mistake, which is trying to serve too many segments at once, by giving it a veneer of progress.

    When to actually scale

    The signal to scale isn’t a calendar date or a board mandate. With proven positioning and a successful pilot behind you, your country manager or regional team arrives with a playbook to execute rather than a problem to solve. That’s the difference between a first hire who spends six months figuring out why no one’s buying, and one who arrives with a repeatable process and a reference customer to point at.

    A market entry built this way is slower to look impressive on a slide, but it’s considerably harder to get catastrophically wrong.

  • Before You Sign: Vetting a Strategic Alliance

    Before You Sign: Vetting a Strategic Alliance

    The failure rate for strategic alliances sits somewhere between 60 and 70 percent, which is remarkable given how enthusiastically businesses pursue them. Everyone agrees partnerships are a fine idea, and then a substantial majority quietly collapse within a few years. The problem is almost never bad luck. It’s that the groundwork wasn’t done before anyone picked up a pen.

    Why most alliances go wrong before they begin

    The most common explanation is deceptively simple: most alliances that fail should never have been started, because there was no genuine compatibility between the parties. Not a clash of personalities, not a bad contract, not market conditions, just two organisations that wanted different things and never properly checked whether they were aligned before committing. Research consistently points to the same cluster of causes: incompatible objectives, poor partner assessment, and a lack of executive commitment on at least one side of the table.

    Companies that approach alliances in an ad hoc, instinctive way report roughly a 20 percent success rate. Those that follow a structured process do considerably better. The structured approach isn’t complicated. It’s mostly just asking the right questions early enough that the answers can still change your mind.

    The questions worth asking before anything is signed

    What does each party actually want from this? Not what they say in the first meeting, but specifically: what does success look like in 18 months, and whose priorities take precedence when those definitions conflict? If neither organisation has written this down and compared notes, you’re already in trouble.

    Who will own this relationship day-to-day? One of the quieter killers of a strategic alliance is that senior leaders agree on the vision and then the whole thing gets handed to whoever has a spare hour. Companies with the best partnership track records tend to have a named person whose actual job is managing the alliance, someone with real authority and a budget, not a project manager carrying it alongside three other responsibilities.

    What does the other party’s history with partners look like? Ask directly whether they’ve been in alliances before, how those ended, and what they learned. A company that has dissolved several alliances isn’t automatically a bad bet, but the explanation matters. If the answer is vague, or they point the finger at every previous partner, that’s genuinely informative.

    How will you measure whether this is working? It sounds obvious, but a great many alliances that collapse do so partly because neither party agreed on measurable milestones at the start. Without a shared definition of progress, one side always ends up quietly concluding that the other isn’t pulling their weight, and resentment grows faster than revenue.

    What happens if one of you becomes a competitor? This is uncomfortable to raise early, but Cisco’s experience is instructive: its alliances with Motorola and Ericsson fell apart after acquisitions made them direct rivals, whilst its partnership with Microsoft survived because both parties were willing to limit the scope of their collaboration when competition grew. Building an exit or adaptation clause into the agreement from the start isn’t pessimism. It’s just tidiness.

    The thing most businesses skip entirely

    Before you assess anyone else, it’s worth being honest about what your own organisation actually brings. A good strategic alliance should mean each party contributing something the other genuinely lacks: complementary capabilities, market access, technology, distribution, whatever it might be. If you’re not clear on your own gaps and strengths going in, you’re not well placed to judge whether a potential partner fills them, or whether you’re both just hoping the other one will do the heavy lifting.

    The alliance that works is usually the one where both parties were a little nervous to commit, because they’d done enough digging to understand what they were actually getting into. That discomfort is, oddly, a good sign.

    Frequently Asked Questions

    How long should vetting a strategic alliance partner take?

    There’s no fixed timeline, but rushing it is the single biggest risk. For a substantive alliance involving shared resources or co-development, a few weeks of structured conversations, reference checks, and written goal-setting is a reasonable minimum. Larger commitments warrant proportionally more time.

    Do we need a formal legal agreement for a strategic alliance?

    Yes, even for relatively informal arrangements. A written agreement that spells out goals, responsibilities, how decisions get made, and what happens at exit protects both parties and, more practically, forces you to have conversations you might otherwise avoid until things go wrong.