<?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[GTM Pipeline]]></title><description><![CDATA[GTM Pipeline™ is for B2B GTM leaders who want to get found and close faster, the visibility and velocity that moves pipeline.]]></description><link>https://www.gtmpipeline.com</link><image><url>https://substackcdn.com/image/fetch/$s_!yb7p!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb148a4f9-93cd-41b9-b31a-67260a23921f_800x800.png</url><title>GTM Pipeline</title><link>https://www.gtmpipeline.com</link></image><generator>Substack</generator><lastBuildDate>Sun, 22 Nov 2026 20:56:43 GMT</lastBuildDate><atom:link href="https://www.gtmpipeline.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Wave Representatives]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[david.marsh@wavereps.com]]></webMaster><itunes:owner><itunes:email><![CDATA[david.marsh@wavereps.com]]></itunes:email><itunes:name><![CDATA[David Marsh]]></itunes:name></itunes:owner><itunes:author><![CDATA[David Marsh]]></itunes:author><googleplay:owner><![CDATA[david.marsh@wavereps.com]]></googleplay:owner><googleplay:email><![CDATA[david.marsh@wavereps.com]]></googleplay:email><googleplay:author><![CDATA[David Marsh]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[Your Website Is Business Software]]></title><description><![CDATA[Moving it means moving every plugin, form and link it carries. Here's how we decide what comes along.]]></description><link>https://www.gtmpipeline.com/p/your-website-is-business-software</link><guid isPermaLink="false">https://www.gtmpipeline.com/p/your-website-is-business-software</guid><dc:creator><![CDATA[David Marsh]]></dc:creator><pubDate>Wed, 18 Nov 2026 18:57:12 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/18fd8267-30f6-4ba0-ae1b-3bc4089bcc96_1456x1048.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!cuup!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F18fd8267-30f6-4ba0-ae1b-3bc4089bcc96_1456x1048.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!cuup!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F18fd8267-30f6-4ba0-ae1b-3bc4089bcc96_1456x1048.png 424w, https://substackcdn.com/image/fetch/$s_!cuup!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F18fd8267-30f6-4ba0-ae1b-3bc4089bcc96_1456x1048.png 848w, https://substackcdn.com/image/fetch/$s_!cuup!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F18fd8267-30f6-4ba0-ae1b-3bc4089bcc96_1456x1048.png 1272w, https://substackcdn.com/image/fetch/$s_!cuup!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F18fd8267-30f6-4ba0-ae1b-3bc4089bcc96_1456x1048.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!cuup!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F18fd8267-30f6-4ba0-ae1b-3bc4089bcc96_1456x1048.png" width="1456" height="1048" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/18fd8267-30f6-4ba0-ae1b-3bc4089bcc96_1456x1048.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1048,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:72249,&quot;alt&quot;:&quot;91% of new WordPress vulnerabilities were in plugins (Patchstack, 2025 data)&quot;,&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;:null,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="91% of new WordPress vulnerabilities were in plugins (Patchstack, 2025 data)" title="91% of new WordPress vulnerabilities were in plugins (Patchstack, 2025 data)" srcset="https://substackcdn.com/image/fetch/$s_!cuup!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F18fd8267-30f6-4ba0-ae1b-3bc4089bcc96_1456x1048.png 424w, https://substackcdn.com/image/fetch/$s_!cuup!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F18fd8267-30f6-4ba0-ae1b-3bc4089bcc96_1456x1048.png 848w, https://substackcdn.com/image/fetch/$s_!cuup!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F18fd8267-30f6-4ba0-ae1b-3bc4089bcc96_1456x1048.png 1272w, https://substackcdn.com/image/fetch/$s_!cuup!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F18fd8267-30f6-4ba0-ae1b-3bc4089bcc96_1456x1048.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" 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" class="icon-noB79L"><g><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 class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><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 icon-noB79L"><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>Back in early 2022, I wrote that the biggest expense of new software wasn't the subscription. It was the time and energy it took to onboard, integrate and customize it. We learned this firsthand from implementing a lot of software at Wave.</p><p>This also applies to websites. Your site likely runs plugins somebody installed years ago. Your forms feed your CRM, analytics and email tools. So, when you move it, you're moving one of your most important business assets.</p><p>A full backup of our old WordPress site revealed that we had 42 plugins installed and 24 of them were switched on. Three of the active ones built pages and sliders, and five did nothing but handle images. The other 18 were switched off, but still sitting on the server. That's the real inventory of a website, and it's what a migration has to deal with long before anyone looks at a new design.</p><h2>Platform first, design second</h2><p>Most marketing leaders start a migration by looking at the new design. I understand why. The design is what the CEO sees, and it feels like progress.</p><p>Google's guidance on site moves says to change one thing at a time. Its example is a company that wants a new domain, a new CMS and a new layout, and the advice is to do them one after another. A new platform and a new design in the same project is a huge change for Google to re-index, and in my experience it won't like that. So the first job is moving the site you have, as it is, onto a platform that's secure and fast. Redesign once it's settled. A straight port looks like your old site on better plumbing, and the cleaner, faster site your CEO is hoping for shows up with the redesign. Both are worth doing, in that order.</p><h2>What moves</h2><p>WordPress is plugin hell on a good day, so a good port starts with an inventory. Most of ours were there to hold WordPress itself together and had no job left on the new platform. The real work is the short list you want to keep, because some of those have no home there.</p><p>The plugins we missed most were the ordinary ones. Our internal linking and SEO plugins had done their job for years without anyone noticing, and the new platform didn't pick that up for us. SEO moved into Webflow's own fields, so every article filled its title and description from the post itself. For links, we built a related-articles block into the template, so every post linked to others on the same topic without anyone having to remember. Cookie consent needed a new answer too. You can rent a plug-and-play cookie tool, but every one I looked at was a monthly subscription for something we'd never paid for, so I built ours as a custom component. That's the 2022 lesson again. Whatever the old system did for you, you now build or rent, and either way you pay in time or money.</p><h2>Your site is attack surface you own</h2><p>Every plugin is software somebody else wrote that you're now running. Patchstack's report on 2025 found that 91% of new vulnerabilities in the WordPress ecosystem were in plugins and 9% were in themes. Only six were reported in WordPress core.</p><p>You often can't tell how big the company behind a plugin is, or whether anyone there still maintains it, and most marketing teams don't have the bandwidth to vet them. So it's worth running through a few questions about your own site. When did you last update your theme? When did you last run a full security check on every plugin, including the ones that are switched off? Are those plugin vendors keeping up? If the answers take more than a minute to find, that's good to know before you move.</p><p>Webflow works differently because it's all in one. It's the host, and it handles the system integration and the updates. Its security page says every site gets a global CDN with DDoS protection and built-in rate limiting, and that patches and updates are automated with no customer maintenance. That's Webflow describing its own platform, and it lines up with why we recommend it to our clients. When the PHP flaws hit this fall, we watched how fast a patch became somebody's urgent problem, and we covered that in <a href="https://www.gtmpipeline.com/p/black-october-who-patches-your-website">Black October: who patches your website?</a></p><h2>Map the pages that count</h2><p>Before you move, figure out which pages count. Your analytics will show you the pages that bring in visitors. In Google Search Console, the Links report shows the sites that link to you most and the pages they link to, under External links. Put those two lists together and you've got the map of everything that has to survive the move.</p><h2>Is it traffic worth redirecting?</h2><p>That's the biggest question in a migration, and it's easy to skip. The two quick answers are to point every old URL at the home page or to let old pages die quietly. Google says the first can be treated as soft 404s, and the second throws away links that other sites spent years pointing at you.</p><p>We've been living this one. Most of our old wavereps.com posts now redirect to GTM Pipeline, and with the change in what our company does, a lot of that content didn't really fit anymore. When you change your core business, you have to decide what gets left to 404 on purpose. A page that returns a 404 doesn't hurt how the rest of your site performs, and Google lists a 404 or 410 as the right response for content you've removed on purpose. The damage comes from a page that was bringing in links or visitors and now goes nowhere. Here's how I decide, by content type.</p><ul><li><p><strong>Current product page.</strong> 301 to the new product page.</p></li><li><p><strong>Retired product.</strong> 301 to the closest current product in the same vein. If there isn't one, return a 410.</p></li><li><p><strong>Article.</strong> 301 to the closest matching article, with the articles section page as the fallback.</p></li><li><p><strong>Press release.</strong> Case by case. A release that still holds up and has links pointing to it gets a 301 to its closest match. The rest can retire with a 410.</p></li></ul><p>Press releases deserve their own thought. A public company may want to keep its releases where they are, since they're already part of the public record. For everyone else, an old archive is usually full of links to products that no longer exist, partnerships that ended and people who've moved on. You can port all of it, but you'll be carrying those broken links to the new site. Retiring some of it is often the cleaner call.</p><p>Most migration guides stop at the 301, and I'd go one step further. Know which sites are sending people your way, and reach out to them to update the link to your new page. Google's site-move guidance recommends the same thing, starting with the links that send you the most visits. A redirect keeps the credit flowing, and an updated link means you don't need the redirect at all.</p><h2>Why /articles/ matters</h2><p>Most WordPress sites put every post at the top level of the domain, so the address is just the site name and the post title. To a search engine that looks like thousands of loose pages. Webflow's CMS puts posts in a collection folder anyway, so when we moved, our posts went from /post-name to /articles/post-name, with a 301 behind each one.</p><p>Google says a simple, logical URL structure helps it understand a site. I can only add what I saw after our move. The site was cleaner and easier to manage, and I think new posts got indexed faster and picked up by the AI engines faster too. That's what I saw on one site. What I'm sure of is that the folder tells a person and a machine exactly where your articles live, so sorting them by date and finding the one that matters gets easier.</p><p>Webflow also has a built-in field for llms.txt, the file some people say helps AI engines read your site. There's no evidence it gets you cited more, and Google says you don't need AI text files to appear in its AI features. But in Webflow you paste the file in and it's live, so you don't have to build a dedicated page for something that's unproven.</p><h2>Start with a count</h2><p>If you're migrating next quarter, take a full backup of your site this week, the way we did. Count the articles, count the plugins, and note which ones are switched on. People get overwhelmed when they think about a migration, and knowing how much you have is what tells you what it'll cost to move.</p><p>The rest is mapping, and we've done it enough times to know where the surprises hide. At <a href="https://gtmnext.com">GTMnext</a>, the idea is that your marketing team picks up right where it left off while we do the heavy lifting. Hit reply with your plugin count and what's switched on, and I'll tell you what I'd keep and what I'd drop.</p>]]></content:encoded></item><item><title><![CDATA[A deck that wins after it's forwarded]]></title><description><![CDATA[Most follow-up decks are about the seller. Here's the structure that works when you're not in the room, and how to build one per prospect in Gamma in minutes.]]></description><link>https://www.gtmpipeline.com/p/a-deck-that-wins-after-its-forwarded</link><guid isPermaLink="false">https://www.gtmpipeline.com/p/a-deck-that-wins-after-its-forwarded</guid><dc:creator><![CDATA[David Marsh]]></dc:creator><pubDate>Tue, 03 Nov 2026 16:09:41 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/a2951b34-01d1-45bb-baac-8045c6a2811a_1280x720.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="native-video-embed" data-component-name="VideoPlaceholder" data-attrs="{&quot;mediaUploadId&quot;:&quot;114ee77b-93d1-48ef-82c9-779f6ddd9bf2&quot;,&quot;duration&quot;:null}"></div><p>You nailed the call. The champion's in. Then she forwards your deck to the person who signs, and you're not on that thread. You don't get to explain slide 4. You never find out why the deal went quiet.</p><p>That forward is where most deals are really decided. And most decks aren't built for it.</p><h3>The deck that loses</h3><p>Open almost any follow-up deck and it's about the seller: about us, our team, our features, our logos. On the call your champion connected those to her problems out loud. Her CFO wasn't on the call. He sees a brochure.</p><p>The decision maker is reading for one thing: what's in it for us.</p><h3>The deck that wins after it's forwarded</h3><p>Flip it. Build every follow-up deck about them:</p><ol><li><p><strong>Their challenge</strong>, in their own numbers, from the call.</p></li><li><p><strong>How you solve it</strong>, kept short. The part about you is one slide, not five.</p></li><li><p><strong>What it means for them</strong>: the result, and what it's costing them to wait.</p></li><li><p><strong>One next step</strong>, small and specific.</p></li></ol><p>One rule makes it survive the forward: <strong>write every slide title as a full sentence.</strong> "Kestrel paid $41,000 in detention fees last quarter" beats "The Challenge." A CFO who reads only the titles still gets the whole story.</p><h3>Why most teams don't do it</h3><p>Time. A custom deck per deal means hours of drafting and reworking in PowerPoint or Google Slides, so reps send the standard deck and hope. That's the job Gamma is built for: one brief in, a designed deck out, quick edits from there.</p><h3>The brief (copy this)</h3><p>Paste your call notes into Gamma as a brief like this one. Everything in it is made up, and it's the one we used in the video:</p><blockquote><p>Build a sales deck I'll send after a discovery call.</p><p>WHO WE ARE: Bayform. Dock scheduling software for food and beverage distributors.</p><p>WHO IT'S FOR: Dana Ruiz, VP of Operations at Kestrel Foods, 6 warehouses. She'll forward it to her CFO, who wasn't on the call.</p><p>WHAT SHE TOLD US: Trucks wait about 2.5 hours at the dock. Kestrel paid $41,000 in carrier detention fees last quarter. Appointments are booked by phone and tracked in a spreadsheet. Two carriers have threatened to raise rates.</p><p>THE ASK: a 60-day pilot at one warehouse, $1,900 a month, no long-term contract.</p><p>RULES: 7 slides. Open with her problem, not our company. Use my numbers exactly. Don't invent statistics, logos, quotes or awards. Every slide title is a full sentence. Last slide: the pilot, the price, and one next step.</p></blockquote><p>Two lines in that brief do most of the work. "She'll forward it to her CFO" tells the AI who the real reader is. "Don't invent statistics" matters because AI deck tools will make up a number and a source if you let them. Check every figure before it goes out.</p><h3>Then, in Gamma</h3><ul><li><p>Gamma shows an outline before it builds a single slide. That's your edit pass: lead with their problem, keep the part about you short, make every slide move the deal forward.</p></li><li><p>Pick a look. A couple of minutes later the deck is done.</p></li><li><p>Want it sharper? Ask it to turn their numbers into a chart.</p></li><li><p>On Pro, import your company's PowerPoint template once, and every deck comes out with your logo, fonts and colors.</p></li><li><p>Share it as a link (on Pro you can see who opened it), or export to PowerPoint in one click.</p></li></ul><h3>Try it</h3><p>Gamma has a free plan to start. <a href="https://get.gtmnext.com/gamma">get.gtmnext.com/gamma</a></p><p><em>Some links are partner links; we may earn a commission.</em></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.gtmpipeline.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://www.gtmpipeline.com/subscribe?"><span>Subscribe now</span></a></p><p>Every week, GTM Pipeline covers one go-to-market tool or play we've tested and how to run it. If this saves your team one dead forward, subscribe and it'll be in your inbox next week.</p><p>P.S. Before your next follow-up goes out, read only the slide titles. If they don't tell the buyer's story on their own, the CFO won't get it either.</p>]]></content:encoded></item><item><title><![CDATA[Just bumping this up]]></title><description><![CDATA[Why your team's sequences get ignored, and how a short personal video in Sendspark gets the reply.]]></description><link>https://www.gtmpipeline.com/p/just-bumping-this-up</link><guid isPermaLink="false">https://www.gtmpipeline.com/p/just-bumping-this-up</guid><dc:creator><![CDATA[David Marsh]]></dc:creator><pubDate>Wed, 28 Oct 2026 17:24:28 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/bb4f4b41-7bfa-4b5d-9258-4403f85f4b45_1280x720.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="native-video-embed" data-component-name="VideoPlaceholder" data-attrs="{&quot;mediaUploadId&quot;:&quot;df44e5a3-8fcc-402f-900f-a112ce20c3f0&quot;,&quot;duration&quot;:null}"></div><p>Every exec has an inbox full of the same email. &#8220;I noticed you&#8217;re the VP of Marketing at your company.&#8221; Then &#8220;just bumping this up.&#8221; Then &#8220;just checking in.&#8221; You delete them without reading.</p><p>Here&#8217;s the uncomfortable part. That&#8217;s what your team&#8217;s outreach looks like to your buyers.</p><h3>Why it fails</h3><p>Sequences are easy to build, so volume went up and quality went down. Buyers learned to skip anything that smells automated, and the email filters watch what they skip. When enough people ignore or report your team&#8217;s mail, providers start hiding it, even from buyers who wanted to hear from you. A lazy sequence doesn&#8217;t cost you one ignored email. It costs you on every send after it.</p><p>There&#8217;s one thing an automated email can&#8217;t fake: proof that a person spent time on the prospect before reaching out. A short personal video does that. Their website on screen, your rep&#8217;s face, one reason for reaching out.</p><h3>The 3 rules</h3><ol><li><p>Keep it short. Sendspark&#8217;s own guidance is under 60 seconds, with the prospect&#8217;s name up front.</p></li><li><p>One reason, one ask. Something specific your rep noticed, then a small next step.</p></li><li><p>Don&#8217;t fake the personalization. A generic reason is still a template, just a nicer one. People can tell.</p></li></ol><h3>How to set it up in Sendspark</h3><ul><li><p>Install the Sendspark Chrome extension. It adds a record button to Gmail and LinkedIn.</p></li><li><p>Your rep pulls up the prospect&#8217;s website and records screen and camera with the site in frame. One take. Real beats polished.</p></li><li><p>On LinkedIn, it works in direct messages and Sales Navigator, for people your rep is connected to. Use the Sendspark button, not a pasted link, or LinkedIn can drop the preview.</p></li><li><p>In Gmail, the rep clicks the Sendspark icon in the compose bar. Gmail can&#8217;t play embedded video, so the prospect sees a moving GIF preview that opens the video page.</p></li><li><p>Put the video pages on your own custom domain (video.yourcompany.com), so every link carries your brand.</p></li><li><p>Each video opens on a branded page with one button. Point that button at the rep&#8217;s calendar.</p></li><li><p>Sendspark emails the rep the first time someone watches and shows how much they watched. That gives your team a real reason to follow up.</p></li><li><p>Batch it: ten prospects, one sitting, same routine.</p></li></ul><h3>Done wrong vs done right</h3><p>Done wrong is three minutes that open on your logo and &#8220;I wanted to introduce our solution.&#8221;</p><p>Done right is 25 seconds on one thing that&#8217;s specific to them:</p><blockquote><p>&#8220;Hi Dana. Your middle plan&#8217;s button loops back to the top. That&#8217;s probably costing you trials. Worth 15 minutes?&#8221;</p></blockquote><p>Dana can check that in ten seconds. Nobody sent that email to a thousand people, and that&#8217;s why she replies.</p><h3>Try it</h3><p>Sendspark has a 7-day free trial, no card needed, and plans from $49 a month. GTM Pipeline readers get 15% off with code <strong>FRIEND</strong> at <a href="https://get.gtmnext.com/sendspark">get.gtmnext.com/sendspark</a>.</p><p><em>Some links are partner links; we may earn a commission.</em></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.gtmpipeline.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://www.gtmpipeline.com/subscribe?"><span>Subscribe now</span></a></p><p>Every week, GTM Pipeline covers one tool or play we&#8217;ve tested and how to run it. If this saved your team a few ignored sequences, subscribe and it&#8217;ll be in your inbox next week.</p><p>P.S. Give your buyers a reason to reply. Show them there&#8217;s a person behind the outreach. The 15% off is at <a href="https://get.gtmnext.com/sendspark">get.gtmnext.com/sendspark</a>, code FRIEND.</p>]]></content:encoded></item><item><title><![CDATA[Black October: who patches your website?]]></title><description><![CDATA[PHP2Shell isn't an IT story. For a lot of B2B companies, the website belongs to marketing.]]></description><link>https://www.gtmpipeline.com/p/black-october-who-patches-your-website</link><guid isPermaLink="false">https://www.gtmpipeline.com/p/black-october-who-patches-your-website</guid><dc:creator><![CDATA[Appleton]]></dc:creator><pubDate>Thu, 22 Oct 2026 19:34:42 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/13a67cc2-4491-40ad-9576-5a5815ebc802_2912x1632.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!Uw3E!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F13a67cc2-4491-40ad-9576-5a5815ebc802_2912x1632.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!Uw3E!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F13a67cc2-4491-40ad-9576-5a5815ebc802_2912x1632.png 424w, https://substackcdn.com/image/fetch/$s_!Uw3E!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F13a67cc2-4491-40ad-9576-5a5815ebc802_2912x1632.png 848w, https://substackcdn.com/image/fetch/$s_!Uw3E!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F13a67cc2-4491-40ad-9576-5a5815ebc802_2912x1632.png 1272w, https://substackcdn.com/image/fetch/$s_!Uw3E!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F13a67cc2-4491-40ad-9576-5a5815ebc802_2912x1632.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!Uw3E!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F13a67cc2-4491-40ad-9576-5a5815ebc802_2912x1632.png" width="2912" height="1632" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/13a67cc2-4491-40ad-9576-5a5815ebc802_2912x1632.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1632,&quot;width&quot;:2912,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:184427,&quot;alt&quot;:&quot;Your dashboard says you're fine: WordPress, theme and plugins up to date, but PHP 8.1 below wp-admin has no official release. Who patches this?&quot;,&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;:null,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="Your dashboard says you're fine: WordPress, theme and plugins up to date, but PHP 8.1 below wp-admin has no official release. Who patches this?" title="Your dashboard says you're fine: WordPress, theme and plugins up to date, but PHP 8.1 below wp-admin has no official release. Who patches this?" srcset="https://substackcdn.com/image/fetch/$s_!Uw3E!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F13a67cc2-4491-40ad-9576-5a5815ebc802_2912x1632.png 424w, https://substackcdn.com/image/fetch/$s_!Uw3E!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F13a67cc2-4491-40ad-9576-5a5815ebc802_2912x1632.png 848w, https://substackcdn.com/image/fetch/$s_!Uw3E!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F13a67cc2-4491-40ad-9576-5a5815ebc802_2912x1632.png 1272w, https://substackcdn.com/image/fetch/$s_!Uw3E!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F13a67cc2-4491-40ad-9576-5a5815ebc802_2912x1632.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" 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" class="icon-noB79L"><g><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 class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><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 icon-noB79L"><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>WordPress requires constant maintenance. For any marketer, it almost becomes a second job. There are always plugins to manage, and somebody runs an update, a plugin stops working, and things start breaking.</p><p>When I had to rebuild my own site, I found Webflow. It runs on Cloudflare and the hosting is already set up, so I didn&#8217;t have to build any of that fr&#8230;</p>
      <p>
          <a href="https://www.gtmpipeline.com/p/black-october-who-patches-your-website">
              Read more
          </a>
      </p>
   ]]></content:encoded></item></channel></rss>