Account Reengagement Plan

Account Re-engagement Plan

Restarting a relationship is not selling, and treating it as selling is the failure this skill exists to prevent. The buyer already holds an opinion about the work. It was formed from an experience the seller may not have witnessed, it is often held by someone who was not in the room when the decision was made, and it is rarely the opinion the seller assumes. The default move, proposing the next phase, tests none of that. It arrives as a document about the seller's ambitions addressed to a person who has an unresolved question about the last engagement, and it is filed unanswered.

The cost is specific. A dormant account carries exactly one credible re-entry with a new stakeholder, and a premature proposal spends it, leaving something worse than silence: a documented reason to decline that the stakeholder can repeat to their own leadership. Meanwhile the account sits in the pipeline at a notional probability for four quarters, absorbing forecast attention it cannot repay. This skill enforces the reverse order, diagnose then rebuild the shared picture then propose, and where the diagnosis says not now, it says so and sets a date.

When to use this, and when not to

Use it when work was delivered and then stopped, when a phase was proposed and never signed, when a sponsor left and activity died within a quarter, when a renewal went quiet, when a new contact has inherited a relationship they did not build, when the last recorded interaction was an invoice, or when a client said "let's revisit in the new year" and the new year has arrived.

Do not use it on an account that was never worked. A company that has bought nothing is a prospecting problem, and outreach-email is the skill, because there is no shared history to diagnose and the whole method here rests on there being one. Do not use it inside a live sales cycle that stalled between two meetings, which is a deal problem handled in pipeline-deep-dive and sales-call-analysis. Do not use it for a healthy account approaching renewal on schedule, which is account management rather than re-entry. Do not use it where the relationship ended in a dispute, a termination for cause, or an unpaid invoice in collection: the commercial and legal position has to be settled first, and re-entry attempted while money is owed reads as a negotiating tactic.

discovery-to-proposal-deck takes over the moment the diagnosis is complete and the client agrees to a scoping conversation; it starts from discovery notes for one named client and produces the deck that gets the work approved. sales-roleplay runs the rehearsal this skill prepares the personas for. proposal-writer writes the document that follows, and never precedes the diagnosis.

What you need before starting

The engagement record. What was scoped, what was delivered, what was invoiced and paid, and the dates. This is the spine of the dossier and the thing most often held in one person's memory. Missing: reconstruct from invoices and the shared drive, and mark every reconstructed item as such. Do not present a reconstructed scope to a client as though it were the contract.

The stated objectives from the original engagement. What success was supposed to look like, in the words used at the time. This decides whether the later conversation is about value delivered or about a moved target. Missing: say so plainly in the plan, because an engagement with no stated objectives cannot be defended and should not be defended; move straight to the client's current objectives instead.

Evidence that the objectives were met. A measurement, a client statement, an adoption figure, anything a client could repeat to their own board without embarrassment. Missing: this is a finding, not a gap. An engagement with no evidence of outcome means the re-entry cannot lead with results, and the plan must say so in the diagnosis rather than assert value anyway.

The last recorded interaction, with date and participants. The dormancy clock starts here and it sets the whole approach. Missing: take the last invoice or the last calendar entry and label it as a proxy.

The current state of the client organisation. Leadership changes, funding, restructuring, acquisitions, a strategy shift, a new system programme. Use connected tools for firmographics, contact changes and news where they exist and ordinary web research where they do not; the unpaid version of this check is the company's announcements page and the professional profiles of the four people who matter. Missing: run it before drafting anything, because approaching a company that reorganised six months ago with a plan built on the old structure is the fastest way to look absent.

Who is still there. Sponsor, users, budget holder, and the person who inherited each role. Missing: assume turnover. Two years is long enough that assuming continuity is the riskier bet.

An honest internal account from whoever delivered. The delivery team knows what the commercial record does not: the meeting that went badly, the deliverable nobody opened, the scope argument in month three. Missing: ask privately and ask specifically what went wrong, because "how did it go" returns nothing useful.

