<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Federal Acquisition on k4i.com</title>
    <link>https://k4i.com/tags/federal-acquisition/</link>
    <description>Recent content in Federal Acquisition on k4i.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 13 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://k4i.com/tags/federal-acquisition/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Buy, Build, or Let the Vendor Decide: How Federal Agencies Are Approaching AI Acquisition</title>
      <link>https://k4i.com/buy-build-or-let-the-vendor-decide-how-federal-agencies-are-approaching-ai-acquisition/</link>
      <pubDate>Mon, 13 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://k4i.com/buy-build-or-let-the-vendor-decide-how-federal-agencies-are-approaching-ai-acquisition/</guid>
      <description>&lt;p&gt;One of the more useful contributions of GAO&amp;rsquo;s April 2026 AI acquisitions report (GAO-26-107859) is its taxonomy of the different procurement approaches federal agencies are actually using—not as a policy prescription, but as an empirical account of what agencies have tried, what trade-offs they&amp;rsquo;ve encountered, and where each approach leaves agencies exposed.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Agency-Directed vs. Vendor-Driven&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Some agencies began with a defined requirement and went out to acquire a solution. Others found vendors presenting AI capabilities to them that didn&amp;rsquo;t correspond to any existing requirement—and accepting those offerings anyway. GSA acquired a facility management software platform that included a chatbot feature the vendor added as a bonus, not in response to any stated requirement. VA awarded a task order for medical software that arrived with embedded AI capabilities.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
