<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Erlend Førsund — Insights</title>
    <link>https://erlendforsund.lovable.app/en/innsikt</link>
    <description>Strategic perspectives on B2B visibility, positioning, and leadership in an AI-driven world.</description>
    <language>en</language>
    <lastBuildDate>Tue, 14 Jan 2025 12:00:00 +0100</lastBuildDate>
    <atom:link href="https://erlendforsund.lovable.app/en/rss.xml" rel="self" type="application/rss+xml"/>
    
    <item>
      <title>Why B2B visibility is now a leadership issue</title>
      <link>https://erlendforsund.lovable.app/en/innsikt/visibility-leadership-issue</link>
      <description>The mechanisms that determine how your company is discovered have shifted. This is no longer a marketing problem — it's a strategic one.</description>
      <pubDate>Sun, 01 Dec 2024 12:00:00 +0100</pubDate>
      <guid isPermaLink="true">https://erlendforsund.lovable.app/en/innsikt/visibility-leadership-issue</guid>
    </item>
    
    <item>
      <title>AI-driven buying: What executives need to understand</title>
      <link>https://erlendforsund.lovable.app/en/innsikt/ai-driven-buying</link>
      <description>Your buyers are increasingly relying on AI systems to research, compare and shortlist suppliers. Here's what that means for how you invest in visibility.</description>
      <pubDate>Fri, 01 Nov 2024 12:00:00 +0100</pubDate>
      <guid isPermaLink="true">https://erlendforsund.lovable.app/en/innsikt/ai-driven-buying</guid>
    </item>
    
    <item>
      <title>The case against more content</title>
      <link>https://erlendforsund.lovable.app/en/innsikt/case-against-content</link>
      <description>Most B2B companies don't need more content. They need clarity about what to say, to whom, and why it matters.</description>
      <pubDate>Tue, 01 Oct 2024 12:00:00 +0200</pubDate>
      <guid isPermaLink="true">https://erlendforsund.lovable.app/en/innsikt/case-against-content</guid>
    </item>
    
  </channel>
</rss>
