Mahima Gupta

My sequence was running. Replies were coming in. And I had no idea if any of it was moving pipeline. Smartlead was sending. HeyReach was connecting. Clay was enriching. Three tools doing their jobs. Zero of it mapped back to HubSpot. I could tell you how many emails went out. I could not tell you how many became opportunities. This is the most common infrastructure failure I see on lean GTM teams. Not bad copy. Not a weak ICP. A broken data bridge between the tools doing the work and the CRM holding the truth. The fix is not complicated but it has four parts and most teams are missing at least two of them. 1. Every sequence needs a deal trigger, not just a reply tag. A reply in Smartlead is not a pipeline signal until something in HubSpot moves. Map your reply webhook to create or update a deal stage automatically. If you are manually logging replies from your sequence tool into your CRM, you are already behind on the accounts that matter. 2. HeyReach connections need to land in HubSpot as contacts, not just LinkedIn notifications. Most teams are running LinkedIn outreach in a completely separate loop from everything else. A new connection on HeyReach should create a contact in HubSpot with source tagged, sequence name tagged, and connection date logged. Without that you have no idea which LinkedIn touches are contributing to conversations downstream. 3. Your Clay enrichment output needs a HubSpot property for every field you care about reporting on. If Clay is enriching company size, funding stage, and tech stack but none of those fields exist as mapped properties in HubSpot, the enrichment is decorative. You ran the waterfall, you paid for the data, and it lives in a Clay table that nobody looks at after the sequence starts. 4. Build one pipeline source report before you scale anything. Pull every open deal in HubSpot and tag it by first touch source: Smartlead, HeyReach, inbound, referral. If you cannot do this in under ten minutes, your attribution is broken and you are scaling blind. Fix the reporting layer first. Then scale the volume. When these four things are working together you stop running outbound on faith and start running it on data. I put together a full walkthrough covering the exact HubSpot property setup, the Smartlead and HeyReach webhook logic, the Clay field mapping template, and the source attribution report I use to track pipeline contribution across channels. If you want it, like this post, connect with me, and comment PIPELINE below. I will send it directly.

Okay I have some tea to spill. Someone really close to me once told me you don't have it in you to be in SaaS. Casually, like it was already decided. And the worst part? I believed it. I didn't even know what SaaS meant back then. I just knew someone I trusted had looked at me and quietly decided I had a ceiling. Something just went quiet in me then. And then something else went, okay. Fine. Watch. I had no plan. No background. No one showing me the way. Just the common sense about people. About what makes someone open an email. About what a buyer actually needs to hear versus what we think they want to hear. And I got obsessed. Cold email and LinkedIn automation started feeling like a game. What time does it land. What trigger do I track. How do I write one line that makes a complete stranger feel seen. That adrenaline I still feel every single day. I taught myself the technical side. Infra, sequencing, tools, how all of it connects into a system that actually moves pipeline. First year of my career. 6 markets. KSA. Philippines. Indonesia. GCC. Africa. US. Targets overachieved. Circle of Excellence award. Changed my job, now building those things that I learnt. And a career in GTM that I stumbled into without even knowing GTM was a thing. This industry is ruthless. AI is changing everything every single day. It demands you to always be one step ahead. But nobody tells you that common sense is a superpower here. That curiosity compounds. That LinkedIn is literally an ocean if you actually swim in it. My colleagues taught me things no course ever could. This community gave me more than any classroom did. I am still learning. Still playing the game. Still chasing that feeling. So when my colleague asked me yesterday if I like what I do, before my brain could even catch up, I said I love it. And in that fraction of a second I thought about all of this. And that gave me flashbacks of everything that I wrote above. If you are figuring out GTM, growth, outbound, or just finding your footing without a traditional path, follow along.

A prospect replied to say my email was the most relevant cold outreach they had received in months. The personalisation that landed it came from a Clay formula I had written at midnight six weeks earlier and completely forgotten about. I did not write that email. The system did. I just built the system. Most GTM teams treat outbound like a daily task. Show up, pull a list, write something, hit send. Repeat tomorrow. The teams that actually scale pipeline treat it like infrastructure. You build it once. It runs without you. The output shows up whether you are there or not. That shift does not happen because of effort. It happens because of how the Clay table is set up. Four things have to be true for the system to personalise without you. > Your formula logic has to pull from signals, not fields. > Your field mapping has to be clean before the waterfall runs. > Your waterfall has to handle failure gracefully. > Your trigger condition has to fire at the right moment. When those four things are working together, the system does the thinking. You do the building. The difference between a campaign operator and an infrastructure builder is not skill level. It is which problem they think they are solving. One thinks the job is to send better emails. The other thinks the job is to build something that sends better emails without them. Which side of that are you currently on?

