Published project figures from the LDM team, with their measurement limits. These are not independently verified self-service outcomes.
List = published starting list, not proof that every entry was contacted. TAL and SQL keep the original report labels.
FEATURED CASE · IT / SAAS
GreenData
Starting list: 7,700 · TAL: 800+ · SQL: 70+
IT / low-code in Russia. Email and social channels. The reporting period and qualification criteria are not published in the available summary.
Published source and definitions
Focus on traditional software developers
List
7 700
TAL
800+
SQL
70+
IT/SaaS · IT / low-code, Russia · email + social channels
Published project experience across email, phone and messaging; outcomes depend on the project, audience and approved scope.
List = published starting list size, not proof that every entry was contacted. TAL and SQL retain the labels used in the original summaries. A case-specific counting and qualification rule is needed before comparing conversion.
Published figures are case-specific; compare only after defining period, denominators and qualification criteria.
Use this case to understand the team’s experience. To estimate your own outcome, first agree a period, qualification criteria, contact denominator and channel attribution for a pilot.
Source: LDM project summaries. Figures reported by the team.
Context: IT / low-code in Russia; targeting traditional software developers.
Published figures: Starting list: 7,700. TAL: 800+. SQL: 70+. The list size is not a verified count of delivered messages or unique people contacted.
Channels: Email and social channels. The result is reported for the project; a channel-by-channel contribution is not published.
Period and qualification: The reporting period, unique processed contact count, SQL qualification criteria and deduplication method are not published in the available summary.
Team and platform contribution: This is the team’s project experience. The split between manual work and platform automation, platform version and an independent self-service result are not published.
