<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Startups on Thede Technologies</title><link>https://thedetech.com/tags/startups/</link><description>Recent content in Startups on Thede Technologies</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 05 Aug 2026 14:47:19 -0500</lastBuildDate><atom:link href="https://thedetech.com/tags/startups/index.xml" rel="self" type="application/rss+xml"/><item><title>The Processing Layer Is Not a Moat</title><link>https://thedetech.com/blog/the-processing-layer-is-not-a-moat/</link><pubDate>Wed, 05 Aug 2026 00:00:00 +0000</pubDate><guid>https://thedetech.com/blog/the-processing-layer-is-not-a-moat/</guid><description>&lt;p>A few months ago, a friend booked a meeting room at a coworking space in Nashville and invited anyone interested in AI to come talk shop on a Friday morning. No agenda, no slides - just builders comparing notes on what&amp;rsquo;s actually working.&lt;/p>
&lt;p>One of those Fridays, a conversation about MCP - Model Context Protocol, the mechanism that lets AI agents interact directly with tools like Jira, Sentry, and GCloud - sent me home to rebuild my entire engineering workflow. I wrote about that in &lt;a href="https://thedetech.com/blog/eliminating-waste-in-the-sdlc/">Eliminating Waste in the SDLC&lt;/a>
. The short version: I gave Claude Code access to the same tools I use, and 12 hours of manual work per week disappeared.&lt;/p></description></item></channel></rss>