The commercial position. Value delivered, the value of the paused scope, whether a master agreement is still live, and any agreed rate card or discount. Missing: check the agreement file before the first conversation, since a live master agreement removes a procurement cycle and changes what the smallest credible step can be.

The method

1. Set the dormancy clock and let it choose the mode. Count months from the last real interaction, not the last email sent. Under three months is a pause: continuity is intact, the same person reaches out, and the conversation can reference the work directly. Three to nine months is dormancy: assume the picture has changed, rebuild the stakeholder map, and lead with a catch-up rather than the work. Over nine months, treat the account as a new sale with an unusually good research advantage. The judgement call is which clock to use when an account was quiet but an invoice cleared last month; the rule is to use the last substantive conversation, because payment is administrative and proves nothing about attention.

2. Build the dossier, marking every hypothesis. Account, engagement history, the stop, the people, the commercial position, then an explicit open questions list. Every line is either sourced or labelled a hypothesis, and there is no third category. A hypothesis carried into a client conversation as a fact ("we understood budgets were reallocated") invites a correction that costs the seller the frame.

3. Write the diagnosis before writing any outreach. Name one primary cause from the table below, state the evidence for it, and design the first conversation to test it. Where two causes are plausible, choose the least self-flattering one the evidence allows and hold the other in reserve. This one rule prevents the most common error in the method, which is diagnosing budget when the truth was adoption.

4. Rebuild the stakeholder map from scratch. Do not edit the old one; build a new one, then compare. For each person: role now, relationship to the earlier work, what they are measured on this year, and what they would need to believe. Mark who is new, who inherited, and who has no memory of the original decision. A person who inherited a paused project inherited someone else's judgement and owes it nothing, which usually makes them more open than the person who made it.

5. Choose who makes contact, and from where. This follows the diagnosis and is a real decision. Sponsor departure: the approach comes from whoever has the longest tenure with the account, because continuity is the asset. Delivery dissatisfaction: someone senior who was not in the delivery team, because the first conversation has to be able to acknowledge rather than defend. Capacity or priority: the original owner, where familiarity helps. Weak access: the route in is a mutual contact, and the ask made of them is an introduction, not an endorsement.

6. Sequence the conversations, and write the actual questions. Five steps, in order, and the plan contains the words rather than a description of them. Reconnect, diagnose, reconstruct the picture, size the smallest credible step, agree the trigger. Detail in the section below.

7. Write the objection playbook for restart, not for cold sales. Restart objections are answered with curiosity rather than pressure, because most of them are questions about the past wearing the costume of an objection about the future. Two standing rules govern all of them. Never defend prior delivery before understanding the specific concern, since a defence offered before the complaint is stated confirms it was warranted. And treat every stall as a request for a smaller first step rather than for more persuasion.

8. Prepare the rehearsal. Two practice personas, each with an opening mood, the pains they actually feel, the objections they will raise, and one thing they will not volunteer until they trust the person opposite. Default pair: the inheriting stakeholder who is open but sceptical, and the executive who wants proof of return on the earlier spend. Rehearse particularly where the diagnosis is dissatisfaction, because that is the conversation people improvise badly.

9. Set the close-the-file rule before the first contact. Decide now what ends the effort: typically two substantive conversations with no named condition and no date, or three unanswered approaches across six weeks. When it triggers, write the account down to a dated review, record what was learned, and take it out of the pipeline. Setting this in advance is what stops re-engagement becoming a permanent activity with no result, and it is the part teams skip.

Deciding whether to re-engage at all

Not every dormant account earns a plan. Score three things before spending a day on one.

The rule: two weak factors and the account is not re-engaged, it is logged with a dated review and removed from the pipeline. One weak factor is workable, and which one it is changes the approach. Weak access means the first move is a route in through a mutual contact rather than a direct approach. Weak evidence means the re-entry cannot reference the earlier work as a success and must be built entirely on the client's current situation. Weak fit means the honest opening is a question about what has replaced the old priority.

Diagnosing why it stopped

Two evidence rules. A cause is only named where something in the record supports it, and "we assume budget" is not evidence. And where the client has stated a cause themselves, it is recorded as their stated cause and tested rather than accepted, because the stated cause is frequently the polite one.

