They Signed the Contract, but Nobody Uses the CRM
When a Telegram industry group has someone complaining about a CRM that was bought and ignored, the opportunity is usually in data migration, permissions configuration, and user training—not in selling another tool.
You open Telegram every morning and scan the same few industry groups. Reposted articles, ads, job listings—most of it you scroll past without stopping.
This morning one exchange makes you pause.
Company IT Lead: We bought a CRM—a customer relationship management system—two months ago. Dozens of salespeople, not a single one uses it. Everybody still keeps their contacts in Excel. They say they’re “used to it.” My boss asks about adoption rates, and I have nothing to show him.
Group Member A: Was the sales director involved in the selection process?
Company IT Lead: He was. He signed off on it. But when implementation started, he said he was too busy to participate. All the data is still sitting in Excel, and nobody is taking ownership of moving it into the system.
(The conversation above is an illustrative composite used to demonstrate how to assess a potential lead.)
You do SaaS implementation business development. After a client signs the contract, your job is to get the system actually used by the people who need it. When you read this kind of message, what comes next?
“That client needs help” is the right instinct. But the more useful questions are: What kind of help, exactly? What specific things could you go in and do? And is anyone inside that company actually pushing for this to happen?
Three separate services hidden in one paragraph
Read the IT lead’s words again, this time as work packages. At least three distinct needs are visible, and each one can be scoped and quoted independently.
First: data migration. “All the data is still sitting in Excel, and nobody is taking ownership of moving it.” Dozens of salespeople’s historical customer records, contact notes, deal progress—even if you only migrate one year’s worth of data, the work breaks down into concrete steps: cleaning (standardizing the inconsistent formats people use in a spreadsheet), field mapping (telling the system that “Company” in Excel corresponds to the customer-name field in the CRM), and import validation (checking that nothing got lost or misaligned). This is a weeks-long engagement on its own.
Second: permissions and business-process configuration. The sales director signed the purchase but “was too busy” during implementation. What that tells you is that approval workflows, role-based permissions, and field-level access rules probably never got set up. Which sales levels can see which accounts? When does a quote need a manager’s approval? Without this layer configured, the first screen a salesperson sees is a blank page with no structure. There is no obvious next action for them to take.
Third: training and habit change. Dozens of people all saying they are “used to Excel.” A two-hour training session will not fix this. Someone needs to walk the sales team through real customer scenarios inside the system, answer questions like “Does leaving this field blank break anything?” and “Do I need to backfill my old records?” This kind of accompaniment-based implementation service can run anywhere from a few days to several weeks.
Three needs, all showing up in the same message. The question is: why did the current implementation provider not handle these?
The timeline tells you more than the complaint
Go back to the two numbers in the message: the contract was signed “two months ago,” and the system is unused.
Two months. If the current implementation provider started work right after the contract was signed and still has not completed data migration and user adoption after two months, the reasons could be internal—the sales director signed but never pushed his team to participate—or they could be about the provider’s own capacity and scheduling. From a single Telegram message, you cannot tell which.
What you can confirm is this: as of the time that message was posted, data migration and user adoption had not been completed. That does not mean the current provider cannot get it done. Maybe their implementation consultant is not scheduled until next month. Maybe the client has not handed over the data, and the provider is waiting. Two alternative explanations worth considering:
- The project is already in the provider’s pipeline; the IT lead is complaining about slow progress, not about absence of service.
- The mid-level managers inside the client company have no personal incentive to make this work, and any implementation partner would hit the same wall.
Rushing in based on a complaint alone risks a wasted trip.
The person who is not in the conversation
Throughout the entire exchange, only the IT lead speaks out loud.
The other person in the purchasing decision chain—the sales director—appears only once, in the IT lead’s retelling: “He was involved. He signed off. But when implementation started, he said he was too busy.”
What does the sales director actually think about this system? Does he genuinely see value in it but cannot find the time, or did he view the CRM as an IT project from the start—something that has nothing to do with sales? Is he even in this Telegram group? Did he see this message?
These are unknowns.
To understand why the system is not being used, you need to know where the business-side decision-maker stands. The IT lead says the sales director “signed off.” Signing off on a budget for a purchase is not the same as committing to participate in implementation. If the person who runs the sales team does not treat go-live as his own responsibility, no amount of configuration or training from an implementation partner will change the outcome: the salespeople will still not use it.
This does not mean the lead is worthless. It means the first step is not to pitch your services. It is to find out what the person who is not in the group conversation actually thinks.
What to verify before you follow up
If you decide to spend time on this message, here are four things worth checking. Whether to contact the client is your own call—this is about what to verify.
First, when was the message posted? If it was weeks or months ago, the client’s implementation may already be complete by now, or the project may have been abandoned. Only recent messages are worth acting on.
Second, what is the contract status with the current provider? Fixed-price or time-and-materials? Are there defined acceptance milestones? If the contract already includes data migration and user training but those deliverables have not been signed off, the project is still open. That could be the source of the client’s frustration, but it also means there are outstanding contractual obligations between the client and their current provider. Walking into that situation requires awareness of the business boundary.
Third, does anyone inside the client company actually own the go-live target? Is only the IT department pushing for adoption, or does the business side also have a metric tied to it? Pay attention to whether the sales director ever mentions this project again in the group or elsewhere.
Fourth, can you actually deliver what this scenario needs? If you have done bulk data migration and field-level sales training before, you can prepare a concrete capability statement. If the client needs someone on-site for two weeks walking the team through workflows, and you only do remote support, the delivery requirements of this deal may exceed your scope.
How many messages like this do you scroll past every day?
Telegram industry groups have someone every day saying the software is not working, the project is stuck, the vendor is not delivering. Most of the time those messages come and go, and nobody stops to read them twice.
But if you can look at a complaint and see “data not migrated,” “configuration not done,” and “training not completed” as three distinct things—and you know which direction to verify first—then some of the messages you scroll past every day might contain a name worth searching for in your contacts and a profile worth opening.
If you are interested in a more systematic way to surface leads from large volumes of group discussion, this article walks through how to filter the signal from the noise: How to Identify High-Intent Leads in Telegram Business Communities
How a Signal worth attention is found
See how Top Prospect finds and organizes Signals worth checking, keeps the original Telegram context, removes duplicates, and helps you decide what to review first. You decide whether to follow up and what to do next.
