Total Click Solutions

Category: business development

  • 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.

  • Cold Outreach Is Getting Worse. Try This Instead.

    Cold Outreach Is Getting Worse. Try This Instead.

    Cold outreach has always been a numbers game, but the numbers have turned ugly. Reply rates on cold emails now sit somewhere between 1 and 3 percent across most B2B sectors, and cold call success rates have roughly halved since 2024. You can run a well-crafted sequence, spend serious time on copywriting and targeting, and still have 97 out of every 100 people simply not respond. At some point it’s worth asking whether the game itself is still worth playing.

    The honest answer is: sometimes, but much less than most businesses assume. Warm outreach converts at a fundamentally different rate, with response rates of 18-25% routinely reported for warm contacts versus low single digits for cold. That gap isn’t a rounding error. It reflects something real about how people decide to trust a stranger with their attention and, eventually, their money.

    Why cold outreach stopped working so well

    Several things have compounded at once. Gmail’s spam filters now block close to 15 billion unwanted emails per day, AI-generated outreach has flooded inboxes to the point where anything that smells templated gets binned on instinct, and Google and Yahoo tightened sender authentication requirements through 2024 and 2025, meaning poorly configured domains often don’t reach a human at all.

    Buyers have also simply become better at filtering noise. Gartner research suggests B2B buyers are around 70% through their own evaluation before they engage a sales rep, so an unsolicited email landing before someone has even identified a problem they want to solve is more or less invisible.

    None of this makes outbound dead. It makes indiscriminate outbound expensive and slow, which is a different thing.

    What warm outreach actually means (and doesn’t)

    Warm outreach isn’t a tactic so much as a condition: you’re contacting someone who has some prior awareness of you, your work, or your name, however slight. That prior awareness does most of the heavy lifting before you’ve written a single word, because it short-circuits the instant-distrust reflex that kills cold messages. It can come from a shared LinkedIn connection, someone who commented on something you published, an event you both attended, a podcast appearance, or a mutual client who mentioned you in passing.

    The practical implication is that warm outreach isn’t a single channel. It’s what happens when you’ve done enough visible, useful work that some people already have a reason to reply. That’s the part most people skip, because it takes longer to build than a bulk email sequence.

    Building more warm opportunities without waiting years

    The most overlooked source of warm prospects is people who’ve already interacted with something you’ve put out: liked a LinkedIn post, downloaded something from your website, asked a question in a webinar, replied to a newsletter. These are signals, and reaching out within a short window after them, ideally within 72 hours, can lift response rates considerably because the context is still fresh. They remember the post. They remember thinking it was useful.

    Second-degree connections are also worth treating more deliberately. If a current client knows someone at a company you want to work with, a direct introduction moves that prospect from cold to warm in one conversation. This is specifically about making someone aware of you before you ever reach out directly.

    A smaller, high-quality warm list will almost always outperform a large cold one. Ten genuinely personalised messages to people who’ve had some contact with your work, each referencing something real and specific about them, will generate more replies than 200 templated emails to a scraped list. That’s not a philosophical position; it’s just what the conversion data has been showing, consistently, for the past couple of years.

    When cold outreach still makes sense

    Cold outreach scales in a way warm doesn’t, because warm is constrained by the size of your existing network and the pace at which you can create visibility. If you’re entering a completely new market where you have no presence whatsoever, some cold prospecting is the only realistic way to build an initial foothold. The key is treating it as a long game of building familiarity rather than expecting immediate replies, and being genuinely specific about why you’re contacting that particular person rather than sending something that reads like it went to five hundred people at once.

    The businesses that do cold outreach well in 2025 tend to use intent signals to decide who to contact and when: a company that just posted a relevant job role, or whose CEO mentioned a specific challenge on a public earnings call. That specificity transforms a cold email into something that at least reads as informed, which is a different category entirely from a generic pitch.

    So the simplest reframe is this: use cold outreach to expand the pool of people who know you exist, and warm outreach to actually convert. Conflating the two, and expecting cold contacts to behave like warm ones, is where most pipelines quietly stall.

    Frequently Asked Questions

    How do I turn a cold contact into a warm one?

    Engage with their content publicly before reaching out, get a mutual connection to make an introduction, or create something useful, a piece of writing, a talk, a newsletter, that they interact with first. Any of these creates prior awareness, which is all “warm” really means.

    Is cold email still worth doing at all?

    Yes, for scale and for entering new markets where you have no existing network. But keep expectations realistic: a well-run cold campaign in 2025 might generate a 3-5% reply rate at best, so volume matters, and highly targeted lists almost always outperform large generic ones.

  • How to Ask Existing Clients for Referrals

    How to Ask Existing Clients for Referrals

    Most businesses quietly agree that referred clients are their best clients, then do absolutely nothing to generate more of them. The problem isn’t a lack of satisfied customers; it’s that asking them to spread the word feels uncomfortably close to begging for a compliment in public.

    It doesn’t need to feel that way, and the fix is mostly about timing.

    Ask at the right moment, not whenever it suits you

    The single biggest mistake is treating a referral request as a task you get round to eventually, usually when you’re between projects and slightly anxious. By then the client has mentally filed you away under “sorted”, and your request lands like an invoice from a contractor they’d almost forgotten. The sweet spot is the moment a client has just expressed satisfaction, whether that’s a thank-you email after delivery, a positive comment on a call, or a glowing reply to a routine check-in. Enthusiasm is perishable, so act on it while it’s fresh.

    Wharton research has found that a referred customer can be worth at least twice as much over their lifetime as a non-referred one. That puts a rather different complexion on how much a single well-timed ask is actually worth.

    Be specific rather than hopeful

    “Let me know if you think of anyone” is not an ask; it’s an invitation to forget. People are genuinely willing to help, but they need a sharper prompt than a vague gesture towards their entire contact list. Tell them exactly who you’re looking for: “If you know any operations directors at mid-sized manufacturers wrestling with the same problem you had six months ago, I’d love an introduction.” That kind of specificity makes the client’s job easy, because they can picture a real person immediately rather than scanning a mental rolodex of everyone they’ve ever met.

    It also signals confidence. You’re not casting desperately into the void; you know your market and you’re growing it deliberately.

    Don’t conflate incentives with appreciation

    Financial incentives work well in consumer contexts, where a discount code fits naturally into the relationship. In professional services, they can quietly corrode the thing you’re trying to trade on, which is trust. A client who refers you because they genuinely rate your work sends a credible signal to their network. A client who refers you for a gift voucher is doing something that feels faintly transactional, and their contact may sense it.

    Acknowledging a referral warmly and promptly is almost always enough. A short personal note, or a follow-up letting the referrer know how the introduction went, costs nothing and tends to go further than most incentive schemes.

    Build the ask into your process

    If asking for referrals only happens when you remember, it won’t happen consistently. The businesses that do this well have made the ask a routine part of closing a project: a line in the wrap-up email, a question on the post-project review form, a standing item on the account review agenda. That way it doesn’t feel like a special favour you’re nervously requesting; it feels like a normal part of how your business operates, which is exactly what it should be.

  • You’re Probably Charging Too Little (And Ignoring It)

    Most businesses that know they’re undercharging carry on regardless. The price was set years ago, it hasn’t caused a walkout, and raising it feels like a confrontation nobody is ready for. So it quietly stays where it is, whilst inflation, rising supplier costs, and the extra hour you now spend on every client eat into what was never a fat margin to begin with.

    The clearest signs you need to raise your prices

    You’re winning nearly every piece of work you quote for. That sounds encouraging until you realise what it probably means: you’re the cheapest option, and price-sensitive clients are gravitating to you for exactly that reason, which isn’t the client base most businesses actually want to build. Charging too little compresses margins and can signal lower quality, and if you’re winning nearly every deal on price, you’re leaving money on the table.

    Your costs have risen but your prices haven’t moved. Supplier invoices, software subscriptions, energy bills, payroll: it’s easy to focus on the cost of goods whilst forgetting that overhead creeps up too. If those costs have risen over two or three years and your prices haven’t, you’re effectively cutting your own pay in slow motion.

    Your best clients keep telling you that you don’t charge enough. That one should be embarrassing, and it usually is. It means the people who understand the value of what you do have already done the maths on your behalf.

    How to raise your prices without drama

    Small, regular increases are far easier for clients to accept than a large jump every five years, which is what happens when businesses avoid the conversation for too long and then have to scramble to catch up. At a minimum, prices should be revisited annually. Even a 1% increase can lift net profit by around 12% on average, which is not a figure to scroll past.

    Give clients 30 to 60 days’ notice, explain the reasoning plainly, and resist the urge to apologise at length. A straightforward note saying that your prices are changing, when, and by how much is genuinely sufficient for most established relationships. Four hedging paragraphs don’t make it easier; they just make it weirder.

    If you have a mixed client base, it’s worth thinking about which services are most underpriced and starting there, rather than adjusting everything at once and giving people a reason to shop around.

    The psychology of what low prices actually signal

    There’s a widespread assumption that cheaper always means more appealing, but in many service categories, consultancy, design, legal, health, coaching, a suspiciously low price reads as a warning sign rather than a bargain. The market has absorbed enough dodgy-cheap experiences to be cautious. Set prices too low, and clients may quietly question whether you know what you’re doing.

    Pricing is a message. And if the message you’re sending is “I’m not entirely sure I’m worth more than this,” your clients will take you at your word.

    The businesses that wait longest to raise their prices tend to be the ones most anxious about losing clients, which is understandable. But the clients most likely to leave over a modest increase are usually the ones who take the most time, pay the latest, and push back the hardest on everything else. Losing them, whilst uncomfortable, is often quietly useful.

    Frequently Asked Questions

    How much should I raise my prices by?

    There’s no universal figure, but a small annual increase in line with your rising costs is far better than a large, infrequent jump. Review your actual costs first, then look at what comparable businesses charge. Even a 5-10% increase, applied carefully to your most underpriced services, can meaningfully improve margins without triggering significant pushback from established clients.

    What if I lose customers when I raise my prices?

    Some businesses have built a base of clients willing to pay a premium; others attract bargain hunters who’d switch to save a small amount. A modest, well-communicated increase rarely loses you the former group, and losing the latter often improves your margins anyway.

    Is there a good time of year to raise prices?

    Timing does matter. Business clients are often more receptive at the start of a calendar or financial year, and raising prices just before a busy season can work well. Avoid doing it immediately after a service problem or during a period when a client is already under pressure.