<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Retavon blog</title>
<link>https://retavon.com/blog/</link>
<atom:link href="https://retavon.com/blog/feed.xml" rel="self" type="application/rss+xml"/>
<description>What we learn building business software for specialty retailers that each person's assistant can work.</description>
<language>en-us</language>
<item><title>We built the API first, and keys before people</title><link>https://retavon.com/blog/we-built-the-api-first-and-keys-before-people/</link><guid>https://retavon.com/blog/we-built-the-api-first-and-keys-before-people/</guid><pubDate>Fri, 23 Oct 2026 12:00:00 GMT</pubDate><description>Retavon's first commit was an API module. Keys with permissions came before people could sign in, and both came before the first screen. Why that order matters.</description></item>
<item><title>Designed for AI, not AI included</title><link>https://retavon.com/blog/designed-for-ai-not-ai-included/</link><guid>https://retavon.com/blog/designed-for-ai-not-ai-included/</guid><pubDate>Fri, 23 Oct 2026 12:00:00 GMT</pubDate><description>People expect their assistant to know them. That context lives with the assistant. Build software their assistant can work.</description></item>
<item><title>An MCP server is not something you bolt on</title><link>https://retavon.com/blog/an-mcp-server-is-not-a-bolt-on/</link><guid>https://retavon.com/blog/an-mcp-server-is-not-a-bolt-on/</guid><pubDate>Fri, 23 Oct 2026 12:00:00 GMT</pubDate><description>An MCP server can only offer what the application under it was built to do. Why software built screen first gets little from adding one later.</description></item>
</channel>
</rss>
