<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[Signal Intelligence by Syft Data]]></title><description><![CDATA[Dispatches on B2B Growth Systems]]></description><link>https://blog.syftdata.com</link><image><url>https://substackcdn.com/image/fetch/$s_!G-G0!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0d8cf2a4-03ea-4175-b287-d204af39eb14_180x180.png</url><title>Signal Intelligence by Syft Data</title><link>https://blog.syftdata.com</link></image><generator>Substack</generator><lastBuildDate>Wed, 06 May 2026 10:56:27 GMT</lastBuildDate><atom:link href="https://blog.syftdata.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Syft Data]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[syft@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[syft@substack.com]]></itunes:email><itunes:name><![CDATA[Imran Patel]]></itunes:name></itunes:owner><itunes:author><![CDATA[Imran Patel]]></itunes:author><googleplay:owner><![CDATA[syft@substack.com]]></googleplay:owner><googleplay:email><![CDATA[syft@substack.com]]></googleplay:email><googleplay:author><![CDATA[Imran Patel]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[LinkedIn Signals Are a Commodity. Here Are 6 Plays That Still Create Pipeline.]]></title><description><![CDATA[Lessons from Kellen Casebeer on the LinkedIn outbound plays that still work when everyone has access to the same signals.]]></description><link>https://blog.syftdata.com/p/linkedin-signals-are-a-commodity</link><guid isPermaLink="false">https://blog.syftdata.com/p/linkedin-signals-are-a-commodity</guid><dc:creator><![CDATA[Imran Patel]]></dc:creator><pubDate>Mon, 20 Apr 2026 15:35:48 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/194764126/88fe282bf6ff60bcd1551c02f803072b.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p></p><p><strong>Most GTM teams are not struggling because they lack LinkedIn signals. They are struggling because they are using the same ones the same way as everyone else else.</strong></p><p>Hiring triggers. Job changes. New funding. Post engagement. Event attendee lists. None of these are bad. But once a signal becomes widely available, the message pattern attached to it usually becomes widely recognizable too.</p><p>That is the trap.</p><p>A lot of what gets called &#8220;signal-based GTM&#8221; today is really just workflow automation wrapped around stale logic. The signal fires. The playbook says &#8220;send message B.&#8221; The rep references something technically true. The buyer sees the pattern immediately. And the message dies on arrival.</p><p>That does not mean LinkedIn stopped working. It means the dumb use of LinkedIn signals stopped working.</p><p>After <strong><a href="https://www.youtube.com/watch?v=KGb-3h_fGAU&amp;t=7s">our podcast</a></strong> with <a href="https://www.linkedin.com/in/kellen-casebeer">Kellen Casebeer</a> from The Deal Lab, that was the biggest thing that stood out to me: the edge is no longer in merely having access to the signal. The edge is in how you interpret it, stack it, and turn it into a motion that feels timely instead of templated.</p><p>That matters because LinkedIn is still one of the few channels where identity, context, and outbound can work together at the same time. The profile matters. The public graph matters. The category conversation matters. And unlike email, the channel gives you a visible way to create familiarity before you ask for anything.</p><p>That is also why I think a lot of teams misread LinkedIn altogether. <strong>They treat it like an intent feed. The better teams use it like a relationship placement channel.</strong></p><p>That sounds softer than it is. It is actually a very tactical way to think about outbound. Because once you stop trying to force conversion in the first touch, a lot of the right plays become obvious.</p><p>In this post, I want to break down:</p><ul><li><p>why most LinkedIn signal selling fails</p></li><li><p>the signal hierarchy that actually matters</p></li><li><p>6 practical LinkedIn plays worth stealing</p></li><li><p>the landmines that quietly kill response rates</p></li><li><p>where Syft fits in if you want to operationalize this without turning it into spam</p></li></ul><h2>Why Most LinkedIn Signal Selling Fails</h2><p>There are two broad ways GTM teams misuse LinkedIn signals.</p><p>The first is treating a commodity signal like proprietary insight.</p><p>A hiring signal is the easiest example. Five years ago, reaching out right when a company was hiring might have felt sharp. Today, everyone has some version of that trigger. So if your logic is just &#8220;I saw you are hiring SDRs, therefore you must care about pipeline,&#8221; you are not delivering insight. You are arriving late to a crowded pattern.</p><p>The second is using context that belongs to someone else as a reason to pitch.</p><p>This is the class of motion where someone likes another person&#8217;s post, comments on a thread you were not part of, or interacts with a category conversation in public, and a random vendor jumps into their inbox as if that were a buying signal.</p><p>Usually it is not. Usually it is just creepy.</p><p><strong>The buyer has no affinity to you. No relationship with you. No reason to think you should be in that exchange. Even if the underlying signal is real, the interpretation is bad.</strong></p><p>That is the key distinction. Signals do not create pipeline on their own. Interpretation does.</p><h2>The Signal Hierarchy on LinkedIn</h2><p>Not all signals are created equal. And most teams overreact to the weakest ones. Here is the hierarchy I would use.</p><h3>1. Commodity timing signals</h3><p>These are posts around:</p><ul><li><p>hiring</p></li><li><p>funding</p></li><li><p>job changes</p></li><li><p>public announcements</p></li></ul><p>These are useful for timing. They are usually weak for messaging by themselves. They tell you that something may be changing. They do not tell you how to frame the outreach.</p><h3>2. First-party engagement signals</h3><p>These are much stronger:</p><ul><li><p>someone engaging with your content</p></li><li><p>someone engaging with your ads</p></li><li><p>someone viewing your profile</p></li><li><p>someone messaging you</p></li><li><p>repeated interaction with your team&#8217;s presence on LinkedIn</p></li></ul><p>These matter because there is actual affinity. There is at least some legitimate reason for you to follow up.</p><p>That still does not mean every like is intent. A one-off like is usually just a weak hint. But repeated engagement, especially from the right account, starts to mean something.</p><h3>3. Contextual signals</h3><p>This is where the best operators live.</p><p>These are signals that only make sense when combined with surrounding context:</p><ul><li><p>the person is active in a specific category conversation</p></li><li><p>the account is showing multiple weak signals at once</p></li><li><p>the sender profile is relevant to the buyer</p></li><li><p>there are mutuals inside the account</p></li><li><p>there is event proximity</p></li><li><p>the problem is being discussed publicly, even if your product is not</p></li></ul><p>This is the layer where LinkedIn goes from being a notification stream to being a working surface for GTM judgment.</p><p>The teams that do well here do not ask, &#8220;what trigger fired?&#8221; They ask, &#8220;what is the most plausible explanation for what is happening here, and what is the least annoying way to enter that situation?&#8221;</p><h2>Play 1: Use Blank Connects to Build the Right Audience</h2><p>This is the most underrated LinkedIn play because it feels too simple.</p><p>A lot of teams treat connection requests like mini cold emails. They try to compress targeting, personalization, credibility, value prop, and CTA into one step. That is usually a mistake.</p><p>A connection request is not a pitch. It is not even a conversation yet. It is a lightweight acknowledgment that two people may benefit from being in the same professional orbit.</p><p>That is why blank connection requests work better than many people think.</p><p>They are low friction. They do not force context where none exists. And they let you build relevant audience density over time instead of trying to manufacture urgency on day one.</p><p>The tactical version of this is straightforward:</p><ul><li><p>pick a narrow ICP</p></li><li><p>send connection requests consistently</p></li><li><p>do not ask for anything in the request</p></li><li><p>treat acceptance as access, not conversion</p></li></ul><p>This is especially powerful if you sell into the same audience repeatedly. Over time, your network becomes an asset. Not because all of those people are ready to buy now, but because familiarity compounds. You are no longer starting from zero every time.</p><p><strong>The mistake is expecting cold connects to behave like hot buyers. The point is not conversion. The point is placement.</strong></p><h2>Play 2: Follow Engagement, But Only When There Is Real Affinity</h2><p>One of the better LinkedIn plays is still the simplest one: if someone engages with your content, connect with them and continue the interaction privately.</p><p>That works because the public engagement already did the hardest part. It created familiarity. But this play gets butchered constantly because teams overread weak engagement.</p><p>A single like is rarely enough. A one-off comment is often not enough either. The move becomes much stronger when you see repeated engagement, account fit, and some plausible reason the topic matters to them.</p><p>This is where I think a lot of signal tooling either helps or hurts.</p><p>If your system just says, &#8220;person liked post, trigger outreach,&#8221; you are going to generate a lot of false positives.</p><p>If your system helps you stack the signal against the account, the topic, prior engagement, and broader GTM context, now you have something useful.</p><p>A practical version of this play looks like:</p><ul><li><p>identify repeated engagers, not one-off engagers</p></li><li><p>filter for ICP fit before acting</p></li><li><p>use the DM to continue the thread, not restart it from scratch</p></li><li><p>keep the ask small</p></li></ul><p>If they engaged with a post about rep ramp, do not pivot immediately into a generic product pitch. Stay with the topic. Show that you understood what they were actually interacting with. Then earn the right to take the conversation one step further.</p><h2>Play 3: Enter Through the Conversation, Not the Trigger</h2><p>This was probably the sharpest tactic from the conversation with Kellen.</p><p>Most signal-based outreach still starts from the trigger.</p><p>Company is hiring.<br>Person changed jobs.<br>Team raised money.</p><p>And then the outreach simply mirrors the trigger back to the buyer.</p><p>That used to work better when fewer people were doing it. Now it often just sounds like everyone else.</p><p>The better move is to enter through the category conversation already happening around the trigger.</p><p>If a company is hiring sales reps, the interesting question is not &#8220;can I mention hiring?&#8221;</p><p>It is &#8220;what problem sits underneath that hiring motion?&#8221;</p><p>Maybe it is rep ramp.<br>Maybe it is manager capacity.<br>Maybe it is enablement debt.<br>Maybe it is territory design.<br>Maybe it is outbound consistency.</p><p>That is the move. Use the trigger to identify potential relevance. Use the broader conversation to frame the outreach.</p><p>This is much harder than plugging a field into a sequence. But it is also much harder to ignore. Here is the operating rule:</p><p><strong>Commodity signals are for targeting. Category conversations are for messaging.</strong></p><p>That shift alone will clean up a lot of bad LinkedIn outbound.</p><h2>Play 4: Connect One Layer Below the Obvious Buyer</h2><p>Most teams are too transactional in how they build their LinkedIn graph.</p><p>They go straight to the highest title they can find, pitch too early, and then wonder why the account feels cold.</p><p>There is a better compounding play: connect one layer below.</p><p>If you sell to VPs, build density with managers and directors.<br>If you sell to CISOs, build density with the people who will become CISOs.<br>If you sell to founders, build relationships with their operators.</p><p>There are two reasons this works.</p><p>First, today&#8217;s manager is often tomorrow&#8217;s executive. If you sell into the same market long enough, those relationships appreciate.</p><p>Second, network density inside the account creates trust. When a more senior person clicks your profile and sees that you already know people on their team, the interaction feels less random. Mutuals act as lightweight trust bridges even before anyone says a word.</p><p>This is one of the cleanest examples of LinkedIn working as a long-duration channel rather than a one-shot prospecting surface.</p><p>The tactical move here is not complicated:</p><ul><li><p>stop measuring every new connection by immediate pipeline potential</p></li><li><p>build network density in the layer beneath the formal buyer</p></li><li><p>revisit those people over time as they grow in seniority</p></li><li><p>let mutual connection depth do some of the work for you</p></li></ul><p>This is a slower play. It is also one of the least fragile ones.</p><h2>Play 5: Match the Motion to the Sender Profile</h2><p>One thing Kellen&#8217;s playbook gets very right is that not every LinkedIn sender is interpreted the same way.</p><p>A founder message is read differently than an SDR message.<br>An operator message is read differently than an AE message.<br>An executive message is read differently than a junior rep message.</p><p>That means the play itself should change depending on who is sending.</p><h3>If the sender is a founder</h3><p>Lean into curiosity, point of view, and long-term relevance. Founders often get more latitude because buyers assume there may be partnership value or future optionality in the relationship.</p><h3>If the sender is an operator</h3><p>Use peer language. Operators respond well to other operators when the message feels grounded in the actual work.</p><h3>If the sender is an AE</h3><p>Credibility matters. Competence matters. The recipient is asking whether you understand the space enough to be worth replying to.</p><h3>If the sender is an SDR</h3><p>Keep it light. Keep it short. Keep it respectful. The goal is not persuasion. The goal is to open a door.</p><p>This is one of the biggest mistakes I see in LinkedIn outbound. Teams centralize message logic too aggressively and forget that the profile itself is doing a huge amount of work before the message is ever read.</p><p>Your copy does not land in a vacuum. It lands on top of identity.</p><h2>Play 6: Use Events as Momentum, Not Just Meetings</h2><p>LinkedIn and events are much more complementary than most teams realize.</p><p>The reason events work is not mystical. It is momentum. The buyer already decided this category matters enough to spend time on. They already chose to be in the room.<br>They are already in a mode where conversation is expected.</p><p>That means LinkedIn outreach around an event has a much better chance of feeling near and familiar. There are two especially good versions of this play.</p><h3>The pre-event connect</h3><p>Get the attendee list. Connect ahead of time. Keep the note simple. &#8220;Saw you&#8217;ll be there, would love to say hi.&#8221;</p><p>This works because the context is already real. You are not inventing relevance.</p><h3>The post-event miss</h3><p>After the event, connect with the people you did not meet. &#8220;Sorry we missed each other, would have loved to connect.&#8221;</p><p>This is a great play because it borrows the event&#8217;s momentum without requiring a full meeting at the event itself.</p><p>The broader lesson is that LinkedIn often works best when it sits next to another source of context. Events are one of the cleanest examples of that.</p><h2>The Brand Layer Most Teams Miss</h2><p>There is another mistake buried under all of this.</p><p>A lot of companies still use LinkedIn like a glorified PR wire.</p><p>The company page posts announcements. The founder posts polished updates. The comments go unanswered. The employees repost things they did not write. Everybody claims to be &#8220;doing LinkedIn,&#8221; but nobody is actually participating in the category.</p><p>That creates the worst possible setup for outbound. You have activity without familiarity. Content without conversation. Presence without permission.</p><p>The better version is a flywheel:</p><ul><li><p>the company creates useful context</p></li><li><p>the founder contributes real point of view</p></li><li><p>employees become credible nodes in the category</p></li><li><p>public familiarity makes private outreach easier</p></li></ul><p>This matters because the best LinkedIn outbound rarely starts in the inbox. It starts in the feed, the comments, the profile, and the surrounding category conversation.</p><h2>Landmines That Quietly Kill Response Rates</h2><p>A few mistakes show up again and again.</p><h3>Pitching in the connect request</h3><p>Too early. Too heavy. Usually unnecessary.</p><h3>Treating one weak signal as intent</h3><p>A like is not a meeting request.</p><h3>Using third-party engagement as your excuse to pounce</h3><p>This is how a lot of &#8220;signal-based&#8221; outreach turns creepy fast.</p><h3>Forcing context where none exists</h3><p>If there is no real connection, keep it simple. Do not pretend there is one.</p><h3>Overexplaining</h3><p>Long messages often signal insecurity more than relevance.</p><h3>Confusing silence with failure</h3><p>Silence is normal. It is data, not drama.</p><h3>Talking to yourself in follow-ups</h3><p>A couple of thoughtful touches can work. A stack of unanswered messages makes you look careless.</p><h3>Trying to convert before the person becomes responsive</h3><p>This is the big one. Responsiveness creates the conversion window. Not the other way around.</p><h2>How We&#8217;d Operationalize This at Syft</h2><p>The temptation with LinkedIn data is to collect more of it.</p><p>I think that is the wrong goal.</p><p>The goal is to get better at separating weak signals from strong ones, isolated signals from stacked ones, and first-party context from random public exhaust.</p><p>That is the lens we increasingly care about at Syft.</p><p>Not &#8220;more triggers.&#8221;<br>Better judgment.</p><p>In practice, that means a few things:</p><ul><li><p>prioritize first-party engagement over third-party voyeurism</p></li><li><p>do not fire on one-off signals unless there is other context</p></li><li><p>stack engagement with account fit and surrounding category context</p></li><li><p>route different plays based on who is sending</p></li><li><p>use LinkedIn as part of a broader outbound system, not as a standalone channel</p></li></ul><p>That last point matters.</p><p>One of the best parts of Kellen&#8217;s playbook is that LinkedIn is not treated as some sacred standalone motion. It sits alongside email, calls, events, and broader outbound design. Sometimes the DM is the opener. Sometimes it is the recognition layer that makes email work better. Sometimes it is simply the fastest way to get into the right people&#8217;s orbit.</p><p>That is a much healthier way to think about the channel.</p><h2>Closing Thought</h2><p>LinkedIn signals did not stop mattering but they just got cheaper. And once a signal gets cheap, the edge shifts somewhere else.</p><p>Usually it shifts into:</p><ul><li><p>interpretation</p></li><li><p>timing</p></li><li><p>sender identity</p></li><li><p>surrounding context</p></li><li><p>and the discipline to keep the interaction light until the buyer gives you permission to do more</p></li></ul><p>That is the game now. Not who has the most signals but who can operationalize the <a href="https://www.syftdata.com/playbook">best motions</a> with the right context. </p><p>If you want the full conversation behind these ideas, <strong><a href="https://www.youtube.com/watch?v=KGb-3h_fGAU">watch the full episode with Kellen here</a></strong><a href="https://www.youtube.com/watch?v=KGb-3h_fGAU">.</a></p>]]></content:encoded></item><item><title><![CDATA[Your Website Isn’t Dying. It’s Being Promoted.]]></title><description><![CDATA[ChatGPT is sending you fewer visitors. They're just worth 4x more.]]></description><link>https://blog.syftdata.com/p/your-website-isnt-dying-its-being</link><guid isPermaLink="false">https://blog.syftdata.com/p/your-website-isnt-dying-its-being</guid><dc:creator><![CDATA[Imran Patel]]></dc:creator><pubDate>Sat, 14 Feb 2026 00:59:35 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!j9B1!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76640cd-a445-47c7-87fc-f3c4417722a6_2528x1696.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>&#8220;Will websites even exist in their current form beyond 2026?&#8221;</p><p>That question came up repeatedly at a lunch event I attended this week with CMOs and marketing leaders. And I get why they&#8217;re asking. Traffic is down. AI overviews are eating clicks. ChatGPT scrapes 1,200 pages for every single human page view on your site (Anthropic&#8217;s Claude does 6,000). Your beautiful top-of-funnel content strategy is increasingly performing for an audience of bots.</p><p>So yeah if you&#8217;re measuring your website by traffic volume, things look bleak.</p><p>But the website isn&#8217;t dying. Its job description just changed. And the new role is a <em>promotion</em>.</p><div><hr></div><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!j9B1!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76640cd-a445-47c7-87fc-f3c4417722a6_2528x1696.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!j9B1!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76640cd-a445-47c7-87fc-f3c4417722a6_2528x1696.png 424w, https://substackcdn.com/image/fetch/$s_!j9B1!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76640cd-a445-47c7-87fc-f3c4417722a6_2528x1696.png 848w, https://substackcdn.com/image/fetch/$s_!j9B1!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76640cd-a445-47c7-87fc-f3c4417722a6_2528x1696.png 1272w, https://substackcdn.com/image/fetch/$s_!j9B1!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76640cd-a445-47c7-87fc-f3c4417722a6_2528x1696.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!j9B1!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76640cd-a445-47c7-87fc-f3c4417722a6_2528x1696.png" width="1456" height="977" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/a76640cd-a445-47c7-87fc-f3c4417722a6_2528x1696.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:977,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:7746764,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://blog.syftdata.com/i/187911475?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76640cd-a445-47c7-87fc-f3c4417722a6_2528x1696.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!j9B1!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76640cd-a445-47c7-87fc-f3c4417722a6_2528x1696.png 424w, https://substackcdn.com/image/fetch/$s_!j9B1!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76640cd-a445-47c7-87fc-f3c4417722a6_2528x1696.png 848w, https://substackcdn.com/image/fetch/$s_!j9B1!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76640cd-a445-47c7-87fc-f3c4417722a6_2528x1696.png 1272w, https://substackcdn.com/image/fetch/$s_!j9B1!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76640cd-a445-47c7-87fc-f3c4417722a6_2528x1696.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image"><svg role="img" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg"><g><title></title><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p><em><strong>The classic funnel drove traffic down. The inverted funnel captures intent at the center and amplifies it outward.</strong></em></p><div><hr></div><h2>The Funnel Flipped</h2><p>For two decades, we ran the same play. Drive traffic to the top of a wide funnel with SEO, social, paid ads and then nurture visitors down through consideration to conversion. The website <em><strong>was</strong></em> the starting point.</p><p>That era is over.</p><p>Today, buyers do their research before they ever touch your site. They ask ChatGPT. They read a thread on LinkedIn. They hear about you in a Slack community or a podcast. By the time they land on your website, they&#8217;re not browsing; they&#8217;re <em>deciding</em>.</p><p><strong>This is the inverted funnel</strong>. Your website used to be the wide mouth at the top. Now it&#8217;s the narrow point where intent concentrates. The visitors who make it there carry real signal which is why LLM referral traffic converts 3-4x higher than traditional organic search.</p><p>Read that again: the traffic that AI sends you <em>closes better</em> than the traffic Google used to send you.</p><p><strong>Your site didn&#8217;t lose its purpose. The purpose upgraded from awareness to conversion.</strong></p><h2>The &#8220;Waist&#8221; Is Where the Magic Happens</h2><p>The inverted funnel has a waist - the narrowest point where human visitors arrive with intent. This is where you need to instrument everything.</p><p>Most marketing stacks are still optimized for the old funnel. They measure page views, sessions, and bounce rates - vanity metrics from the traffic era. In the inverted funnel, what matters is:</p><ul><li><p><strong>Who</strong> showed up (not how many)</p></li><li><p><strong>Where</strong> they came from (LLM referral? Branded search? A partner&#8217;s link?)</p></li><li><p><strong>What</strong> they did (pricing page? Security docs? Integration pages?)</p></li><li><p><strong>How many people</strong> from the same account are visiting (one stakeholder or three?)</p></li></ul><p>These are first-party signals that only you have. No competitor can buy them from a third-party vendor. No intent data provider can replicate them. They&#8217;re yours.</p><h2>The Bottom Half: Amplification</h2><p>Below the waist, it opens back up: wider than the old funnel ever was. This is the amplification zone.</p><p>You take the signals from that narrow intent point and fan them out to every channel that touches your buyer: social posts, partner co-marketing, email sequences, community engagement, even the context you feed back to LLMs through your content strategy.</p><p>Think of it as a feedback loop. A prospect visits your site from a ChatGPT referral. You capture the signal. You see they&#8217;re researching a specific use case. Now you amplify: your team shares relevant content on LinkedIn, your partner mentions you in a webinar, your SDR sends a personalized note that references the exact problem the prospect was researching.</p><p>The amplification loop works because it&#8217;s informed by real intent, not guesses. And many of the channels you&#8217;re amplifying into - social, community, partner content - are the same places LLMs pull from when forming their recommendations. <strong>So the loop compounds.</strong></p><h2>What This Means for Your Team</h2><p>If you&#8217;re a Growth Marketer reading this, here&#8217;s the practical upshot:</p><p><strong>Stop mourning traffic declines.</strong> The volume game is over. A smaller number of high-intent visitors who actually convert is worth more than a firehose of tire-kickers who bounce.</p><p><strong>Instrument the waist.</strong> If you can&#8217;t tell me who visited your site today, where they came from, and what content they engaged with at the account and person level you&#8217;re flying blind in the most important part of the funnel.</p><p><strong>Invest in the amplification layer.</strong> Most marketing teams are still organized around the top of the old funnel. The inverted funnel demands a different muscle: taking bottom-funnel signal and distributing it across channels. This is where in-person events, community, and partnerships become critical; but they need to be fed by signal, not run on vibes.</p><p><strong>Reclaim your content strategy for LLMs.</strong> Your website now feeds two audiences: humans and AI. The content you publish shapes how LLMs talk about you, which shapes the referral traffic you receive, which shapes the intent you capture. It&#8217;s a flywheel, and it starts with content you control on your own domain.</p><h2>Websites Aren&#8217;t Obsolete. They&#8217;re the Tip of the Spear.</h2><p>The question isn&#8217;t whether you need a website. The question is whether you&#8217;ve upgraded your website&#8217;s job to match how buyers actually behave now.</p><p>In the old world, your site was a lobby - welcoming, broad, trying to appeal to everyone. In the new world, it&#8217;s a signal station - capturing concentrated intent from the few visitors who matter most, then broadcasting what you learn to the channels where your next buyers are forming their opinions.</p><p>The funnel flipped. Your website got promoted. The only question is whether your GTM stack noticed.</p><div><hr></div><p><em>This is what we think about every day at <a href="https://syftdata.com/">Syft Data</a> &#8212; helping GTM teams capture and act on the first-party signals that matter most. If you&#8217;re rethinking how your website fits into your go-to-market, I&#8217;d love to hear what you&#8217;re seeing. Reply to this email or find me on <a href="https://linkedin.com/in/imranpatel">LinkedIn</a>.</em></p>]]></content:encoded></item><item><title><![CDATA[The Quiet Reshaping of Data Enrichment]]></title><description><![CDATA[LinkedIn and LLMs are transforming a $10B market - here's what our data reveals]]></description><link>https://blog.syftdata.com/p/the-quiet-reshaping-of-data-enrichment</link><guid isPermaLink="false">https://blog.syftdata.com/p/the-quiet-reshaping-of-data-enrichment</guid><dc:creator><![CDATA[Imran Patel]]></dc:creator><pubDate>Mon, 10 Feb 2025 15:02:37 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!Latq!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8fbe0915-3d48-4c6b-9860-3c2c7c191f4c_800x547.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The B2B data enrichment landscape is experiencing a seismic shift, driven by two powerful forces: LinkedIn's growing dominance and the rapid advancement of Large Language Models (LLMs). At <a href="https://syftdata.com">Syft</a>, we're seeing evidence of this transformation both in market spending data and in our own product development. Let's dive into what the data tells us.</p><h2>The Shifting Power Dynamic in Data Enrichment</h2><p>Recent spending data from Ramp reveals fascinating trends in the data enrichment market. While ZoomInfo maintains its leadership position with 42% market share, LinkedIn Sales Navigator has been steadily gaining ground, now commanding 18% of wallet share - a significant increase from just 4% in Q3 2023.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://blog.syftdata.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading Signal Intelligence by Syft ! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!Latq!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8fbe0915-3d48-4c6b-9860-3c2c7c191f4c_800x547.jpeg" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!Latq!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8fbe0915-3d48-4c6b-9860-3c2c7c191f4c_800x547.jpeg 424w, https://substackcdn.com/image/fetch/$s_!Latq!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8fbe0915-3d48-4c6b-9860-3c2c7c191f4c_800x547.jpeg 848w, https://substackcdn.com/image/fetch/$s_!Latq!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8fbe0915-3d48-4c6b-9860-3c2c7c191f4c_800x547.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!Latq!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8fbe0915-3d48-4c6b-9860-3c2c7c191f4c_800x547.jpeg 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!Latq!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8fbe0915-3d48-4c6b-9860-3c2c7c191f4c_800x547.jpeg" width="800" height="547" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/8fbe0915-3d48-4c6b-9860-3c2c7c191f4c_800x547.jpeg&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:547,&quot;width&quot;:800,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:null,&quot;alt&quot;:&quot;Image preview&quot;,&quot;title&quot;:null,&quot;type&quot;:null,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:null,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="Image preview" title="Image preview" srcset="https://substackcdn.com/image/fetch/$s_!Latq!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8fbe0915-3d48-4c6b-9860-3c2c7c191f4c_800x547.jpeg 424w, https://substackcdn.com/image/fetch/$s_!Latq!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8fbe0915-3d48-4c6b-9860-3c2c7c191f4c_800x547.jpeg 848w, https://substackcdn.com/image/fetch/$s_!Latq!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8fbe0915-3d48-4c6b-9860-3c2c7c191f4c_800x547.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!Latq!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8fbe0915-3d48-4c6b-9860-3c2c7c191f4c_800x547.jpeg 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image"><svg role="img" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg"><g><title></title><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>This growth isn't accidental. LinkedIn's strategy combines three powerful elements:</p><ul><li><p>Ownership of the world's richest professional network data</p></li><li><p>Strategic expansion into intent data offerings</p></li><li><p>Aggressive stance against data scraping, directly impacting competitors who rely on LinkedIn as a data source</p></li></ul><h2>LLMs: The Dark Horse in Data Enrichment</h2><p>But there's an even more intriguing disruption happening: LLMs are becoming remarkably effective at synthesizing public data for enrichment purposes. Our recent experience with incorporating LLMs in <a href="https://syftdata.com">Syft&#8217;s</a> waterfall produced some eye-opening results.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!Gdn5!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdf1020d0-3389-45d1-b989-39ead1e667f7_699x497.jpeg" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!Gdn5!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdf1020d0-3389-45d1-b989-39ead1e667f7_699x497.jpeg 424w, https://substackcdn.com/image/fetch/$s_!Gdn5!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdf1020d0-3389-45d1-b989-39ead1e667f7_699x497.jpeg 848w, https://substackcdn.com/image/fetch/$s_!Gdn5!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdf1020d0-3389-45d1-b989-39ead1e667f7_699x497.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!Gdn5!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdf1020d0-3389-45d1-b989-39ead1e667f7_699x497.jpeg 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!Gdn5!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdf1020d0-3389-45d1-b989-39ead1e667f7_699x497.jpeg" width="699" height="497" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/df1020d0-3389-45d1-b989-39ead1e667f7_699x497.jpeg&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:497,&quot;width&quot;:699,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:null,&quot;alt&quot;:&quot;Image preview&quot;,&quot;title&quot;:null,&quot;type&quot;:null,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:null,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="Image preview" title="Image preview" srcset="https://substackcdn.com/image/fetch/$s_!Gdn5!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdf1020d0-3389-45d1-b989-39ead1e667f7_699x497.jpeg 424w, https://substackcdn.com/image/fetch/$s_!Gdn5!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdf1020d0-3389-45d1-b989-39ead1e667f7_699x497.jpeg 848w, https://substackcdn.com/image/fetch/$s_!Gdn5!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdf1020d0-3389-45d1-b989-39ead1e667f7_699x497.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!Gdn5!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdf1020d0-3389-45d1-b989-39ead1e667f7_699x497.jpeg 1456w" sizes="100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image"><svg role="img" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg"><g><title></title><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>When we tested company revenue enrichment across providers, we found:</p><ul><li><p>Clearbit: 27% success rate</p></li><li><p>Perplexity (LLM): 16% success rate</p></li><li><p>Apollo: 12% success rate</p></li></ul><p>What makes this particularly impressive is that Perplexity achieved this 16% rate even when consulted last in our enrichment waterfall! For our customers (B2B companies) using revenue data to define their Ideal Customer Profile (ICP), this represents a significant improvement in lead qualification accuracy.</p><h2>The Nuanced Reality of LLM Integration</h2><p>However, this doesn't mean companies should immediately abandon traditional data providers. Here's what we've learned:</p><ol><li><p><strong>Private Data Maintains Value</strong>: Providers with proprietary datasets (like ZoomInfo, maintaining 40%+ market share) continue to offer unique value</p></li><li><p><strong>Emerging Partnerships</strong>: The recent Perplexity-Crunchbase partnership signals a trend toward integration rather than pure disruption</p></li><li><p><strong>Quality Control Challenges</strong>: LLM hallucinations remain a concern, making robust evaluation datasets essential</p></li></ol><h2>The Future: A Hybrid Approach</h2><p>Based on our experience and market data, we're seeing a new enrichment stack emerge:</p><ol><li><p>LLMs as the first layer for public data synthesis</p></li><li><p>Traditional providers for private and verified data</p></li><li><p>Hybrid solutions that combine both approaches</p></li></ol><p>The Ramp spending report shows that the market isn't winner-take-all - different providers serve different needs. Even as LinkedIn Sales Navigator grows and new players like LLMs emerge, companies like ZoomInfo maintain strong positions through their proprietary data advantages.</p><h2>What This Means for B2B Companies</h2><p>For companies relying on B2B data, the implications are significant:</p><ul><li><p>More accurate data enrichment through diversified sources</p></li><li><p>Potential cost optimization by leveraging LLMs for public data</p></li><li><p>Need for sophisticated evaluation and validation mechanisms</p></li></ul><h2>Looking Ahead</h2><p>The writing is on the wall: if your data lives on LinkedIn or anywhere public, traditional enrichment providers will face increasing pressure. At <a href="https://syftdata.com">Syft</a>, we're already seeing the impact of this shift in our enrichment success rates, and we're investing heavily in building robust evaluation datasets to maximize the potential of both LLMs and traditional data sources.</p><p>The future of data enrichment won't belong to any single approach, but rather to platforms that can effectively combine the power of LLMs with traditional data sources while maintaining high accuracy standards. The market data and our own testing confirm this hybrid future is already taking shape.</p><div><hr></div><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://blog.syftdata.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption"><strong>Subscribe to Signal Intelligence by Syft! </strong> Notes on running modern B2B GTM with better data and playbooks</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[Why you should get SOC 2 compliant much sooner]]></title><description><![CDATA[The case for investing early in compliance for B2B startups]]></description><link>https://blog.syftdata.com/p/why-you-should-get-soc-2-compliant</link><guid isPermaLink="false">https://blog.syftdata.com/p/why-you-should-get-soc-2-compliant</guid><dc:creator><![CDATA[Imran Patel]]></dc:creator><pubDate>Thu, 19 Dec 2024 08:44:05 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/3715209c-444d-476e-8ba1-251a2432b1c3_420x300.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><a href="https://syftdata.com">Syft</a> is SOC 2 Type 2 compliant as of last month! Why did a 1-year old startup like ours go through such a long process this early? Doesn&#8217;t it SOC 2 much, as they say?<br><br>One major reason you hear startups getting SOC 2 compliance is to win upmarket deals. In our experience, startups sell to other startups in the beginning and a majority of them don&#8217;t strictly require SOC 2 unless they are in a regulated space liked Fintech.<br><br>But our customers entrust us with user data that is covered by privacy laws. Quite frankly, we think SOC 2 and CPRA/GDPR compliance should be table stakes in the GTM/martech space. We owe it to our customers and so we made it a priority.<br><br>There were some other pros of getting this process done early:<br><br>&#128272; It signals that we think of security and privacy of customer data as &#8220;being integral to our service&#8221;. Even for customers who don&#8217;t strictly require SOC2, this is reassuring and a differentiator. When it is required, as sellers, there is one less objection to worry about. <br><br> &#128260; The earlier you get started, the easier it is. The surface area and complexity of systems is smaller. Your team is smaller. It is much faster to audit and document risks, mitigate them, and make changes.<br><br>&#128203; You can bake in the best practices from the very beginning e.g. it helped us tighten up our onboarding/offboarding and access control processes and policies.<br><br>&#128104;&#127996;&#8205;&#128188; Between me and my co-founder, we wear multiple hats and it was great to recognize and formalize certain responsibilities and roles we had on the infosec and privacy front.<br><br>There were some minor inconveniences as well:<br><br>&#10062; SoC 2 is not just a pure &#8216;security&#8217; framework. It encompasses things like employee performance management. We don&#8217;t have some of these setup yet, and so it took some time to document processes/policies that are not applicable at our stage.<br><br>&#128034; If your technology stack is somewhat modern, it might not be natively supported for automated compliance monitoring. We use Vercel to host our application service which is not supported by most SOC 2 vendors. In the end, we used the usual screenshots for evidence but this slowed things down. <br><br>Despite these, we were able to finish the process in a reasonable time (it took us ~7 months) thanks to the agility of our engineering team. <br><br>If you are an early stage startup and on the fence, we strongly recommend getting this done earlier. Your customers, your engineering team, and your sales team will thank you for it!</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://blog.syftdata.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading Signal Intelligence by Syft ! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[The Gmail Signup Problem in B2B]]></title><description><![CDATA[How savvy growth teams get high-quality leads from PLG]]></description><link>https://blog.syftdata.com/p/the-gmail-signup-problem-in-b2b</link><guid isPermaLink="false">https://blog.syftdata.com/p/the-gmail-signup-problem-in-b2b</guid><dc:creator><![CDATA[Imran Patel]]></dc:creator><pubDate>Sun, 27 Oct 2024 03:23:19 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/150782116/a637c91fdf2a220970ecc43c62c21790.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>B2B products with PLG and open source models often don&#8217;t know who is using their product. Here are three ways how savvy growth teams solve this problem.<br><br>Most B2B and B2D PLG companies allow sign-ups via 3rd-party providers such as Google, Github or Microsoft. This reduces friction but also attracts a lot of personal (or what people call &#8220;gmail&#8221;) signups. <br><br>For certain customers, we have seen 80-95% of signups use personal emails.<br><br>Unfortunately, it is very hard to identify the work context of these users from their personal email. Where do they work? What is their title and team? This information is critical to not only provide a good product experience but also helps your sales and customer support prioritize signups from high-value accounts. While signups from students and hobbyists are great, you might want your GTM team to focus on accounts that are within your ICP (which might not include students/hobbyists) and have greater expansion/revenue potential.</p><p>Unfortunately, without this context, growth and sales teams spend hours trying to research these signups. It becomes extremely difficult to qualify them as product-qualified leads (PQLs) for their sales-assist motions. </p><h3>Knowing your users</h3><p><br>So how do most companies solve this problem? We have seen three approaches:<br><br>1&#65039;&#8419; <strong>Incentivize signups with work email</strong><br><a href="https://capsule.video">Capsule</a> prioritizes early product access for work email signups. <a href="https://www.heygen.com">HeyGen</a> offered extra credits with a work email signup. <a href="https://wandb.com">Weights &amp; Biases</a> makes it clear that certain features such as teams and invitations require a work email. Get creative based on your offering!<br><br>2&#65039;&#8419; <strong>Build a profile during onboarding</strong></p><p>You can ask the users about their role and company during onboarding. <span class="mention-wrap" data-attrs="{&quot;name&quot;:&quot;Elena Verna&quot;,&quot;id&quot;:3478323,&quot;type&quot;:&quot;user&quot;,&quot;url&quot;:null,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/6eeab89f-c508-46ec-91a1-9e8e3ce3021a_1926x2892.jpeg&quot;,&quot;uuid&quot;:&quot;380a597e-c6e8-402e-ad01-bad7a32dbbfe&quot;}" data-component-name="MentionToDOM"></span> has a great framework you can use for this.<br><br>3&#65039;&#8419; <strong>Enrich email signups</strong> </p><p>With a stack of data providers and public data, you can enrich a significant fraction of signups. We see upto 90% success with work emails and close to 25% with personal emails at <a href="https://syftdata.com">Syft</a> with this strategy.<br></p><h3>Putting it all together</h3><p>We recommend layering these three approaches to get better identification rates: </p><p>1.&nbsp; <strong>Nudge</strong> for work email at sign up. <strong>Be Creative</strong>!</p><p>2.&nbsp; <strong>Enrich</strong> emails during signup with an enrichment waterfall.</p><p>3. <strong>Augment</strong> non-enriched profiles with onboarding questions.</p><p>This will ensure that you get good coverage on the firmographic information about a user once they sign up. <br><br></p>]]></content:encoded></item><item><title><![CDATA[How accurate is site visitor identification? ]]></title><description><![CDATA[Results from benchmarking de-anonymization services]]></description><link>https://blog.syftdata.com/p/how-accurate-are-site</link><guid isPermaLink="false">https://blog.syftdata.com/p/how-accurate-are-site</guid><dc:creator><![CDATA[Imran Patel]]></dc:creator><pubDate>Thu, 22 Aug 2024 00:10:00 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe10bb638-c498-4b54-9246-2dd401a10090_900x450.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p></p><p>We recently launched a <a href="https://whoami.syftdata.com/">benchmarking tool</a> to compare the accuracy of website visitor de-anonymization services. In this post, we will share some preliminary benchmark results from the data we collected from folks who used the tool.<br><br><strong>tldr:</strong> Accuracy rates for company identification remain low across services. Clearbit has higher identification and accuracy rates compared to others<a class="footnote-anchor" data-component-name="FootnoteAnchorToDOM" id="footnote-anchor-1" href="#footnote-1" target="_self">1</a> but is limited to company-level identification.</p><h3>Methodology </h3><p>We took a sample of of data from global visitors who used the tool. The FAQ on the <a href="https://whoami.syftdata.com">whoami</a> page explains how the tool works. But as a quick recap, the tool identifies a visitor with multiple de-anonymization services. An identification is considered accurate if the company identified by a service matches the work email that the visitor submits. This is not always perfect - some folks work at multiple companies - but is close enough. </p><p>There is another caveat.&nbsp;A service like RB2B only works in the US so their metrics might be diluted given the data considers global visitors. We felt global data was more representative given every other service works globally. </p><h3>&#129345;&#129345; The Results </h3><p>The chart below show the two major metrics we used to measure the coverage and accuracy of de-anonymization services.</p><p><br><strong>Total Identified</strong>: This simply measures the percentage of visitors who were identified by a service. <br><br><strong>Accurately Identified</strong>: This is the percentage of visitors whose company was accurately identified by a service across *all* visitors (identified or unidentified). <br></p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!B2OD!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe10bb638-c498-4b54-9246-2dd401a10090_900x450.jpeg" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!B2OD!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe10bb638-c498-4b54-9246-2dd401a10090_900x450.jpeg 424w, https://substackcdn.com/image/fetch/$s_!B2OD!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe10bb638-c498-4b54-9246-2dd401a10090_900x450.jpeg 848w, https://substackcdn.com/image/fetch/$s_!B2OD!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe10bb638-c498-4b54-9246-2dd401a10090_900x450.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!B2OD!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe10bb638-c498-4b54-9246-2dd401a10090_900x450.jpeg 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!B2OD!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe10bb638-c498-4b54-9246-2dd401a10090_900x450.jpeg" width="900" height="450" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/e10bb638-c498-4b54-9246-2dd401a10090_900x450.jpeg&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:450,&quot;width&quot;:900,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:null,&quot;alt&quot;:&quot;No alt text provided for this image&quot;,&quot;title&quot;:null,&quot;type&quot;:null,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:null,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="No alt text provided for this image" title="No alt text provided for this image" srcset="https://substackcdn.com/image/fetch/$s_!B2OD!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe10bb638-c498-4b54-9246-2dd401a10090_900x450.jpeg 424w, https://substackcdn.com/image/fetch/$s_!B2OD!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe10bb638-c498-4b54-9246-2dd401a10090_900x450.jpeg 848w, https://substackcdn.com/image/fetch/$s_!B2OD!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe10bb638-c498-4b54-9246-2dd401a10090_900x450.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!B2OD!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe10bb638-c498-4b54-9246-2dd401a10090_900x450.jpeg 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image"><svg role="img" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg"><g><title></title><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p></p><p>We can however get more precise. What really matter when it comes to accuracy is the false positive rate i.e. <strong>how many &#8220;identified&#8221; visitors are accurate</strong>. Here&#8217;s the money chart:</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!SEJ5!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F41b75232-07dc-4314-9df4-5db4057f05dc_738x767.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!SEJ5!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F41b75232-07dc-4314-9df4-5db4057f05dc_738x767.png 424w, https://substackcdn.com/image/fetch/$s_!SEJ5!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F41b75232-07dc-4314-9df4-5db4057f05dc_738x767.png 848w, https://substackcdn.com/image/fetch/$s_!SEJ5!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F41b75232-07dc-4314-9df4-5db4057f05dc_738x767.png 1272w, https://substackcdn.com/image/fetch/$s_!SEJ5!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F41b75232-07dc-4314-9df4-5db4057f05dc_738x767.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!SEJ5!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F41b75232-07dc-4314-9df4-5db4057f05dc_738x767.png" width="738" height="767" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/41b75232-07dc-4314-9df4-5db4057f05dc_738x767.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:767,&quot;width&quot;:738,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:92498,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:null,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!SEJ5!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F41b75232-07dc-4314-9df4-5db4057f05dc_738x767.png 424w, https://substackcdn.com/image/fetch/$s_!SEJ5!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F41b75232-07dc-4314-9df4-5db4057f05dc_738x767.png 848w, https://substackcdn.com/image/fetch/$s_!SEJ5!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F41b75232-07dc-4314-9df4-5db4057f05dc_738x767.png 1272w, https://substackcdn.com/image/fetch/$s_!SEJ5!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F41b75232-07dc-4314-9df4-5db4057f05dc_738x767.png 1456w" sizes="100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image"><svg role="img" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg"><g><title></title><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p></p><p>As you can see, Clearbit and Snitcher do quite well in terms coverage but Clearbit is clearly superior in terms of precision along with Dealfront. Apollo&#8217;s and People Data Lab&#8217;s offerings are quite new so it doesn&#8217;t surprise us that they still have ways to go. </p><p>We will have more data to share in a follow-up post with more cuts to identify how they all stack up in terms of overlap coverage across different geographies e.g. US vs non-US. Please <a href="https://whoami.syftdata.com">sign up here</a> to get it.</p><h3><br>&#128273; Key Takeaways</h3><p>Given the mixed results here, you might be tempted to give up on de-anonymization. After all &lt;50% coverage and precision doesn&#8217;t look good! But there is another way to look at this. Every % point in coverage gives you visibility into your traffic that otherwise you wouldn&#8217;t have!</p><p>There are also techniques you can use to improve the precision as well get more signal out of this noisy data. Here are four concrete ideas we recommend:</p><p><br>1&#65039;&#8419; <strong>Use confidence scores</strong>. Vendors like Clearbit and PDL will offer confidence scores (High/Medium/Low). We strongly recommend using these to filter out Low confidence visits.<br><br>2&#65039;&#8419; <strong>Use multiple visitors as a signal</strong>. A single visitor is typically a weak signal by itself but with inaccuracy issues, it becomes even weaker. Multiple visitors from the same company in a short timeframe provide a stronger evidence, especially in the Work-from-home era (where they don't share an office IP).<br><br>3&#65039;&#8419; <strong>Combine multiple providers</strong>. Using multiple data providers can not only increase coverage, but also accuracy when they agree on an identification. When providers that use different technologies e.g. for company vs person-level, match each other, it tends to be quite accurate. With a solution like <a href="https://syftdata.com">Syft</a>, you automatically get access to a world-class de-anonymization/enrichment waterfall that takes care of this for you.<br><br>4&#65039;&#8419; <strong>Combine with first Party signals</strong>. If you identify a company on your website after emailing a prospect there, then you have a strong 1st party signal (the prospect's company and location) and a strong geographic signal (location of visitor). You can combine them to build a stronger confidence. </p><p>If you have any questions, please let us know in the comments below. <br></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://blog.syftdata.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading Signal Intelligence by Syft! Subscribe for free to get new posts.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p></p><div class="footnote" data-component-name="FootnoteToDOM"><a id="footnote-1" href="#footnote-anchor-1" class="footnote-number" contenteditable="false" target="_self">1</a><div class="footnote-content"><p>Which is why they are one of our partners!</p><p></p></div></div>]]></content:encoded></item><item><title><![CDATA[Why we built WhoAmI? ]]></title><description><![CDATA[Bringing transparency to de-anonymization data quality]]></description><link>https://blog.syftdata.com/p/why-we-built-whoami</link><guid isPermaLink="false">https://blog.syftdata.com/p/why-we-built-whoami</guid><dc:creator><![CDATA[Imran Patel]]></dc:creator><pubDate>Wed, 10 Jul 2024 16:46:00 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!ynld!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F033e4dc3-a9b3-4526-9dd7-2546657717dd_1338x830.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://blog.syftdata.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://blog.syftdata.com/subscribe?"><span>Subscribe now</span></a></p><p>Website visitor de-anonymization is all the rage nowadays within the GTM community. It is a foundational piece that powers ABM campaigns, outbound motions, and website content personalization, among other things.</p><p>But every other day there is a debate in the GTM community about which vendor has the highest 'identification rates'?</p><h2><strong>Picking the Right Metrics</strong></h2><p>There is no "one-size-fits-all" answer to this question for two main reasons:</p><ol><li><p><strong>ID rates are highly dependent on the visitor profile</strong>. Which country is the visitor coming from? What is their persona? Are they likely to have an "online" presence? A Construction Tech SaaS targeting contractors in Canada might not identify traffic at the same rate as a B2B SaaS selling to US digital marketers.</p></li><li><p><strong>ID rates vary based on precision</strong>. You can identify visitors at company-level, company and role level, and person-level with diminishing ID rates. Different services offer varying coverage across these granularities. Most offer only company-level identification unlike newer solutions such as <a href="https://syftdata.com/">Syft</a> and <a href="https://rb2b.com/">RB2B</a>.</p></li></ol><p>Finally, the most important consideration is accuracy of identification. ID rates don't tell you whether the ID was correct!</p><p>Given these factors, our advice has been to evaluate multiple vendors, in parallel, and do two basic tests:</p><ol><li><p><strong>The Friends &amp; Co-workers Test</strong>: Visit your website yourself and ask a few of your co-workers and friends to do the same. Check which of you are identified and whether the result matches your current company, role, linkedin.</p></li><li><p><strong>The Signup Test</strong>: Check if the users that signed up were de-anonymized correctly prior to them signing up. This is the best way to check accuracy at scale.</p></li></ol><p>However, performing these side-by-side tests is time consuming. They require you to talk to vendors, go through procurement, deploy these solutions, and then do evaluations. We speak to a lot of folks who are evaluating solutions including ours and this was one of their top frustrations.</p><h2><strong>Introducing WhoAmI</strong></h2><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!ynld!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F033e4dc3-a9b3-4526-9dd7-2546657717dd_1338x830.jpeg" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!ynld!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F033e4dc3-a9b3-4526-9dd7-2546657717dd_1338x830.jpeg 424w, https://substackcdn.com/image/fetch/$s_!ynld!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F033e4dc3-a9b3-4526-9dd7-2546657717dd_1338x830.jpeg 848w, https://substackcdn.com/image/fetch/$s_!ynld!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F033e4dc3-a9b3-4526-9dd7-2546657717dd_1338x830.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!ynld!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F033e4dc3-a9b3-4526-9dd7-2546657717dd_1338x830.jpeg 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!ynld!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F033e4dc3-a9b3-4526-9dd7-2546657717dd_1338x830.jpeg" width="1338" height="830" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/033e4dc3-a9b3-4526-9dd7-2546657717dd_1338x830.jpeg&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:830,&quot;width&quot;:1338,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:81729,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/jpeg&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:null,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!ynld!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F033e4dc3-a9b3-4526-9dd7-2546657717dd_1338x830.jpeg 424w, https://substackcdn.com/image/fetch/$s_!ynld!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F033e4dc3-a9b3-4526-9dd7-2546657717dd_1338x830.jpeg 848w, https://substackcdn.com/image/fetch/$s_!ynld!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F033e4dc3-a9b3-4526-9dd7-2546657717dd_1338x830.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!ynld!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F033e4dc3-a9b3-4526-9dd7-2546657717dd_1338x830.jpeg 1456w" sizes="100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image"><svg role="img" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg"><g><title></title><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>So, we decided to build a tool that makes it easy for you to do the "Friends &amp; Co-workers" Test. Our tool - WhoAmI - helps you decide which vendors have the best coverage and accuracy objectively. With this tool we will identify you using multiple de-anonymization vendors and show you side-by-side results. If you are interested, we will send you a report with aggregated benchmark results from all the submissions as well.</p><p>Our goal is to educate the GTM community about the wonders and limitations of this technology. <a href="https://whoami.syftdata.com/">Please try it out</a> and <a href="mailto:hello@syftdata.com">let us know</a> what you think!</p><div><hr></div><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://blog.syftdata.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Subscribe to get field notes on running modern B2B GTM with better data!</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p></p>]]></content:encoded></item></channel></rss>