DEV Community

forlazin-debug
forlazin-debug

Posted on

Buying a Customer Database vs. Finding People Who Are Already Asking for Your Service

If you are thinking about buying a customer database, you probably want one thing: orders that start coming in right away, without a long search. That is understandable, but almost nobody on a purchased list is waiting for your offer. This article is about a different approach: finding the people who have posted in a chat that they are looking for a provider.

The first part covers how a contact list differs from a live request, what lead generation in chats looks like, and where to do it. After that comes the practical side: how to tell a real request from casual conversation, when to reply, and what to write. There are no guarantees here. The result depends on your niche, your city, and how well you answer.

Why Buying a Customer Database Does Not Mean Getting Orders

The typical picture looks like this. A business owner buys a file of contacts and starts cold calling. The first conversations go like this: "we don't need it," "where did you get my number," a dial tone. The person on the list was not looking for your service. They ended up there because of a formal attribute: city, industry, company size. They may have a need, or they may not, and at the moment you call they are certainly not thinking about it.

Cold calls and mass mailings to such a list work the same way: you write to people who were not expecting you. A few reply, the rest ignore you, and some get annoyed. On top of that comes the workload: you have to prepare a script, absorb rejections, keep records, and follow up with everyone who said "call me later." For a freelancer or a small team, this eats the time that could go into the actual work.

It is a completely different situation when a person writes in a chat that they need a provider. Here is how they differ from a contact on a list:

  • they have already described the task, so you do not have to guess what they need;

  • they are waiting for a reply and will read it carefully, because they asked the question themselves;

  • they are ready to compare options, rather than deciding whether they need the service at all.

So the whole job comes down to one thing: spot such a message in time and reply to the point, before someone else does.

Lead Generation in Plain English: What It Looks Like in Chats

Put simply, lead generation is finding people who need a service right now. It is not advertising to everyone, and it is not a list of phone numbers. It is a specific person with a specific task. In public Telegram chats, such people show up every day. They ask in ordinary words, with no ads involved. For example:

Can anyone recommend someone who handles packing and shipping for a marketplace? A batch arrives next week, and we need a warehouse and reasonable turnaround times.

You can see how common this is from the numbers. According to Leadolovets data for the last 30 days, among the requests the service found, there were about 2,460 messages from people looking for a provider. That is about 570 per week on average, found in about 460 chats. This is a lower estimate across the 14 niches currently being tracked, so the picture depends on the niche and does not represent all of Telegram.

For a small business, lead generation looks modest and practical: not a database of thousands of contacts, but a dozen live requests in your niche that you can answer well. According to the 30-day data, the most requests were in fulfillment (about 710), product certification (about 410), customer acquisition and marketing (about 290), and cleaning and dry cleaning (about 160). If your niche is not on this list, that does not mean there are no requests. The service simply covers a limited set of areas.

Where to Find People Who Are Looking for a Service

Before deciding whether to buy a customer database, look at where your customers post on their own. According to Leadolovets data for the last 30 days, among the requests the service found, they were distributed like this:

  • marketplace seller communities: about 45%;

  • topic-based and city chats: about 35%;

  • chats for apartment buildings, residential complexes, and neighborhoods: about 10%;

  • business communities: about 5%;

  • freelance and "find a contractor" chats: about 5%.

An important caveat: the skew toward sellers comes from the fact that the service has the most data on services for marketplace sellers. For your niche the shares will be different, so it depends on the niche. Use the numbers as a hint about where to start, not as a rule.

Choose chats to match your service. Cleaning, dry cleaning, small repairs, and other at-home services are more often requested in chats for buildings, residential complexes, and neighborhoods, where neighbors ask who can come over. Services for sellers, such as fulfillment, certification, or product infographics, are requested in seller communities. Psychologists and coaches look at topic-based and city chats, where people share problems and ask for advice.

It is easiest to build your chat list step by step: find about ten communities in your niche and city, join them, read the rules, and just watch for a few days. That way you will learn what people ask there, how colleagues answer, and whether offering services is allowed. A list of chats like this is often more useful than the decision to buy a customer database: you see live questions instead of faceless rows in a spreadsheet.

