<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Aidany on Medium]]></title>
        <description><![CDATA[Stories by Aidany on Medium]]></description>
        <link>https://medium.com/@aidany693?source=rss-5ffa15271e79------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*2JR9iR5UZpvJhps-</url>
            <title>Stories by Aidany on Medium</title>
            <link>https://medium.com/@aidany693?source=rss-5ffa15271e79------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 22:43:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aidany693/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[From Raw Data to a More Reliable Lead List: A Design Thinking Case Study]]></title>
            <link>https://medium.com/@aidany693/from-raw-data-to-a-more-reliable-lead-list-a-design-thinking-case-study-a7e5840551ca?source=rss-5ffa15271e79------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7e5840551ca</guid>
            <category><![CDATA[data-quality]]></category>
            <category><![CDATA[data-analytics]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[data-entry]]></category>
            <category><![CDATA[lead-generation]]></category>
            <dc:creator><![CDATA[Aidany]]></dc:creator>
            <pubDate>Sun, 25 Oct 2026 19:40:12 GMT</pubDate>
            <atom:updated>2026-10-25T19:40:12.293Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Lead generation helps businesses find potential customers and build professional connections. However, collecting many contacts is not enough. The data must also be organized, relevant to the client’s target market, and checked for accuracy.</p><p>This case study explains how I used a Design Thinking approach to collect, clean, combine, and validate lead data using Apify and Google Sheets.</p><h3>1. Empathize: Understanding the Client’s Needs</h3><p>The assignment required at least 50 qualified leads from four target countries: the United Kingdom, the United States, Australia, and Indonesia.</p><p>The target roles included Compliance Officer, Compliance Manager, Risk Officer, Risk Manager, AML Specialist, KYC Specialist, Finance Director, CFO, Regulatory Manager, Growth Director, Head of Sales, Business Development Manager, and CEO.</p><p>The required data included names, job titles, company information, work emails, LinkedIn profile URLs, and company websites.</p><h3>2. Define: Identifying the Problem</h3><p>The initial data came from Apify and needed further cleaning and checking. Some person-country fields were blank, and some email addresses were invalid or uncertain.</p><p>The main problem was how to turn raw contact data into a more organized and reliable lead list without guessing missing information.</p><h3>3. Ideate: Finding Possible Solutions</h3><p>I considered several ways to improve the data quality:</p><ul><li>Use the required Apify actor to collect leads.</li><li>Combine separate country batches into one spreadsheet.</li><li>Standardize important fields and check for duplicate emails.</li><li>Verify email addresses with an email-verification tool.</li><li>Keep source information and validation notes for further checking.</li></ul><p>These steps helped organize the work and made it easier to review the results.</p><h3>4. Prototype: Building the Lead Database</h3><p>I exported the data from Apify as CSV files and combined two batches into one spreadsheet.</p><p>The combined file contained 200 unique leads. Based on the company-country field, the distribution was:</p><ul><li>United States: 89 leads</li><li>United Kingdom: 7 leads</li><li>Australia: 4 leads</li><li>Indonesia: 100 leads</li></ul><p>The spreadsheet included contact names, job titles, departments, person and company locations, company names, work emails, LinkedIn URLs, company websites, and validation notes.</p><p>Person location and company location were kept in separate columns because they do not always refer to the same place.</p><h3>5. Test: Validating the Results</h3><p>I used the Email Verifier actor to check the work email addresses. The combined results were:</p><ul><li>57 emails classified as Verified</li><li>77 emails classified as Needs Verification</li><li>66 emails classified as Unverified</li></ul><p>The results showed that not every collected email was ready to use. Some addresses passed the verification checks, while others were risky or invalid.</p><p>A verified result does not guarantee successful delivery. Job titles, country requirements, company details, and source links must also be checked before a contact can be considered a qualified lead.</p><p>I also prepared five outreach-message templates in English for different professional audiences. The messages were designed for personalized business communication, but no outreach response results were measured in this project.</p><h3>Lessons Learned</h3><p>This project showed that lead generation involves more than collecting a large number of contacts. Organizing data in a spreadsheet makes it easier to filter and review. Email verification helps identify invalid and uncertain addresses, while source links and validation notes support quality checking.</p><p>I also learned that missing information should not be guessed. The data must be reviewed against the client’s requirements before it is delivered.</p><h3>Conclusion</h3><p>Using Design Thinking helped structure the lead-generation process into clear stages: understanding the client’s needs, defining the data-quality problem, exploring solutions, building a database, and checking the results.</p><p>The final dataset contained 200 unique leads across the four target company countries, with email-verification results recorded for review. Further checks of job-title relevance and individual contact details are still needed before the final qualified-lead list is delivered.</p><p>The key lesson is simple: a useful lead list is not just large. It must be organized, relevant, traceable, and carefully checked.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7e5840551ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>