Reactivating Dormant and Closed-Lost Accounts
Your CRM probably contains companies that went quiet for reasons that may no longer apply. One had no budget. Another had just chosen a supplier. Some projects lacked an owner, while others simply lost priority. Your notes still hold that context, even if nobody has looked at the account for eighteen months.
A public change can give you a reason to look again. This guide shows which changes are relevant to common closed-lost reasons, what to verify before writing, and how to reopen the conversation while investigating whether a buying need exists.
Why your CRM history matters
A capital increase at a company you have never spoken to leaves many possible explanations. It could support growth or settle a balance-sheet problem. It might also fund something unrelated to your offer. You need more context before writing about it.
The same notice is more useful when the account went quiet over budget. Your CRM tells you what the company wanted and why the conversation stopped. The notice gives you a reason to check whether the budget constraint still applies. You still need to answer that question.
You also start with less research. Read the old notes and confirm that the people and project are still relevant. Then open the source behind the new event and check the evidence. That is a better starting point than qualifying the company from scratch.
Public changes that may justify another look
Start with the reason recorded in the CRM. A later public change is useful when it bears on that specific reason.
A capital change may justify revisiting a budget constraint. A relevant leadership appointment may change who owns the decision. Hiring, a new product page or a trademark filing may show that a paused initiative deserves another look. A merger may create a future review of suppliers and systems. In every case, the event creates a question that further evidence must answer.
Some loss reasons need a change on your side. If the product was a poor fit, return only when the relevant capability has materially changed. If trust broke down during the sales process, repair the relationship directly before you reopen the conversation.
Use the old CRM note and the new public record together. The table shows which assumptions may be worth checking and what evidence to look for next.
| Public clue | Old assumption to check | Check before writing |
|---|---|---|
| Capital increase | The project had no budget | Read the full notice. Check the form of the increase and look for related hiring, expansion or product activity. |
| Relevant director or signatory appointed | Nobody owned the decision, or the former sponsor left | Confirm the person's remit. Check whether the previous contact or blocker is actually gone. |
| Merger, acquisition or ownership change | The incumbent relationship may be reviewed | Look for integration milestones, leadership changes and evidence that the relevant systems or suppliers are in scope. |
| New branch or site | The company may have a new operational need | Confirm that the location is active and relevant to what you sell. A registered address alone is weak evidence. |
| Trademark filing | A project or offer may be moving | Read the classes and compare them with current products, roles and announcements. |
| Substantial website or product-page change | Positioning or product scope may have changed | Compare dated versions to establish when the change happened. Check related public sources to understand why. |
| Hiring in the relevant function | Ownership or capacity may be changing | Check whether the role is new or a replacement, and whether its remit overlaps the old project. |
Verify the change before you act
Most of what a register publishes about a company is administrative. A change of auditor, a new address on the same street, a statutory update after a change in company law, a correction to a previous entry: these say little about whether the company needs what you sell. Using one as the sole reason to write can make ordinary public information feel like surveillance.
Register entries are often republished when a detail is corrected, so the same change can appear twice with different dates. The later publication may repeat the first event. Job postings get duplicated across boards and reposted when they go unfilled, so a role you saw in March can look like fresh hiring in June. Open the original record and compare the underlying dates before treating a new publication as a new event.
Timing
Commercial-register changes reach the public with a lag. Across 305,902 SHAB records from a twelve-month window, the median gap between the effective date of a change and its publication is five days, and 38% publish within three (the same measurement as in monitoring a Swiss company for changes). The internal decision may predate the notice by more.
Treat the publication date as the date you learned the fact. Verify the event, check that your old notes are still relevant and write while you can ask a current question.
The useful window depends on the change. A live vacancy matters while the role is open. A leadership appointment can remain relevant through the person's first priorities. A merger may create several later moments, such as a new operating structure or a systems migration. Time your outreach to those concrete milestones.
What to write when you come back
Keep the message short because the earlier conversation supplies the context. Name the last conversation and roughly when it was. State the constraint that ended it in neutral language the recipient would recognise. Name the change you saw and where you saw it, with the date. Then ask one question about whether the original constraint still holds.
Subject: Has the operations project moved?
Hi Lea,
When we spoke last March, the operations project was on hold because its budget sat with the parent company. I saw the capital increase published in SHAB on 3 August and thought it was worth checking back. Has the budget position for that project changed, or should I leave it with you for now?
Best,
Marc
The message recalls the real constraint and names the public source. It asks one question and treats the link between the capital increase and the project as open. If Lea says the constraint remains, Marc has still received a useful answer and avoided forcing a new pitch.
If the source fits naturally, name it. "I saw the 3 August SHAB notice" is clearer than "I noticed some changes at your company" and lets the recipient check what you mean. Keep the reference brief. The email should focus on the earlier conversation, with monitoring limited to a brief source reference.
How Prospex fits in
Prospex lets you follow Swiss companies and see newly detected changes in one feed. Signals can include commercial-register entries, trademark filings, vacancies and website updates. Each item is dated and links to its source, so you can verify it against the notes in your CRM.
Automated classification can mislabel a signal, and private internal changes remain invisible until they appear in a public source. Contact history and the original loss reason still belong in your CRM.
Create a free account and follow the twenty closed-lost accounts you would most like to reopen.