<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>B2B on Tim&#39;s log</title>
    <link>https://luu.is/en/tags/b2b/</link>
    <description>Recent content in B2B on Tim&#39;s log</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 Hi, I&#39;m Tim</copyright>
    <lastBuildDate>Wed, 22 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://luu.is/en/tags/b2b/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>The hidden friction of running a hybrid B2B trade portal</title>
      <link>https://luu.is/en/posts/avoiding-traps-hybrid-architectures-b2b-portal/</link>
      <pubDate>Wed, 22 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://luu.is/en/posts/avoiding-traps-hybrid-architectures-b2b-portal/</guid>
      <description>Decoupling our B2B customer portal from WordPress saved us from a massive database migration, but it introduced a complex web of logic drift and cache lag. Here is how we managed the coordination overhead.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://luu.is/en/posts/avoiding-traps-hybrid-architectures-b2b-portal/cover.png" />
    </item>
    
    <item>
      <title>We spent a year burning marketing cash on vanity leads before we fixed our trade pipeline</title>
      <link>https://luu.is/en/posts/burning-marketing-cash-vanity-leads-trade-pipeline/</link>
      <pubDate>Sat, 31 Aug 2024 16:45:04 +0000</pubDate>
      
      <guid>https://luu.is/en/posts/burning-marketing-cash-vanity-leads-trade-pipeline/</guid>
      <description>How we stopped chasing high-volume retail leads, rebuilt our HubSpot tracking, and focused on the 120 trade accounts that actually drive our revenue.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://luu.is/en/posts/burning-marketing-cash-vanity-leads-trade-pipeline/cover.png" />
    </item>
    
  </channel>
</rss>
