Andy Stearman couldn’t bulk-export his own Fathom meeting transcripts, so he wrote a Chrome extension to do it. Five months later that one-button tool has pulled in $20K. It gets roughly 80 visitors a month and converts 23% of them into buyers.
The part that should make every builder sit up: he never built a discovery engine, ChatGPT became one for him. People ask it “how do I bulk export Fathom transcripts,” and it sends them straight to his checkout.
In today’s indie hacker news:
- 💰 A $2/mo Chrome extension cleared $20K on 80 visitors a month
- 🌍 Google’s Genie 3 builds a world you can walk from one sentence
- ✍️ A 362-point essay: prove human effort before you ask for attention
- 📉 An indie dev found 80% of his Apple ad spend bought nothing
- 🔖 Plus: a Cursor $1,400 refund, a .NET coding agent, Homebrew 6.0
TOP STORIES
ONE BUTTON, TWENTY GRAND
💰 A solo dev turned a $2-a-month Chrome extension into $20K in five months
The story: Stearman (u/saucecat2) shipped TranscriptExporter on the Chrome Web Store and described the origin with zero ceremony: “People want their meeting transcripts, the service had no internal way to do it, boom a product was born.” Then the plot twisted. Fathom’s team noticed his v1 was scraping against their terms, and instead of a cease-and-desist they handed him an API beta invite. The extension got rebuilt on OAuth and is now a listed Official Fathom API Partner, so the company he was scraping now feeds him distribution.
The details:
- 822 sales at $29 one-time. A $6.99/mo pro tier (Drive/Dropbox auto-sync) adds 39 subscribers, about $273 in MRR.
- “My cost is $2 per month. 2 bucks. 1 dollar for deployment (Vercel pro split between all my projects) and $1 for the domain.”
- He ranks #1 on Google for “bulk export fathom transcripts,” and by his own words is “basically the only result when you search the problem.”
- 85% of buyers use business email domains: SaaS teams, agencies, sales, real estate, coaches.
- He’s cloned the playbook to a Fireflies.ai version (~50 sales) with a Zoom one in progress.
Why builders care: Traffic stops mattering when you own the exact query a buyer types in pain. The repeatable move: find a missing export, import, or sync button inside a popular SaaS tool, build a thin extension on its public API, then get listed on the tool’s own integrations page so the parent product becomes your sales team. The ChatGPT referrals are the part nobody can engineer yet, and they only land on whoever already owns the answer.
Clone your voice once. Ship every video without re-recording. ElevenLabs Pro trains a voice clone in 30 minutes that sounds like you on every long-form, Short, and podcast you ship. We narrate every video on this newsletter with it. Beats hiring a VO artist on Fiverr or settling for a default TTS bot.
We get a cut if you sign up. Only added for tools we use ourselves.
WALK INTO THE PROMPT
🌍 Google’s Genie 3 turns one sentence into a 3D world you can walk through, for 60 seconds
The story: Genie 3 is a Google DeepMind world model that generates a navigable environment from a text or image prompt and renders the path ahead in real time at 720p, 24fps, as you move. The consumer version, Project Genie, went viral again after its I/O Street View expansion: pick any U.S. spot on Maps, choose an art style, and it builds a world out of 280+ billion Street View photos. The Reddit author who set off this round of buzz kept it honest. “It’s really rough. Low framerate, laggy response, visible bugs. Right now it is a tech demo, not a game you would sit down and play.”
The details:
- Worlds stay coherent for only ~1 minute, with a hard 60-second exploration cap per session.
- Access runs $249.99/month through Google AI Ultra, US-first, 18+ only. There is no public API or SDK.
- It isn’t physics-aware: no real cause and effect, weak multi-agent behavior, shaky character control under latency.
- The lineage moved fast: Genie 2 was 360p with 10-20s memory; Genie 3 is 720p/24fps with a ~1-minute window.
- The real tell is robotics: Waymo fine-tuned Genie 3 to simulate edge cases like wildlife and weather, outputting lidar at 4x speed.
Why builders care: The $250 paywall is a consumer toy price, not a developer signal, and there’s nothing to build on yet. The trajectory is the point. Google is steering this at agents and robotics, and the Waymo synthetic-training use is already live, so anyone working on world models, synthetic data, or text-to-environment tooling is now in the splash zone of where this goes next.
DID YOU EVEN READ IT
✍️ A 362-point HN essay argues you must prove human effort before asking for human attention
The story: Tom Bedor’s essay hit 362 points and 111 comments on Hacker News in about a day. The thesis is one line: “If you are requesting human attention, demonstrate human effort.” It started when a teammate forwarded him AI-generated critique of his design doc with the disclaimer “I didn’t read this.” If the sender wouldn’t spend their own time on it, why should anyone else? The math is the brutal part: 15 seconds of prompting on one end becomes hours of review on the other, and people respond by tuning the whole channel out.
The details:
- Bedor names three proofs of effort: label AI output, add your own commentary, and personally review AI code before asking anyone to review it.
- HN consensus was blunt: “Claude did it” is not an acceptable answer in code review. The human who submits it owns the quality.
- Independent data backs the thesis. Average cold-email reply rates have slid to 3-5%, down from 8.5% in 2019.
- Outreach with genuine, human-verified personalization lifts replies from ~9% to 21%; generic blasts sit at 1-2%.
- A commenter shared the inverse win: AI to analyze scraped public records, but a human did the curation, and the emails got answers.
Why builders care: Every cold sales, hiring, or partnership email you send now lands in an inbox trained to delete zero-effort AI on sight. The fix is mechanical: drop in one signal a human was here, a specific detail from the prospect’s own work or a line proving you read their post. The same screen runs on job applications, support replies, and your pull requests.
THE METRIC APPLE HID
📉 An indie iOS dev found 80% of his Apple Search Ads spend funded keywords that paid nothing
The story: Simone Giammusso (u/MuchAge1486) ran the numbers on his own Apple Search Ads and found about 80% of the budget went to keywords that never produced a paying user. The reason is structural: “Apple’s own dashboard tells you installs and cost per install, but stops there. It has no idea whether those installs ever turned into paying users.” Revenue per keyword simply isn’t exposed natively. So he built ASAPilot, which joins ASA spend to RevenueCat revenue to compute real ROAS, after getting official Apple authorization to touch the API.
The details:
- The keyword that paid: “create calendar from photo,” $0.76 of spend returning $99, over 100x ROAS, invisible until he attributed per keyword.
- A broad term like “calendar” can eat most of the budget and return almost nothing, while a long-tail term quietly prints.
- You can run this yourself in a spreadsheet: export ASA keyword spend, join RevenueCat’s source-keyword data, sort by revenue not installs.
- ASAPilot is free for one campaign, with a €2.99/mo Copilot Pro tier.
- The structural gap is Apple-confirmed; several other tools (Adapty, RevenueCat) exist purely to bridge it.
Why builders care: Apple Search Ads optimizes for installs by default because installs are all it shows you, so if you never close the loop to revenue you’re running a CPI campaign while believing it’s a ROAS campaign. The audit costs an afternoon and zero dollars, and the gap it exposes between spend and actual cash is usually the difference between a profitable channel and a slow leak.
TRENDING TODAY
🤖 Long-context agents are failing in boring, unglamorous ways - A 200K token window isn’t memory, and r/artificial spent the day on the failures nobody demos: the agent rereads the same file across steps, or forgets a constraint from earlier and grabs the wrong tool. The line that stuck: “A lot of agent reliability work is really context architecture work.” Paired with a founder’s confession that AI one-shots features but “the work required to separate slop from what is needed is super hard,” it points one way: AI removes the forcing function of slow, deliberate building, and the discipline has to come from you now.
💸 Micro-SaaS posts got useful when founders dropped the victory lap - One thread cycle, three honest numbers. An AI photoshoot business at $250K ARR shut down because “your value shrinks every time the model improves.” A founder featured in Inc. magazine got zero traffic, zero signups, zero revenue from it: PR is social proof, not a channel. And a CV optimizer hit 250 paying users on $0 ad spend, but churns hard because it works and users cancel once they land the job.
🧠 Gemma 4 dropped four ways at once, and the threads turned into tuning guides - Google shipped four quantized Gemma 4 variants (12B up to 31B QAT) the same day, and r/LocalLLaMA immediately got practical. One PSA on llama.cpp threading showed 16 threads beating 6 by ~80% on a 26B model (49→89 tok/s), with the optimal count being hardware-specific. A crowdsourced VRAM guide maps it out: 8GB runs a 12B, 24GB runs the 31B at ~55 tok/s.
DRAMA
THE AGENT THAT BILLED $1,400
🔥 A Cursor agent looped for an hour and burned $1,400, so the CEO refunded it personally
A user (@mardehaym, of Limestone Digital) watched a Cursor AI agent fall into a loop and chew through $1,400 of tokens in roughly an hour. Cursor CEO Michael Truell stepped in and refunded the whole charge himself. Goodwill, sure, but the r/ChatGPT thread caught the other read fast: top comments flagged the whole post as basically an ad for Limestone Digital, and nobody from Cursor mentioned loop detection or a spend cap.
Why builders care: If you ship agents that spend real money, a hard per-task budget cap is product surface, not a nice-to-have. A CEO refund doesn’t scale, and you won’t get one.
STACK OF THE DAY
🧩 MandoCode
A Claude-Code-style coding agent for .NET and C# developers that needs no API keys: it runs on Microsoft Semantic Kernel plus Ollama, so local models work fully offline. You get project-aware file read/write/search with diff approvals before any change, MCP server support in the Claude Desktop config format, keyless web search via DuckDuckGo, and a built-in task planner that breaks complex requests into steps. Install is one line: dotnet tool install -g MandoCode. It’s MIT-licensed and shipped v0.11.0 today. Early days at 6 GitHub stars, but it’s the rare coding agent aimed straight at the .NET crowd.
Not sponsored. We just feature tools builders would actually use.
BOOKMARKED TODAY
🍺 Homebrew 6.0.0 - The big one is a trust gate: third-party taps now need explicit opt-in before their unsandboxed Ruby runs, ending silent supply-chain attacks through malicious taps. It also starts winding down Intel Macs (Tier 3 in September, no new bottles) and adds brew exec. 1,048 points on HN. Run brew tap --list and audit what you’ve auto-trusted.
🤖 MiMo Code by Xiaomi - An MIT-licensed fork of OpenCode with Xiaomi’s MiMo-V2.5 model baked in, no API key needed for the default setup. It claims 62% on SWE-Bench Pro and says it beats Claude Code on tasks needing 200+ sequential steps. 440 points on HN. Separate from the Xiaomi 1,000 TPS throughput story we covered in #69.
📝 Zed DeltaDB - Operation-level version control: every keystroke is a tracked operation you can undo individually, and it links AI conversations to the exact code they produced. CRDT worktrees let people edit the same file at once without merge conflicts. The bet: reviewing AI changes needs operation-level granularity, not commit-level. 223 points on HN.
Ship to one country, QA it from another. Geo-fenced Stripe checkouts, region-gated APIs, feature flags that only fire in EU. NordVPN's 6,400+ exit nodes across 110+ countries let you test a US-only paywall from EU or hit a EU-only checkout from SF. Bonus: free Meshnet for SSH across your devices.
We get a cut if you sign up. Only added for tools we use ourselves.
Curated by AI, built by a human.