{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Outbound Wizards by SalesRobot","title":"Data Quality Drives Pipeline Growth ft. Eishan Deshwal","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/333fc883\"></iframe>","width":"100%","height":180,"duration":1354,"description":"In today's episode, I chat with Eishan Deshwal, GTM operator and consultant, about working with Series A to Series C startups experiencing growing pains - account territory mapping, data validity, CRM cleanliness - taking full ownership of projects rather than just advising, and segmenting by pain (Sandler sales philosophy: disqualify first) rather than static personas. We explore his creative Firecrawl campaign scraping privacy policy update dates from websites (getting 92% coverage after failing with AI agents that hallucinated and hitting bot protection walls), and his Doc.us campaign layering customer and prospect logos onto product screenshots using DynaPictures - testing \"effort as a proxy for trust\" by sending a clean-up email first before the image email to avoid bouncing image-heavy messages. Eishan shares his journey from engineering student in 2022 reading sales books on Reddit's r/sales list, interning at Trika Equity where he first saw CSV-to-HubSpot sequences generate deal flow (\"free money\"), using cold email to land his first job at Safety Wing (Y Combinator), going founding SDR at Hatika to learn email deliverability (DKIM, SPF, CNAME), joining Remote.com and realizing bad data kills velocity everywhere regardless of team size, and going fully freelance to help teams fix data quality - working with people like Brendan Short (Signal newsletter). He predicts GTM engineers will keep growing because startups want velocity over titles, tooling will shift toward terminal-based LLMs with interoperable context-saving across different models (lower cost, faster calls, deterministic results), and everything eventually becomes SaaS because someone always needs to maintain the code. Eishan's advice: if you're from sales, automate things inside your own company first; if you're new, start small with projects that eliminate annoyances, jump into Clay's Slack answering support questions, and stay curious about edge cases - slightly better reliability compounds...","thumbnail_url":"https://img.transistorcdn.com/gdva-6ylrTgU9EKfQzKOKWrDlr1gz9yRLxNq9g2keoI/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS83YzA4/MDQ4MjJmZDZjMmI4/MjkwMTdkYWEyNTRk/MzI0My5wbmc.webp","thumbnail_width":300,"thumbnail_height":300}