18 months ago I didn't know what a cron job was. I also didn't know what ICP stood for. I didn't know the difference between an MQL and a demo request. I didn't know that cold email had its own infrastructure, its own deliverability logic, its own failure modes. I was just a person who wanted to figure it out. This morning at 6:47am I opened my terminal and saw 340 rows enriched, zero errors, cron ran at 4am while I was asleep. Nobody taught me that. I built it because I kept reading, kept breaking things, kept asking why the cost was so high and eventually found a better way. The gap between "I don't know what ICP means" and "my pipeline runs while I sleep" is not talent. It is not a CS degree. It is not a RevOps team. It is 18 months of building things wrong until you understand how to build them right. This is what I actually learned. 𝟭. 𝗦𝘁𝗼𝗽 𝘂𝘀𝗶𝗻𝗴 𝗠𝗖𝗣 𝗳𝗼𝗿 𝗲𝗻𝗿𝗶𝗰𝗵𝗺𝗲𝗻𝘁 𝗮𝘁 𝘀𝗰𝗮𝗹𝗲. MCP pulls around 44,000 tokens per enrichment task. CLI pulls 1,365. That is a 30x difference per run. At a few thousand records a day, MCP also averages 72% reliability, which means hundreds of silent failures you only discover when something downstream breaks. 𝟮. 𝗬𝗼𝘂𝗿 𝗖𝗹𝗮𝘆 𝘄𝗮𝘁𝗲𝗿𝗳𝗮𝗹𝗹 𝗼𝗿𝗱𝗲𝗿 𝗶𝘀 𝗮 𝗱𝗲𝗰𝗶𝘀𝗶𝗼𝗻, 𝗻𝗼𝘁 𝗮 𝗱𝗲𝗳𝗮𝘂𝗹𝘁. I spent weeks debugging inconsistent enrichment before I realised the problem was the order I had providers in. Hitting Apollo first on domains where Apollo consistently returns null wastes the call and degrades the whole run. Map provider performance by domain type and set the order deliberately. 𝟯. 𝗕𝘂𝗶𝗹𝗱 𝘁𝗵𝗲 𝗳𝗮𝗶𝗹𝘂𝗿𝗲 𝗹𝗼𝗴 𝗯𝗲𝗳𝗼𝗿𝗲 𝘆𝗼𝘂 𝗻𝗲𝗲𝗱 𝗶𝘁. When a cron job fails with no logging, you find out the next morning when a sequence did not trigger. Every run should write the record, the step it failed on, and the reason. Takes 30 minutes to set up and saves hours of guessing later. 𝟰. 𝗛𝗲𝘆𝗥𝗲𝗮𝗰𝗵 𝗮𝗻𝗱 𝗦𝗺𝗮𝗿𝘁𝗹𝗲𝗮𝗱 𝗮𝗿𝗲 𝗻𝗼𝘁 𝗶𝗻𝘁𝗲𝗿𝗰𝗵𝗮𝗻𝗴𝗲𝗮𝗯𝗹𝗲. Smartlead needs a properly ramped domain and clean list hygiene before you scale. HeyReach needs enough connection depth in the target segment to not read as cold outreach. The failure modes are completely different and you have to monitor them differently. The system that runs at 4am and gives me 340 enriched rows by the time I open my terminal is not impressive because of the tools. It is the result of 18 months of breaking each of those tools in exactly the wrong way first. If you figured out cold email infrastructure without a proper RevOps team, what was the thing that broke first and taught you the most?

Super excited to share that I’ve joined Qoruz as Manager - Growth & Demand Generation From sending chaotic cold emails, experimenting with ABM campaigns, making meme follow-ups, and figuring things out one campaign at a time… to now building growth at a company that literally sits at the intersection of creators, data & marketing? Kinda surreal honestly. Very grateful for every person and experience that got me here 💛 Time to cook. (hopefully better than my attribution dashboards) Let’s build something crazyyy #NewBeginnings #GrowthMarketing #DemandGeneration #B2BMarketing #CreatorEconomy #newjob