The conversation sequence

1. Reconnect. Ask for a catch-up, not a meeting about the next phase. State the purpose honestly: to understand where things stand and to bring a new stakeholder up to speed. Fifteen to twenty minutes, requested by note or by phone, no attachment. An attachment at this stage converts a catch-up into a pitch and the reply rate falls.

2. Diagnose. Three questions do most of the work. What is your understanding of where this stands. What would have to be true for it to move. What has changed internally since we last worked together. Ask them in that order and let silence do its job after each. Take the answer to the second question down verbatim, because it becomes the acceptance criterion for whatever is proposed later.

3. Reconstruct the picture. Restate the original objective, then update it out loud against what has changed, and ask them to correct it. The output is a jointly owned current version, not a defence of the old one. Where evidence of outcome exists, it is introduced here, once, in a form the client can repeat, and then left alone.

4. Size the smallest credible next step. Propose the version that produces one visible result inside a quarter, not the full paused scope. The test of "credible" is that the client can name the person who would use the result and the date they would use it. Where an unexpired master agreement exists, say so, because removing procurement from the path is often worth more than a discount.

5. Agree the trigger. If it is genuinely not the time, leave with a named condition and a dated check-in: what has to happen, who will know it has happened, and when to speak again. A vague revisit is a decline with better manners, and recording it as anything else is how a forecast fills with accounts that will never close.

Worked example

Situation. A twenty-two person advisory firm had delivered a phase one operating diagnostic to Pellworth Group, a specialty chemicals distributor with nine plants, for 118,000 US dollars across four months. All figures in this example are in US dollars. The engagement closed in March, the sponsoring chief operating officer left in May, and the proposed phase two, an implementation scope worth about 240,000, was never signed. Fourteen months had passed and the account still sat in the pipeline at 30 percent. The master services agreement ran to the end of the following year. The last recorded interaction was a paid invoice in April; the last real conversation was a handover call in March.

Task. Decide within a week whether the account was worth re-engaging and, if so, produce a plan the account lead could execute the following month. Good meant either a first conversation booked with the successor or a defensible decision to close the file, and in either case an end to the account sitting at 30 percent.

Action. The first move was the wrong one and it cost three weeks. Reasoning that the phase two scope was already written and the relationship had ended on good terms, the account lead updated the old proposal, added a section on the client's new sustainability reporting obligations, and sent all thirty-two pages to the new chief operating officer. There was no reply, an out-of-office at two weeks, and silence after a third note.

The plan was restarted properly. The dossier took half a day and produced one fact that reframed everything: the dashboards delivered in phase one were in use at two of the nine plants. The figure came from the team member who had built them and had checked the usage logs out of curiosity in the autumn. It appeared in no commercial record, all of which described the engagement as successful.

That changed the diagnosis from sponsor departure to adoption gap, with sponsor departure secondary, and it explained the silence. The successor had inherited a diagnostic whose recommendations were visibly unused at seven of nine sites, so a proposal to spend 240,000 more read as a proposal to build more of something nobody had adopted.

The route in changed too. Direct approaches had already failed, so the plan went through a plant manager at one of the two sites that did use the dashboards, who agreed to introduce the conversation internally. The ask made of him was an introduction, not an endorsement.

The first conversation was a twenty-minute catch-up with no attachment. The second diagnostic question, what would have to be true for this to move, produced the sentence the plan then turned on: "I would need to see one plant actually running the way that report said it should before I spend anything more."

What followed was not phase two. It was a six-week adoption sprint at one named plant for 28,000, with a single deliverable, the plant's weekly operating review running from the dashboard and led by its own manager, and an acceptance criterion taken word for word from that sentence.

Result. The sprint was signed nineteen days after the first catch-up, under the existing master agreement, which removed a procurement cycle of about six weeks. It ran, and the review adopted the dashboard. Four months later a rollout across five plants was signed at 165,000, less than the original phase two figure and on a longer timeline.

