<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Louis Amira</title><link>https://louisamira.com/</link><description>I&#x27;m co-founder and CEO of Circuit &amp; Chisel, which makes UnbiasedAI. Before that I worked at Stripe, Google and Chainlink. I write about how to actually use AI at work and at home, and what it&#x27;s doing to business. Most posts start as X Articles on @louisamira.</description><language>en</language><atom:link href="https://louisamira.com/feed.xml" rel="self" type="application/rss+xml"/><item><title>Your AI sits idle 77% of the year.</title><link>https://louisamira.com/idle-77-percent/</link><guid>https://louisamira.com/idle-77-percent/</guid><pubDate>Tue, 10 Nov 2026 12:00:00 +0000</pubDate><description>It writes about 15x faster than you can read. So the hours that matter most are the ones when you&#x27;re not at your desk.</description><content:encoded><![CDATA[<p>You read about 4 words a second.</p>
<p>I timed four popular AI models writing the same 1,200-word memo. The slowest wrote 60 words a second. The fastest wrote 93.</p>
<p>So even the slow one writes about 15x faster than you can read. Scale that up (slowest AI, and you reading nonstop):</p>
<blockquote><p>An hour: you read 48 pages. It writes 720.</p><p>A workday: you read one long novel. It writes all seven Harry Potter books, with three hours to spare.</p><p>A work week: you read 1,900 pages. It writes 28,800.</p><p>A work year: you read 95,000 pages. It writes 1.4 million.</p></blockquote>
<figure><img src="https://louisamira.com/idle-77-percent/chart.png" alt="Bar chart of pages: you read 48 an hour against your AI&#x27;s 720, then 380 vs 5,760 in a workday, 1,900 vs 28,800 in a week, and 95,000 vs 1,440,000 in a year."><figcaption>Same 15x every time. The gap is what grows.</figcaption></figure>
<p>(Writing isn't working, of course. Plenty of those pages would be junk. But it tells you who the slow one is, and it isn't the AI.)</p>
<p>Now the part that bugs me.</p>
<p>A year has 8,760 hours. A full-time job is about 2,000 of them. Most people only use AI while they're sitting in front of it, so for the other 6,760 hours it just... waits.</p>
<p>That's 77% of the year. Nights, weekends, the commute, the dentist.</p>
<figure><img src="https://louisamira.com/idle-77-percent/year.png" alt="A year drawn as 8,760 squares, one per hour. The 2,000 work hours are gold; the other 6,760 are blue."><figcaption>Each row is a week, each square an hour. Gold is you at your desk.</figcaption></figure>
<p>And the 23% when you <i>are</i> there? You're the bottleneck anyway. It writes 15 pages in the time you read one.</p>
<p>So the cheapest upgrade most people can make isn't a smarter model. It's giving the one you already have a night shift.</p>
<p>That's all a "software factory" is. People throw the phrase around like everyone already knows how to run one. Most don't. Here's the simplest version:</p>
<ul><li>Before you leave, hand it one job that would take a person a full day. Read the last 200 support emails and sort the complaints. Draft three versions of the pricing page. Check 20 competitors' prices.</li><li>Drafts only. Nothing gets sent, bought or deleted overnight. (Rule from my last post: make each mistake small.)</li><li>Ask it to check its own work and put three sentences at the top.</li><li>In the morning, read the three sentences. Open the rest only if something looks off.</li></ul>
<p>Do that every weeknight and the 77% starts working for you.</p>
<p>Showing <i>how</i> to build these, step by step, is most of what we write about at <a href="https://x.com/theunbiasedco">@theunbiasedco</a>.</p>
<p><i>I co-founded <a href="https://x.com/theunbiasedco">@theunbiasedco</a>, which builds all sorts of stuff with (and for) AI agents.</i></p>]]></content:encoded></item><item><title>Your AI coworkers shouldn&#x27;t have a landlord.</title><link>https://louisamira.com/openbot/</link><guid>https://louisamira.com/openbot/</guid><pubDate>Tue, 10 Nov 2026 12:00:00 +0000</pubDate><description>Why I&#x27;m so excited about OpenBot.</description><content:encoded><![CDATA[<blockquote class="twitter-tweet" data-dnt="true"><p lang="en" dir="ltr">💫 Welcome to the <a href="https://t.co/OKwVXQYsdB">https://t.co/OKwVXQYsdB</a> era <a href="https://t.co/Dmf40TBDkN">https://t.co/Dmf40TBDkN</a> <a href="https://t.co/LxJnCjzTA6">pic.twitter.com/LxJnCjzTA6</a></p>&mdash; OpenBot (@0penBot) <a href="https://x.com/0penBot/status/2120273209044201771?ref_src=twsrc%5Etfw">November 10, 2026</a></blockquote>
<p>Grok Bot's recent issues stem from you suddenly having to care which model was powering it. You couldn't see it, and you couldn't bring plans you already pay for. (<a href="https://unbiased.ai/blog/grok-bot-part-2/">We wrote about it on November 9.</a>)</p>
<p>OpenBot fixes all three. Here's why I'm so excited.</p>
<p>The setup screen, in one line: "Sign in with a plan you already have, or use an API key." The big labs are there. As is <a href="https://unbiased.ai/blog/openbot-with-unbiased/">Unbiased AI</a>.</p>
<figure><img src="https://louisamira.com/openbot/setup.png" alt="OpenBot&#x27;s &quot;Connect your AI&quot; screen: OpenAI, Anthropic, Google Gemini, xAI, Unbiased AI, and any OpenAI-compatible endpoint."></figure>
<p>On November 9 I said a bot should work like Google Flights: Google doesn't own planes, it puts all the airlines on one screen. Same idea.</p>
<p>No landlord: it's open source and runs on your own laptop. (Bring your own cloud 🤫?!?) Nobody can change the terms overnight, or evict your bot. Grok Bot runs on a cloud computer, and <a href="https://cursor.com/help/grok-bot/models">its own help page</a> says it doesn't show which model answered you.</p>
<p>Why this team: <a href="https://www.copilotkit.ai/">CopilotKit says</a> the majority of the Fortune 500 use it, and it has 38,000+ GitHub stars. OpenBot itself has 10,000+ more. A friend introduced us (hi <a href="https://x.com/aviel">@aviel</a>!), and we quickly realized we see the future in the same way.</p>
<p>Why Pareto fits: we make blended models, so several models work on every request. You pick it once and stop caring which one is on. Think auto updates. Like your bot read a bunch of textbooks, the news, learned some recipes and workout routines, all while you slept.</p>
<p>That was Grok Bot's promise, before the bill came.</p>
<p>With us under the hood, $10 a month gets <a href="https://unbiased.ai/blog/pareto-26-10/">50M tokens each week</a>. Run far more bots, or feed your main one.</p>
<p>My bet from November 9 stands: by November 30, Grok Bot follows their lead and lets you plug in another company's plan. They should!</p>
<p>If you'd rather not wait and pray, <a href="https://unbiased.ai/blog/openbot-migration-guide/">here's how to move your bot over</a>. You can hand it straight to your agent.</p>
<p>p.s. Remember the Sphere at the top? OpenBot did that. Did it buy the ad space, or just generate an image? Who knows! I bet if you ask it, you just might find out.</p>
<p><i>I co-founded Circuit &amp; Chisel, which makes Pareto. We're partners with OpenBot. Drafted with agents, edited by me.</i></p>]]></content:encoded></item><item><title>Right 91% of the time. Still made $0.</title><link>https://louisamira.com/right-91-percent/</link><guid>https://louisamira.com/right-91-percent/</guid><pubDate>Mon, 09 Nov 2026 12:00:00 +0000</pubDate><description>An AI that only takes good bets, and slips once in a while, can be right almost every time and still make nothing. The question isn&#x27;t how often it&#x27;s right.</description><content:encoded><![CDATA[<p>Say you hand an AI agent $10,000 and tell it to follow one rule:</p>
<blockquote><p>Make me money. Bet $100 at a time, but only when the odds are at least 51–49 in your favor.</p></blockquote>
<p>Seems pretty safe. A 51–49 bet doesn't win every time, but do enough of them and each one is worth about $2 to you (51 wins × $100 – 49 losses × $100 = $200 per 100 bets).</p>
<p>Casino empires hinge on this elementary math.</p>
<p>But AI is (currently) a little different. Every so often the AI misreads one. It thinks it's looking at 51–49, and it's actually 40–60 against. Same $100 on the line, but the return is suddenly –$20.</p>
<p>One mistake erases ten good bets.</p>
<blockquote><p>(10 good bets × $2) + (1 mistake × –$20) = $0</p></blockquote>
<figure><img src="https://louisamira.com/right-91-percent/jar.png" alt="A jar fills with two coins for every good bet, and a single mistake empties it. After 55 bets, it&#x27;s right 91% of the time and holds $0."><figcaption>Ten good bets fill the jar. One mistake empties it.</figcaption></figure>
<p>That's an AI that's right 10 times out of 11. 91%.</p>
<p>In school, that was an A- and a high five from my dad. Here, it's a waste of electricity.</p>
<p>"Cool...but my AI doesn't bet." Psh, that's what you think!</p>
<p>Every time it books, buys, or sends something for you, it's betting that it understood what you meant. Most of the time it did, and you get a few minutes back. Every so often it didn't, and now you own a nonrefundable flight for the wrong Tuesday.</p>
<p>I ran this experiment on myself pre-AI. I bought Bitcoin at about $520 in 2014, felt like a genius selling two of them at $2,700 and $4,200, then bought back in at 15x what I first paid.</p>
<p>Being early? Cheap (albeit lucky).</p>
<p>The expensive part was one wimpy sell. In addition to being lazy, I'm also a wimp!</p>
<p>To recap, Warren Buffett has two rules. Rule No. 1: never lose money. Rule No. 2: never forget Rule No. 1.</p>
<p>For AI, it's going to be awhile before it never loses money. So for now, Rule No. 2 might have to be:</p>
<ul><li>Make each mistake small: a draft instead of a send, or a spending limit</li><li>Watch the mistakes for a few weeks before you hand it the card</li></ul>
<p><i>I co-founded <a href="https://x.com/theunbiasedco">@theunbiasedco</a>, which builds all sorts of stuff with (and for) AI agents.</i></p>]]></content:encoded></item></channel></rss>
