What would you do with 5 robots?
Forget what's technically possible today. If you had five Apps who never slept, never got bored, and owned a function each — which five would you hire first? We've been asking this on every call.
Write the article →Thought experiments, what we shipped, what's shipping next and why, what we've learned from talking to customers, and the frustrations we ran into building this.
Forget what's technically possible today. If you had five Apps who never slept, never got bored, and owned a function each — which five would you hire first? We've been asking this on every call.
Write the article →The Web Debugger App shipped. Catches customer-reported bugs, writes tests, fixes them, opens the merge request. Stub — fill in the launch retro.
Walking through the chatbot pattern that routes visitors to the right specialist — and the voting fallback when we don't have what they need yet. Stub.
A single Tool, narrow surface, technical audience that knows what they want. The right shape for a first cofounder-driven launch. Stub.
The hiring metaphor isn't decorative — it changes what the product has to do. Owning a function means surfacing the two things that need a human and handling the thirty-eight that don't.
Notes from the first round of customer-discovery calls. What they actually do, what they pretend to do, and where the hours go. Stub — populate after the discovery cycle wraps.
Inspectable runs are the foundation, not the headline. Pulling the "log you can read on Friday" copy off the live site, and what replaced it. Stub.
On-device frontier inference is now actually fast on Apple Silicon. What this changes for the "run locally only" toggle on the Researcher app. Stub.
Paper Writer + Grant Finder + Calendar Organizer + Networker. How a Suite differs from selling four Apps in a coupon, and why the audience tag matters more than the bundle.
macOS Developer ID, Windows OV cert, the SmartScreen reputation cliff. A timeline of what broke and what fixed it. Stub.