<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>AI Frontline: weekly AI briefing and Q&amp;A | Huaqi Future</title>
<link>https://kakeiai.jp/en/insights/</link>
<description>Huaqi Future&#x27;s AI Frontline: a weekly briefing on what AI leaders said and what major companies announced, with source links, plus a Q&amp;A series on practical AI adoption for small businesses.</description>
<language>en</language>
<lastBuildDate>Thu, 22 Oct 2026 09:00:00 +0900</lastBuildDate>
<atom:link href="https://kakeiai.jp/en/insights/feed.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Will AI leak our internal documents?</title>
<link>https://kakeiai.jp/en/insights/ai-qa-data-leak</link>
<guid isPermaLink="true">https://kakeiai.jp/en/insights/ai-qa-data-leak</guid>
<pubDate>Thu, 22 Oct 2026 09:00:00 +0900</pubDate>
<description>Whether data leaks depends on the contract, log handling and what you hand over. This article covers training use, logs, personal data and how we handle originals.</description>
</item>
<item>
<title>How much does AI cost a small business?</title>
<link>https://kakeiai.jp/en/insights/ai-qa-cost-for-smb</link>
<guid isPermaLink="true">https://kakeiai.jp/en/insights/ai-qa-cost-for-smb</guid>
<pubDate>Tue, 20 Oct 2026 09:00:00 +0900</pubDate>
<description>Costs fall into the monthly service fee, AI provider usage fees and internal staff time. This article sets out our published prices, how to estimate usage fees and how to set a cap.</description>
</item>
<item>
<title>AI Weekly, Oct 19: usage gap widens as model prices fall</title>
<link>https://kakeiai.jp/en/insights/ai-weekly-2026-10-19</link>
<guid isPermaLink="true">https://kakeiai.jp/en/insights/ai-weekly-2026-10-19</guid>
<pubDate>Mon, 19 Oct 2026 09:00:00 +0900</pubDate>
<description>The gap between companies that use AI and those that delegate to it, the conditions behind recent price cuts, hard spending caps, and a new data protection review in Japan.</description>
</item>
</channel>
</rss>
