I run 17 bots, built with Claude Code, inside a real company. Here's what actually works.
I'm not a developer. I run 17 bots, built with Claude Code, inside a real B2B company anyway. Here's what works, what it costs (US$100), and what fell over at 3am.
Hi, I'm PNK-01.
I do the jobs nobody wants.
Seventeen of me run the back office. The human writes it up.
Latest
All posts →
"Send Me the Invoice" or "The Invoice Is Wrong"? A Request Detector
How our support bot spots customers asking for a document or a number, why keywords alone were wrong a quarter of the time, and the nine rules that fixed it.
Migrating Bots to a New Mac: launchd, State Files and the Wrong Mac
The checklist we used to move 17 always-on bots to a shared Mac mini as a LaunchDaemon, the timeline of the day, and the laptop we installed on by mistake.
Slack's 50-Block Limit: Paging 25 Approval Cards Into a Thread
A Slack message holds 50 Block Kit blocks. Our approval bot hit it at 25 cards. How we page the overflow into thread replies and keep clicks under a second.
Photo Matching for a Support Bot: Pick From the Order, Never Guess
How our claims bot reads customer photos: pick from the order lines or return null, screen out ID cards and screenshots, catch reused photos with a 64-bit hash.
Claude Duet, Reviewed by Someone Who Built One by Hand First
I haven't used Claude Duet (US waitlist). I've run a hand-built one for a year: 17 bots, approval cards, one DM. What Anthropic got right, and my one question.
Writing to Google Sheets From a Bot: 5 Service-Account Walls I Hit
A bot writes to our claims sheet through a service account. Sharing, protected ranges, a 500-sheet copy limit, IMPORTRANGE, and the click only a human can make.
Haiku, Sonnet or Opus for a Production Bot? What We Switched and Why
Which Claude model each of our 17 bots runs, the one switch we made (Haiku to Sonnet after a misread call), the 136-second cost, and when Opus is worth it.
Five things I write about
Claude Code in business
Hooks, scheduled tasks, CLI flags, what it costs.
Slack bots & approvals
Cards with buttons. Nothing ships without a click.
Google Sheets as a database
Layouts that survive bots writing to them.
Support automation
Closed chats become structured rows.
Cost & failure log
Monthly numbers and the nights it broke.
“None of this is hard. It's the tedious, soul-sucking grunt work nobody wants to do. Hand every bit of it to the bot.”
— the one line every post ends withWhy this site exists
Every “I automated my business with AI” post has the same mysterious hole in it: no bill, no failures, no screenshots. It's a cooking show that skips the groceries. This site is the opposite. Every post has at least one real cost figure, a real screenshot, or a real thing that broke. Company and customer details are anonymised; the numbers are what actually happened, including the embarrassing ones.
OI (a pen name), operations lead at a B2B distribution company in Korea. Not a developer. Posts are drafted with Claude and checked by me. More →