How to revive a stalled technology partnership
Diagnose silence versus conflict versus no owner, use a restart script, and know when to stop trying to revive a technology partnership.
Most stalled partnerships are not a fight. They are a calendar. Someone changed jobs, the build lost its slot, the launch happened and nobody owned the next 90 days, and both sides now assume the other went cold. A smaller number are conflict: credit, scope, a missed SLA. A third pattern is worse: there was never an owner.
Revival is a diagnosis, then one clean restart, then a timebox. It is not a charm offensive. If you cannot name why it stalled, your restart email will sound like every other "just circling back" they are ignoring. If you can name it, you can often put the thing back on a date. If you cannot, sunset is the professional move.
This post is the triage, the scripts, and the stop rule. Use it on partners you already signed or shipped, not on inbound you never qualified. Those need a no, not a revival.
The 60-second version
If you only read one section, read this one:
- Stall is a state you can see. No dated next step, no contact in 30 days, no movement on adoption or build. Do not wait a quarter to name it.
- Diagnose before you ping. Silence, conflict, and no owner need different restarts. A generic check-in helps none of them.
- One restart, written, with a specific ask and a date. Not a thread of nudges.
- Timebox the revival. Two weeks for a reply, one working session, 30 days to a visible move. Then decide.
- No owner on either side means you cannot revive the partnership. You can only find a person or stop.
- Conflict needs the issue in the first paragraph. Credit, scope, breakage. Do not bury it under warmth.
- Stopping is allowed. A clean freeze or sunset beats a zombie you ping twice a year.
Diagnose the stall
Write the last true fact, not the story you tell in stand-up.
When was the last reply from a named human. What was the last agreed next step. What is true in the product (build status, actives, errors). What is true in the CRM (deals, registration). Who owns it on paper. Those five answers pick the bucket.
| Pattern | What you see | What is usually true |
|---|---|---|
| Silence | Warm last meeting, then nothing. Emails read or ignored. | Lost slot, job change, launch hangover, no owner of the next step |
| Conflict | Tone changed, legal copied, a deal went weird, a ticket sat | Credit, scope creep, outage, competitive overlap, a public miss |
| No owner | Your contact left, or they were never the person who could staff work | The partnership was a conversation, not a role |
| You stalled it | Their last note is waiting on you | Do not "revive." Reply with the artifact they asked for |
Silence is the default. People over-diagnose conflict because it feels more dramatic. Check the simple causes first: did their partner manager leave, did your engineer slip the date without a message, did you ship and vanish. Partner communications problems look like relationship problems from the outside.
Conflict is real when someone can name the injury: a stolen registered deal, a competing feature, an outage customers are writing about. If you cannot name the injury, it is probably silence plus embarrassment. No owner is a structural stall. A discovery call that never produced a name, a kickoff with ten people and no DRI. You cannot restart a process nobody is paid to run. Find the person or stop.
Confirm you still want the partner. Re-score against the partner ICP and prioritization. Revival costs a slot. Do not spend it on a name that would not pass intake today.
Restart scripts (silence, conflict, no owner)
Send one note. Name the stall. Offer one next step. Give a date when you will close the loop if they do not reply. Write like GOV.UK: short, the reader first, no decoration.
Silence, after a shipped integration
Subject: Restarting [integration] with a 30-day plan
We shipped in [month] and the last dated step was [X]. I own this again on our side. I would like 30 minutes in the next two weeks to look at adoption, one joint customer or one enablement action, and whether we keep, freeze, or stop. If I do not hear by [date], I will assume freeze and take the listing off our active list. Happy to stay live if you still are.
Silence, during build
Subject: Need a yes or a pause on [scope]
[Scope] has had no movement since [date]. We can re-open a build slot for [window] if you still have an engineer and a reviewer. If not, I will close this as paused and we will not hold the slot. Reply with a name and a date, or with pause.
Conflict
Subject: Straight talk on [issue], then a decision
You flagged [issue]. Here is what I think happened: [two sentences]. Here is what we can do this week: [specific offer]. I would like a call before [date] to agree a fix or to freeze the motion until we can. I am not going to pretend this is still on track until we name it.
No owner
Subject: Who owns [partnership] on your side?
Our last owner was [name], who [left / went quiet]. We are still running [integration / referral] and I need one person who can speak for scope and deals. If you can name them by [date], I will book a restart. If you cannot, we will freeze so we are not pretending this is staffed.
Do not stack these with a long recap of how exciting the partnership is. They know. The lifecycle already had a pitch stage. This is operations.
If they reply, run a short restart meeting, not a new romance. 30 minutes: what stalled, what is still true, one bet for the next 30 days, owners, the kill date. Capture it in the same kind of note you would after a QBR. Then do the work.
If the stall was yours, lead with the artifact. Send the scope, the kit, the deal status, the patch. Then ask for the meeting. People revive faster for a completed action than for an apology.
The 30-day revival window
A revival that is still "getting back in touch" on day 45 is a stall with better manners. Use a tight window.
| Day | Your move | Pass / fail |
|---|---|---|
| 0 | Diagnosis written internally. Re-score. Decide it is worth a slot. | If it would not pass intake, skip to freeze |
| 1 | One restart note, one owner, one date | Sent, not a thread of nudges |
| 14 | Reply in hand, or a second note to a new human (manager, other team) | Still silence: prepare freeze |
| 21 | Restart meeting held, 30-day bet written | No meeting: freeze |
| 30 to 45 | Visible move: build unblocked, adoption action, or a deal step | No move: freeze or sunset |
Visible move means something a third person could see. A commit, a customer email, a registered deal, a listing fix, a named new owner. Another "great to reconnect" is not a move.
Escalate once, not five times. One new human, usually their manager or the person who owns the marketplace or the integration. After that you are chasing. When to hire partnerships does not include a full-time job of chasing ghosts.
While you wait, stop putting their name in decks as live. Internal freeze is allowed even before the public one.
When to stop trying
Stop when the diagnosis is no owner and none appears. Stop when conflict is named and they will not meet. Stop when the restart meeting happens and nothing moves in 30 days. Stop when re-scoring says you would not start this partner now. Stop when the cost of the chase is higher than the slot used on a waitlisted candidate who is actually answering.
Stopping is a written state: freeze (leave it running, no new work, listing maybe stays) or sunset (path off, dates, customers told). Use the sunset checklist if customers are still connected. Do not punish shared customers for a quiet alliance manager.
You can leave the door cracked without keeping a zombie. "If you name an owner in H2, we will re-score." That is enough. Be decent on the way out. Thank them. Do not recap their sins to a wide CC. The same people rotate jobs.
Common mistakes, and the fix
Circling back without a diagnosis. The fix: write silence, conflict, or no owner, then send the matching note.
Nine nudges, no date. The fix: one restart, one deadline, then freeze.
Reviving a partner you would not sign today. The fix: re-score first. Nostalgia is not pull.
Restarting with a new scope to create energy. The fix: finish or kill the original motion. New scope on a stall is how you stall twice.
Keeping sales attached to a dead motion. The fix: internal freeze the same week you send the note.
Taking conflict personally and going quiet yourself. The fix: name the issue in the first paragraph and offer a call. Pride is not a strategy.
FAQ
How long before a partnership is stalled? If there is no dated next step and no contact for 30 days, treat it as stalled. Two quiet quarters is not a stall. It is a zombie.
Should we involve legal in a revival? Only if the stall is a contract fight or you are about to change terms. Most stalls are operational. Do not escalate tone by copying counsel.
What if their owner left and the new person does not know us? That is a no-owner stall. Send a one-page "what this is, what we need, here is the listing or the kit." Give them a date. They may be the best restart you get.
Can we revive with a webinar or a joint blog post? Not as the first move. Co-marketing on a stalled engine is decoration. Get an owner and a working motion, then maybe co-marketing.
What if we caused the stall? Say so, send the missing work, and ask for a date. Do not write a long apology with no artifact.
Is a freeze the same as giving up? No. Freeze is "not investing, still running for remaining users." You can unfreeze if an owner appears and the score still holds. Giving up without a state is how listings rot.
How many stalled partners should we try to revive at once? One, maybe two. Revival is a slot. Parallel charm offensives are how none of them get a 30-day bet.
When is conflict unfixable? When they will not meet, when the competitive overlap is now the product, or when trust broke in front of a customer and they want a hard exit. Then sunset cleanly.
Further reading
- Writing for GOV.UK for short, dated restart notes.
- When to sunset a partnership for the stop path when revival fails.
- Partner communications so silence is less likely next time.
- Partnership prioritization framework for whether the name still earns a slot.
- Partner QBR for the meeting you run if they come back.
The short version
A stalled technology partnership is silence, conflict, or no owner. Diagnose first, re-score, then send one restart note with a specific ask and a date. Give it two weeks for a reply and 30 days for a visible move. If there is no owner, no meeting, or no movement, freeze or sunset. Do not chase a logo you would not sign today, and do not revive with a webinar. Stopping well is part of running the list.
If you want a stall-by-stall pass on the current partner list, with revive versus freeze versus sunset, that is what a Partner Audit is for.