Read time: 5 minutes

Welcome to the Succession newsletter where 2,000+ life science sales reps improve their skills in 5 minutes per week. If you’re getting value from these newsletters, we'd love it if you could forward it along to your sales colleagues. If you’re new here, subscribe below.

Succession Bio works with life science/biotech companies to help drive sales, licensing, and partnership opportunities.

We do this through market research to identify the right companies and people, craft scientifically credible messages, and then perform the outbound sales and marketing tactics on your behalf to facilitate meetings with the right people at the right companies.

Succession

• Specializes in life sciences/biotech (it's all we do!)

• Provides market research, messaging, and outbound sales/marketing services

• Facilitates meetings and opportunities with the right people at the right companies for our clients

• Sales training for teams of 10+ who want to find and close more deals with biotech and pharma

A lot of you sit in small teams where you have to wear multiple hats; finding the leads, writing the cold emails, running the discovery calls, managing the account once it signs, evening dipping into project managing the delivery, and answering the panicked email from procurement at 4pm on a Tuesday. 

Most of what we write about in this newsletter is the front end of all that work. How to fill the top of the funnel, because that's the bit most people get stuck on, and frankly, it's the bit most sales content obsesses over.

But the cheapest revenue you will ever build is the client who already buys from you, buying from you again. And the biggest thing that nukes that flywheel is when something goes wrong, and then you handle the going-wrong bit like an absolute arsehole.

Because eventually, something always goes wrong. Biology is biology, lab equipment breaks, people miss emails, someone in QC has a bad day, and an entire experiment goes in the bin. Welcome to working with humans and living systems. If you're in this game long enough, you will mess up at some point. You will be on the receiving end of an email that ruins your Thursday afternoon. The question is what you do in the short, medium and long term after it lands in your inbox.

There's a fairly famous bit of research from Harvard Business Review on this that's worth knowing about. Customers who go through a service failure followed by a good recovery end up more loyal than customers who never had a problem at all. It's called the Service Recovery Paradox, and it's been replicated across industries. The clients you have screwed up with, if you handle the recovery properly, are statistically more likely to stay, refer you on, and buy from you again than the ones where everything ran like clockwork. 

Counterintuitive, until you think about it. When nothing ever goes wrong, the client has no information about how you behave under pressure. The first time something does go sideways, they panic, because they have no idea whether you'll rescue them or make it worse. A client who has already watched you handle a mess properly knows exactly what you'll do next time, and they trust you because of it.

So today, we're going to talk about how to actually pull this off, how to handle the f*ck up, manage your client through the meltdown, and repair the relationship so it ends up stronger than it was before.

Right, let's get into it.

Why your client is melting down

Before we touch any frameworks, it helps to understand what's actually happening in your client's head when they fire off that furious email. Because if you don't get this bit, you'll respond to the wrong thing.

Nearly every client meltdown traces back to uncertainty, which leads to panic.

There's a bit of neuroscience behind why this lands so hard. When humans face uncertainty, the amygdala, the part of the brain that handles threat, treats ambiguity exactly like it would treat actual danger. The body floods with fight-or-flight signals, and your client's behaviour starts to look like some combination of urgency, panic, aggression, and micromanagement. None of that is them being unreasonable. It's a perfectly normal stress response to a situation where they feel out of control.

Two specific things happen to the brain in that state. Catastrophising and assumption-making. When we don't know the facts, our brain invents them, and they are almost always negative. Evolutionarily, assuming the worst is what kept us alive.

There are three root causes of the panic, and each one points to a slightly different fix.

Lack of visibility. They can't see the work happening. They don't know what the chemists are doing today, what's on the bench, or where their compound is in the workflow. They fear things might be off track because they have no way to verify that they aren't. A client who hasn't had an update in forty-eight hours is, in their head, imagining their compound sitting untouched on a shelf somewhere.

Lack of clarity. They might know something is delayed, but they don't know why. "Delayed due to QC" can mean anything from "we ran a routine extra check" to "the data is wrong and we're trying to work out what happened." They don't know what the knock-on effects are. They don't know whether their project is permanently off track or just slightly behind. The gap between knowing something is wrong and understanding what it actually means is where most catastrophising lives.

Lack of control. They can't influence the timeline. They can't pick up the phone and speak directly to the scientists. They don't understand the internal workflow that takes their problem from business development to project management to the lab to QC and back again. Their fate is in your hands, and that lack of agency is genuinely stressful, especially if their own boss is breathing down their neck about timelines.

The meltdown isn't really about you. It's about a person who feels out of control, in the dark, and is panicking because of it. Which is good news, because it means there are specific things you can do to fix it.

ARTC: What to do in the first twenty seconds

Remember it as ARTIC, because it cools clients down.

Picture the scenario: You've just opened your inbox, there's an email from a client whose pre-clinical data you've been working on. The subject line is "urgent - timeline concerns" and reading it, they're telling you they have an internal review on Friday, they haven't had a proper update in over a week, and they're worried the timeline they committed to internally is slipping. 

You don't actually know what's happened yet because you haven't spoken to the lab. You can't promise a fix, because you don't know what needs fixing. But you also can't ignore the email, because every minute you don't respond, they're at their desk inventing increasingly catastrophic versions of what's going wrong.

This is what ARTC is for. It's a four-step holding response that takes about twenty seconds to write, and it stops the panic spiral while you go and do the actual investigation.

Acknowledge. "Thanks for flagging this, I hear you."

Reassure. "Nothing suggests an issue at this point, but I want to confirm the details"

Timeframe. "I'll come back to you by 3pm this afternoon."

Close the loop. Actually follow up when you said you would. If 3pm comes around and you still don't have the answers, send a short note at 3pm saying so, and giving a new time frame. The follow-through is what builds the trust, not having the answer.

The whole point of ARTC is to reassure the client that you're listening, you're in control, and you're moving things forward, even when you don't have answers yet. It's the breathing space that lets you go and prepare a proper response without the client spiralling in the meantime.

A few red flags to avoid in this first reply:

• Waiting until you've got all the information before replying at all. Silence is what makes the meltdown worse. A short holding email beats a perfect one that arrives three hours later.

• Sending a wall of text. They're in panic mode and won't read it.

• Over-defending. Don't start blaming couriers, instruments, or the moon. They don't care yet.

• Over-apologising. Apologising for things you haven't confirmed yet signals guilt, not confidence.

• Promising timelines you can't control. Commit to next steps, not outcomes.

The 3R apology framework: The structured response

ARTC stabilises the moment, but it doesn't fix anything. What you do next depends on what's actually happening underneath the panic, and there are two common scenarios. There's a different framework for each, and you pick the one that fits.

The 3R Apology Framework is for when there's a real failure on your side to own. You've spoken to the lab, you've got the facts, and now you need to deliver the repair. 

The instinctive thing to do at this point is lead with an apology. "I'm so sorry, we really messed up, let me explain what happened." It feels respectful and human, which is exactly why most people do it. It's also, according to the same Harvard research that gave us the service recovery paradox, the worst-performing way to handle a recovery conversation. When you lead with the apology, you've burned your most emotionally charged tool before you've done anything to fix the problem, and the client is left wondering what you're actually going to do about it.

Let’s take a a look at this in the case of a QC check failure that’s led to a failed experiment and delayed timeline.

Repair. State how you're going to fix it. Be specific and concrete. "We're going to rerun the assay with a fresh sample, and we're going to put it on our priority queue so you have data back by Friday." This is what actually matters to them, and it restores their sense of control because they now know what's going to happen next.

Reflect. Take honest ownership of your role in what went wrong, but don’t overcomplicate it with details about every step of your process. "What happened on our end was that the chemist queued the next step before reading the QC flag from the previous run, and that's a process gap we own." Being transparent and being accountable builds trust back, but overexplaining can confuse the client and could lead to misunderstanding and more issues.

Reassure. Tell them what you're putting in place so this doesn't happen again. "We're adding a mandatory two-person sign-off on QC results before the next step starts, to avoid this happening again in future." This is the bit that turns a single incident into a structural fix.

Then, and only then, you apologise. "I'm sorry this happened. We’re committed to ensuring this doesn’t happen again, and we’re working to ensure your project stays on track." By the time the apology arrives, you've already shown them what you're going to do to fix it, taken ownership, and prevented it from happening again.

Why this works at all comes back to the neuroscience. Certainty reduces anxiety. Structure restores control. Reassurance stops the client from filling the blanks with worst-case assumptions. 

The 3 Cs

Not every client crisis has a full-blown f*ckup behind it. Sometimes the client is on edge because they've lost visibility, they've gone too long without an update, they've heard something vague like "delayed due to QC" and assumed the worst, or they've called you in a panic before you've had a chance to investigate properly. Sometimes something has gone wrong, but you don't yet have the full picture, and a 3R apology would be premature.

In all of those cases, the goal in that moment is to calm the client down with what you actually know, show them someone is on top of things, and give them a clear next signal. That's what the 3 Cs are for.

A different scenario: imagine a temporary outage has affected your client's access to the data dashboard mid-project, and they've called you in a panic worried that data has been lost.

Clarity: what is happening, and what is not happening. The "what is not happening" half is the one most people miss, and it's the one that directly stops catastrophising. "We had a temporary outage that affected access to the data dashboard, but no data has been lost or corrupted." That cuts off about eight worst-case scenarios the client was already running in their head.

Control: ownership and immediate steps. Who's taking this on right now, and what they're doing in the next hour or two. "Our QC team is already cross-checking the affected files to verify integrity, and I'm on a call with the project lead straight after this one to discuss a solution."

Confidence: safeguards and next steps. What's in place to make sure this doesn't get worse while you work out the full picture, and when they'll hear from you next. "We've got it in hand, and I'll come back to you by 5pm with the verification results, and when we expect the data dashboard to be live again".

Used together, the 3 Cs answer the three questions the client's brain is already shouting at you in fight-or-flight mode: what's going on, who's handling it, and what happens next. If the situation turns out to be a real failure once you've investigated, the 3 Cs are what hold the line until you can deliver a full 3R follow-up. If it turns out to be a misunderstanding, a comms gap, or a piece of catastrophising rather than an actual f*ck up, the 3 Cs are the whole response.

Make the reassurance real (or you'll be apologising for the same thing twice)

Before you commit to a structural fix externally, there's some unglamorous internal work to do.

Triage whether this is a one-off or a pattern. Ask yourself honestly: if you'd run a hundred projects exactly like this one, how many would have hit the same issue? If the answer is just this one, log it and move on. If the answer is probably a few, you've got a structural problem, and the fix needs to apply across the board, not just to the client who happened to spot it first.

Get the right people in a room. Operations, project management, QC, and someone from commercial if there's a contract implication. Most root causes are cross-functional; the SOP didn't account for the edge case, the project manager's checklist didn't include it, commercial quoted a timeline that assumed nothing would go wrong. Keep asking why until you hit a process gap rather than a person.

Socialise the change properly. Update the SOP, train the team, brief new joiners, and check in three months later to confirm it's still being followed. A new process that lives only in a single Slack thread doesn't actually exist.

Close the loop with the client. Once the new process is live, go back to the client and walk them through concretely what's changed and why it makes the failure mode unrepeatable. "The contamination pre-check we promised is now running on every fresh sample before any assay starts, with a specific screen for the type of contamination we saw on your project. This is what turns a verbal commitment in the heat of a recovery into something the client can point at later when their own boss asks whether the vendor sorted it.

Clients can tell the difference between a reassure that's been pressure-tested internally and one that hasn't. The next time something wobbles on their project, they'll either flinch or trust you, and which one you get depends entirely on whether the reassure you gave them last time turned into actual change.

The 3 layers of recovery

Once you've fixed the technical problem, it's tempting to mark the recovery complete and move on to the next fire. We tend to think of recovery as a single thing, but it actually has three distinct layers, and you need to recover all three before the relationship is properly back.

1. Technical recovery.

• Is the issue actually fixed?

• Are timelines stable again?

• Is the project truly back on track?

2. Emotional recovery. 

• Does the client feel heard?

• Has their stress dropped?

• Does their confidence in you feel restored?

Are they using "we" language again when they talk about the project, or are they still using "you" - as in "you need to make sure" rather than "we need to make sure"? Emotional recovery is fluffy and hard to put on a dashboard, but you can feel it. If conversations still feel slightly cold or stilted three weeks after the dust has settled, you haven't recovered emotionally yet, even if the project is technically fine.

3. Commercial recovery. 

• Are they willing to continue the partnership?

• Will they give repeat business?

• Will they advocate internally or refer you externally again?

If the technical and emotional layers are recovered, but they're not putting new business in front of you, the relationship isn't actually back. It might be polite, but polite doesn't pay anyone's salary.

So the rule is: don't congratulate yourself on a recovery until you can tick all three layers. And don't try to push for growth (new scope, follow-on projects, expansion conversations) until you genuinely have. If you're using growth as a form of compensation for the mess, or it feels like you're trying to monetise their pain, the client will smell it a mile off and the relationship gets worse, not better.

The 30-day rebuild

Once you've come through the immediate recovery and the project is back on track, there's a thirty-day window where you can either compound the trust you've rebuilt, or let it fade. 

Most teams let it fade, because the urgency has gone and the next fire is already burning somewhere else. That's a missed opportunity, and it's the difference between a client who renews and a client who drifts.

What you want in those four weeks is a light, deliberate rhythm that reminds the client you're paying attention, the fix is holding, and you're worth giving more business to. Six moves to rotate through:

• Mini check-ins. "How does everything feel from your side this week?" Focused on temperature rather than status. Keep them short and frequent.

• Confirm stabilisation milestones. "That second batch hit purity spec on the first run, just so you've seen it." Concrete evidence the project is producing again.

• Share improvements made to prevent recurrence. "The new QC sign-off we promised is live, first one ran on your project yesterday." Shows the reassure step wasn't smoke.

• Offer optional calls. "Happy to review progress whenever suits, no pressure either way." Open door without forcing a meeting.

• Set a positive future focus. "Once this campaign wraps, do you want to start thinking about the secondary panel?" The softest possible signal that you're commercially open.

• Document small wins and regain momentum. Keep a running tally of what's gone right since the incident; milestones hit, deliveries on time, no further wobbles. "Three on-time handovers in a row and the new QC checks haven't flagged anything." Changes how the client remembers the relationship a quarter later.

One thing to try this week

Now this is hard to test in real-time (unless you’re unfortunate enough to wake up to a fresh disaster tomorrow morning). PLEASE don’t cause a f*ck up just to test it, but what you can do is pick one client who's had a problem in the last few months. A delayed delivery, a missed milestone, a quote dispute, anything that caused tension. Run a quick three-layer audit:

• Technical. Is the project genuinely back on track, or are there still loose threads hanging?

• Emotional. Are emails warm again, or still a bit off? 

• Commercial. Have they brought new work, expanded scope, or made a referral? Or have they gone quiet?

Pick the wobbliest layer and do one specific thing about it this week. A check-in call, a small win shared over email, a future-oriented question. Most of the time the intervention is small. The cost of not doing it is a relationship that slowly atrophies until you notice they've gone quiet.

If you can't tell where the gap is, just ask: "Hey, wanted to check in properly after the [X] back in [month]. From your side, is everything feeling like it's properly back on track, or is there anything still sitting with you?" Half the time the answer is "all good." The other half, they'll tell you something you weren't expecting, and you'll have caught it before it becomes a loss.

Take a look back at your comms during the issue, and run through the frameworks to see which one is the best fit and how you would handle it differently if the same thing were to happen again, so you’re ready for the next one.

The clients you've messed up with are not lost causes. Handled right, they're some of your most valuable accounts. The relationships that have weathered something difficult tend to be the most resilient ones in your book, because the trust has been tested rather than assumed. So the next time something goes wrong, and it will eventually, try to see it as the moment your best client relationship gets forged rather than the moment it ends. The data is on your side.

If you want help putting any of these frameworks into practice with your own team, whether that's a tailored training session on client recovery, retention, or the broader account management piece, we can put something together specific to where your team is now. Book a strategy call and we'll talk through it.

Apple Podcast | Spotify | YouTube

1. Lead Generation: We’ll build target lists, write scientifically relevant messaging, and send messages on your behalf to book qualified sales meetings with biotech and pharma companies.

2. Training for Teams: If you want to upskill your team around prospecting, driving to close, key account management, AI, or any other topic, we can put together a training plan specific to your organization’s needs.

3. Strategy Call: Need more than training? Want help implementing and executing your sales strategy? In a 30-minute call, we will assess your company’s current situation and identify growth opportunities.