A pixel desktop cat earned $150 on its first day

The Case: $150 in a day against $1,000 in a year

What he does. Simon, a designer, sells a pixel cat that lives on your desktop and reacts to your mouse, your typing, and your AI agents' activity.

Backstory. He spent about a year running a reading-notes app that took three months to build and made roughly $1,000 across the whole year — understood by everyone, bought slowly by almost no one. Then he built the opposite: no rational pitch, no habit to form, just a creature that responds. The window that makes it land in 2026 is that millions of people now spend hours watching agents work with nothing on screen acknowledging it. That's newly created dead ambient space, and a person who can draw is the one who can fill it.

Product. - Always-on desktop pixel companion - Reacts to mouse movement and typing - Reacts to what your AI agents are working on - No server; nothing leaves the machine (his claim, stated twice in the thread) - Design spec is emotional, not functional: no explanation required

Pricing. Not disclosed. One-time purchase with no subscription mentioned; one commenter reports buying it inside the thread.

Key numbers. - Reading app build time: ~3 months - Reading app revenue: ~$1,000 over ~1 year - Cat revenue, day 1: ~$150 - Days live when he posted: 2 (he says 3 in a same-day comment reply) - Reddit thread: 1,449 points, 451 comments - Servers behind the cat: 0 (his words: "It even have no server") - Confirmed in-thread purchases: 1 ("i just bought it") - Cat build time: not disclosed. A commenter calls it a "weekend project"; Simon never says.

Stack. Not disclosed. The only architectural fact he states is that there's no server. macOS is implied by commenters, not confirmed by him.

Why this works (and what most readers will miss)

1. The pitch fits in one frame. The reading app needed four bullet points to explain itself: save what you read, organize quotes, revisit thoughts, build a habit. The cat needs a GIF. When comprehension and desire happen in the same second, you skip the entire education step that kills slow-converting utility products.

2. Zero server means zero shift schedule. No backend, no migrations, no uptime, no support queue for sync bugs. That's near-total margin on every sale and, more importantly, a product that cannot page him at 2am. Most $1K/year apps aren't failures of demand. They're jobs that pay $83/month.

3. Nobody in the thread priced the input signal. The comments went to Tamagotchi retention and keylogger paranoia. They skipped the one genuinely new thing: the cat reads agent state. Cute desktop pets have existed since 1997. A desktop pet that knows when your agent is mid-run has existed for about three days, and it's the only part of this product that isn't a nostalgia play.

The Distilled Read

Ship the thing that needs nobody. Three months of building bought him a product that returned about $1,000 in a year and still requires him to exist. Two days of the cat being alive bought him $150 and requires nothing — no server to keep warm, no account system to reset, no monthly email to anyone. That's the real split in the case, and it has nothing to do with pixel art. A product with a server has a shift schedule; a product without one has a price. Before you write a line of code, ask what this thing will demand of you every month for the next three years. If the answer isn't "nothing," you're not building a product, you're interviewing for a job you'll pay to keep.

Treat the cat as a template, not a product. He didn't build a cat. He built a mascot runtime — desktop overlay, input hooks, agent-state listener, sprite sheet — and named the first one. The cat is a skin. So is the dog, the ghost, the little slime, the branded mascot you co-release with a CLI tool that pushes it to their entire user base. Every one of those ships in 72 hours once the engine exists, and each one is a fresh launch post with a fresh screenshot. The mistake he's about to make is treating this as one product to nurture rather than a factory to run. Skin #2 should already be drawn.

Score it as a bet, not a revelation. Run the numbers honestly. Capital at risk: near zero. Time to revenue: 2 days against 3 months. Upside: asymmetric, because marginal cost is zero and a good day scales without adding work. Decay risk: the highest line item on the sheet, because delight decays and pixel art is the most clonable asset class in software — someone will ship a copy for $4 within a month. That combination doesn't say "go all in on cats." It says run twenty of these, expect fifteen to do nothing, and never spend three months on one again. And reframe the reading app while you're at it: it wasn't a failure. It was a $1,000 data point held far too long at the wrong position size. My arithmetic, not his: $1,000 spread over a year averages about $2.74/day, and his first cat day was ~$150. He didn't discover that emotion beats utility. He discovered what happens when you stop making one bet the whole portfolio.

The screenshot is the distribution channel. 1,449 upvotes, no marketing budget, no audience play — because the product records its own ad. That's the durable advantage of emotional products: the demo compresses to eight seconds and the viewer does the copywriting for you in the comments. But cold posting is a 1-in-30 game and one thread is luck, not a channel. The move now is to go where the agent-watchers already sit — the CLI tool Discords, the coding-agent subreddits, the vibe-coder servers — and hand out a free skin for two weeks. Watch which tribe screenshots it without being asked. That tribe pre-orders skin #3 before you draw it.

The moat isn't cute. It's permission. Read the keylogger fight again: people openly worried the app hooks their keyboard, and bought it anyway. He just got install rights and input access on machines that would never grant either to a productivity tool, and he got them for the price of one drawing. Cuteness is the cheapest known way past a permission dialog. Eighteen months from now, an always-on desktop face that knows what your agents are doing is a real category with real money in it, and the fight will be over who already has a sprite on screen when the agents need to say something. Here's the trap nobody in the thread named: the no-server purity that makes today's margin also caps tomorrow's. The moment you want the cat to remember you, carry personality across sessions, or speak for your agents, you need state — and state needs recurring revenue, and recurring revenue is a job again. The winners will charge one-time for the skin and monetize the surface. The corpses will bank the $150, conclude that cute sells, and go back to building serious apps.

Steal-the-Playbook

1. Pick one desktop tribe, not "desktop toys." People who run coding agents eight hours a day and stare at a scrolling terminal. That's your first skin's audience, and their dead time is your product spec.
2. Build the overlay before the art. Tauri (Rust) for cross-platform or SwiftUI if you're macOS-only. Transparent always-on-top window, input event listener, one file watcher on your agent's log output. Give it two weekends, not three months.
3. Draw exactly five states in Aseprite ($19.99). Idle, typing, mouse-chase, agent-running, agent-finished. Five states is a complete personality; anything more is you avoiding launch.
4. Sell one-time at $9-$15 through Lemon Squeezy or Gumroad. No trial, no account, no login. Notarize it with an Apple Developer account ($99/yr) so the Gatekeeper warning doesn't eat your conversion, and say "no server, nothing leaves your machine" on the sales page in bold — the trust objection is coming whether you address it or not.
5. Post the GIF, not the pitch. One 8-second recording to r/SideProject, X, and the two Discords where your tribe lives. Then ship skin #2 within 72 hours, aimed at whoever screenshotted skin #1.

Stack: Tauri + Aseprite + Lemon Squeezy + Apple Developer account. ~$120 first-year cost, two weekends to first dollar.