Cross-Border SaaS Case Study: Finding Buying Intent in Telegram Discussions

Consider a cross-border SaaS company that helps ecommerce teams manage international campaign operations. Its buyers include brands, agencies, and operators expanding into Southeast Asia. The team knows relevant demand appears in Telegram communities, but manually reading dozens of discussions is not scalable.

The objective is not to collect every mention of advertising or ecommerce. It is to identify buyers with a specific operational problem and a realistic reason to evaluate a solution.

Step 1: Define the ideal buyer

The team specifies:

• target roles: founder, growth lead, ecommerce operator, agency owner;
• target regions: Southeast Asia and cross-border markets;
• relevant scale: active campaigns or planned market expansion;
• common problems: fragmented workflows, unreliable providers, reporting gaps, and slow execution;
• exclusions: job seekers, general education questions, and providers promoting their own services.

Step 2: Build positive intent patterns

High-value statements include:

• “We need a team that has operated campaigns in Indonesia.”
• “Our current setup is too slow; what are the alternatives?”
• “We are launching next month and need a working process before then.”
• “Has anyone compared these two providers?”

The system recognizes the business meaning rather than requiring an exact phrase.

Step 3: Add negative examples

Without exclusions, the same vocabulary creates false alerts. The team adds examples of recruitment posts, service advertisements, affiliate promotions, forwarded news, and casual market discussion.

Step 4: Score fit, intent, and urgency

One overall number hides too much. The lead card displays:

• ICP fit;
• buying stage;
• urgency;
• confidence and source context;
• reasons for each judgment.

Step 5: Connect the signal to sales

A qualified signal creates a CRM task with the original statement, context summary, owner, recommended opening, and response deadline. If the company already exists in the CRM, the event is attached to the existing account.

Example outcome

During one week, the system may process thousands of messages while surfacing only a small number of meaningful events:

• a brand searching for a regional campaign partner;
• an agency comparing two tools;
• an operator preparing to replace an unreliable provider;
• a founder asking about implementation before a launch deadline.

The business value comes from precision and response time, not notification volume. A good workflow helps the team reach relevant buyers earlier while preserving context and avoiding indiscriminate outreach.