The account had been carried at 30 percent for fourteen months, weighted at 72,000, in a form that was never going to close. The lasting change was procedural: the firm added a usage check at ninety days after every delivery, because the single fact that unlocked this account was known to one team member and to nobody who managed the relationship.

A second scenario, where it goes differently

The same firm looked at Kestrel Instruments nine months after a training and enablement engagement paused. The dossier and the news check found a public announcement of an enterprise resource planning migration, an eighteen-month programme with a named executive sponsor and a hiring freeze on anything outside it. Two of the three original contacts were still in post.

The diagnosis was capacity, and the method behaved differently at almost every step. The re-entry route was the original owner, because continuity was an asset and there was nothing to acknowledge. The sequence stopped at step two: the diagnose conversation confirmed the migration would consume the operations team through the following September, and the person volunteered it without prompting. No picture was reconstructed, no step was sized, and no proposal was written, because proposing anything into a hiring freeze converts a warm dormant account into a declined one.

What was produced instead was the whole deliverable: a named condition, the migration reaching its second wave go-live; a named person who would know when that happened; and a dated check-in the following August with a note of what to ask. The account came out of the pipeline entirely rather than being carried at a nominal probability, which removed 90,000 of weighted revenue that was never going to land in the period.

What changed: the cause was timing rather than value, so the correct output was a trigger and a clean forecast rather than a sequence of conversations. Diagnosing "not now" accurately is a result, and it is the failure the first scenario paid three weeks to learn.

Output

One brief, in this order. It is a working document for the account lead, not a client-facing artefact, and nothing in it is sent to the client.

ACCOUNT RE-ENGAGEMENT PLAN
Account:        [name]        Dormant: [months] since [last substantive interaction, date]
Prior work:     [scope, value, dates]      Paused scope: [value, if any]
Agreement:      [master agreement live to date, or none]
Re-engage?      [yes / log with dated review]   Access / Evidence / Fit: [strong or weak, each]

Dossier. Account, engagement history, the stop, the people, the commercial position. Every line sourced or labelled a hypothesis. Ends with the open questions list.

Diagnosis. One primary cause, the evidence for it, the secondary cause being held, and the question in the first conversation designed to test it.

Stakeholder map.

Re-entry route. Who makes contact, why that person, and through what path.

Conversation sequence. Five steps, each with the actual questions and the artefact, if any, that goes with it.

Objection playbook.

Cover at least: the new stakeholder who does not know the history; internal change and change fatigue; the results did not match what we expected; budget priorities moved; wait until things settle; prove the earlier phases worked before we spend again; the team never adopted what was built; the scope is too broad to know where to start.

Rehearsal personas. Two, each with opening mood, real pains, objections, and the thing they will not volunteer early.

Close-the-file rule. What ends this effort, and the dated review if it triggers.

Failure modes

Proposing before diagnosing. The signature move, and the most expensive. Recognise it because a document exists before a conversation has happened. It spends the single credible re-entry and gives the new stakeholder a documented reason to decline. Replace the document with a twenty-minute catch-up request and no attachment.

Diagnosing budget because budget is comfortable. Budget blames nobody. Recognise it when the diagnosis has no evidence line, or when the evidence is a remembered remark. Take the least self-flattering cause the evidence allows and test it first.

Reusing the old stakeholder map. Recognise it when a name in the plan has no start date or current title beside it. Rebuild the map and compare afterwards; editing the old one preserves exactly the assumptions that need testing.

Leading with value delivered. Even where the evidence is real, opening on it forces the client to agree or argue, and a new stakeholder has no reason to agree. Introduce evidence once, in the third conversation, in a form they could repeat.

Defending delivery before the complaint is stated. Recognise it in the phrase "I should explain what happened with". A defence offered before the concern is voiced confirms the concern. Ask what specifically fell short, and write down the answer before responding to any of it.

Treating a stall as a persuasion problem. More proof, more case studies, a longer follow-up. Recognise it when the third message is longer than the second. A stall is a request for a smaller first step; halve the scope instead of doubling the argument.

