“Just checking in” gives the client no reason to think differently about the relationship. An implementation partner usually has a better route back in: the client company has probably changed since the original project.
Start with what changed
Look for changes that could alter the operating assumptions behind the solution you supplied: new products, new locations, acquisitions, hiring patterns, leadership changes, regulation, customer mix, delivery model, pricing or new systems.
A change is not an opportunity by itself. It becomes useful when you can explain why it may affect the way the client now works.
Build a hypothesis, not a pitch
Suppose a client implemented CRM eighteen months ago and has since hired a Head of Operations, added a service line and increased delivery headcount. A weak approach is to pitch an operations module.
A stronger hypothesis is that the commercial system may still represent the old sales model while delivery coordination has become more complex. The next conversation can test that directly.
The purpose of research is to earn a better question, not manufacture certainty.
Separate evidence from inference
Write down what is public and established, what you infer from it, and what the client would need to confirm. This prevents account development from turning into elaborate speculation.
Re-entry should sound like the client, not the supplier
The best reason to reconnect is usually a concrete change in the client's business and a question about whether the old operating assumption still holds. That is more useful than announcing a new feature or offering a generic health check.
ProperBizFix works with implementation partners on account development research, commercial discovery and white-label requirements analysis.