How to Tell a Real Request from Casual Conversation

People write a lot in chats, and not every message about a service means the person is ready to pay. The first sign of a real request is that the person asks for a recommendation. According to Leadolovets data for the last 30 days, among the requests the service found, about 25% of messages start with exactly this kind of ask: "can anyone recommend who does this," "who should I contact." The second sign is that the message contains a task. Not just "I need a specialist," but "I need to haul away furniture after a renovation on Saturday" or "looking for someone to set up product listings for ten items."

A hot request is one where the person is ready to order now. According to Leadolovets data for the last 30 days, about 40% of the requests found were like this, but that is a slice of the niches being tracked, and in your niche the share may differ. Markers of a hot request:

  • words like "urgent," "today," "by tomorrow," "this week" (a deadline appears in only about 5% of messages, so such a request is worth taking first);

  • a question like "who can take this on" or "who is available";

  • a stated volume, city or neighborhood, or date;

  • the person asks how long it will take.

What you can safely skip: price discussions with no task ("how much does this even cost these days"), complaints about a previous provider with no request to find a new one, ads from colleagues, and chatter "just out of curiosity." Sometimes a complaint turns into a request a few messages later, so it helps to check the thread: if the person wrote "looking for a replacement," that is already a real lead. If the thread is only arguments about what is right, it is better not to step in.

When and How to Reply

Speed matters a lot: while you are thinking, others reply to the message. According to Leadolovets data for the last 30 days, among the requests the service found, the most fall between 12:00 and 18:00 Moscow time, about 45%. Between 8:00 and 12:00 about 25% are posted, between 18:00 and 24:00 also about 25%, and at night about 10%. Requests most often appear around 12:00. The practical takeaway: check the chats in the morning and again before lunch, and come back at least a couple of times during the day. Timing depends on the niche, so after a week compare this with your own observations.

A good reply is short and has three parts:

  • show that you understood the task, in one sentence, in your own words;

  • say exactly how you can help, without listing every service you offer;

  • suggest a next step: clarify two questions, send a work sample, or hop on a call.

There is no need to name a price right away or spell out terms across the whole screen. People in chats read quickly and skim long text. It is better to ask a question that shows you know the field, for example about timing, volume, or what has already been done.

A separate question is whether to reply in the chat itself or send a private message. It depends on the rules. In some communities, any service offer by direct message counts as spam. In others it is common practice, and some require replies only in the thread. Before writing, reread the pinned message with the rules. If replying in the chat is allowed, it also works as a business card: other members will see it too.

An Example Request and Reply, and What Not to Do

Let us walk through a typical situation. The owner of a small shop writes in a sellers' chat:

Hey everyone, who does product listing design? Need it done fast, this week. There are not many products, but our images are really weak right now.

A weak reply looks like a template ad:

Hello! We make listings, infographics, video, photos. We have been around a long time, lots of experience, message us privately.

It is not clear from this whether the author heard you. A good reply is shorter and more precise:

I can help with listings. How many products need to be done, and do you have the original photos? If you send a couple of examples, I will tell you what is realistic by the end of the week, and we can hop on a ten-minute call.

It repeats the task, asks a specific question, and gives a clear next step. The deadline sounds like a preliminary estimate after clarifying the details, not a promise given in advance.

What not to do:

  • copy the same text into ten chats: it will be noticed, and you will be remembered as a spammer;

  • write to everyone with no request, just because someone is in the chat;

  • push discounts and phrases like "today only";

  • promise an exact outcome and deadlines you do not control: it is more honest to describe what you will do and name a timeline after clarifying the details.

And be sure to keep records. A table with three columns is enough: where you found the request, what you replied, and how it ended. After a few weeks it becomes clear which chats produce conversations and which are empty, and which wording works better. When you have a picture like this built on real data, the urge to buy a customer database usually disappears: you know where your customers post on their own.

The service is called Leadolovets, with a five-day trial and no card required.

Top comments (0)