The zombie account. Recognise it when an account has been in re-engagement for three quarters with no named condition and no date. It distorts the forecast and consumes the attention of the person least able to spare it. Apply the close-the-file rule and log the learning.

Approaching while money is owed. Recognise it by checking the ledger, which nobody does. Re-entry attempted with an invoice outstanding reads as a collection tactic and poisons both conversations. Settle the money first, separately.

Edge cases

Nobody from the original engagement is still at the client. This is a new sale with a research advantage, not a re-engagement. Keep the dossier for context, drop the shared-history frame entirely, and run outreach-email. Mentioning prior work to a person with no memory of it is a claim on a relationship that does not exist.

The client ended the relationship explicitly. Re-entry is possible but only after enough time and only through acknowledgement. The first conversation has one purpose, to understand what went wrong from their side, and it carries no ask at all. Where the ending involved a formal complaint, that route is closed until someone senior on the client side has changed.

The account is now a competitor's client. Do not assume it is lost and do not open with a comparison. Ask what they ended up doing and listen to the tense and the enthusiasm. The useful entry point is usually a gap the incumbent does not cover, and the honest position is a second supplier rather than a replacement.

The paused scope is no longer the right work. Common after a year. Say so first, plainly: what was proposed then would not be what we would propose now, and here is what changed. Retiring your own old scope buys more credibility than any case study, and it removes the client's easiest objection before they use it.

The client asks for a discount as the price of restarting. Treat it as a diagnosis signal, not a commercial one. A discount request at re-entry usually means the value of the earlier work is in doubt. Answer with a smaller scope at the standard rate rather than the same scope at a lower one, because the second option confirms the doubt and sets the rate for everything after.

There is no access at all and no route in. Two weak factors. Log it with a dated review and remove it from the pipeline. Sending a fourth message to an address that has not replied to three is not re-engagement, it is bookkeeping with hope attached.

Quality bar

• A named diagnosis with its evidence appears before any proposed scope anywhere in the plan.
• Every dossier line is either sourced or explicitly labelled a hypothesis, with no third category.
• The stakeholder map records who is in post now, with each person marked new, inherited or continuing.
• The first ask is a conversation of twenty minutes or less, with no attachment.
• The smallest credible step is sized to produce one visible result inside a quarter, and its acceptance criterion uses the client's own words.
• The re-entry route names who makes contact and why that person, tied to the diagnosis.
• A close-the-file rule with a date exists before the first approach.
• No claim about value delivered appears that the client could not repeat to their own leadership without support.

Adapting this to your context

The dormancy clock, the three-factor screen and the five-conversation sequence come from services and software firms of ten to a hundred people selling repeat engagements. The diagnosis table travels further than the timings do.

• The dormancy clock. Three and nine months suit a cycle where contact is monthly. Reset both from your own median gap between substantive conversations: an annual or grant-funded rhythm makes nine months normal; a monthly subscription makes three months terminal.

• The three-factor screen. Access assumes one named buyer who will take a call. Public sector and grant relationships often have none; the equivalent is whether you are on the framework when the next round opens, which is a date rather than a relationship.

• The smallest credible step. A paid sprint below the paused scope assumes you can sell one. Where procurement sets a threshold, the smallest step may be a workshop under an existing agreement or a place on the next bidder list. Keep the test: the client can name who uses the result and when.

• One owner per relationship. A solo practice cannot send someone who was not in delivery, so a dissatisfaction conversation has to be rehearsed.

• What not to change. The diagnosis is written before any outreach, and the close-the-file rule is set before the first contact.

Related skills

outreach-email handles the cold case where no engagement exists to restart, and writes the individual reconnect note once this plan has decided who sends it and why. sales-roleplay runs the rehearsal against the two personas this plan produces. discovery-to-proposal-deck picks the work up once the client agrees to a scoping conversation and turns the diagnosis into an approved engagement. proposal-writer writes the document after that, never before the diagnosis. client-economics-analysis sizes what the account was worth and what the smallest step is worth defending. pipeline-deep-dive owns the deal that stalled inside a live sales cycle, which is a different problem from an engagement that stopped after delivery.