ike | カウシェCTO

Web 1.0 came with new channels: - email, search, link sharing, etc Web 2.0 too: - feeds, creators, viral invites, etc Mobile: - app stores, SMS invites, vertical vid, mobile ads What about AI? I’ve been complaining that AI hasn’t come with much. But we’re seeing a big growth channel opening now: Products that are built as APIs/CLIs that can be pulled into new projects by Codex/Claude on the fly Maybe the “AI-native hotel app” doesn’t mean a mobile booking app with an AI chat panel. It means a CLI that can book a hotel for you, that an AI agent can pull into a bespoke answer or project or into code. Bolting on an AI chat panel is this generation’s weak form of AI. Maybe the full reinvention involves making it agent-first not human-first and once you start looking at it that way, a lot of existing products suddenly feel mis-specified. they’re built as destinations, but agents don’t want destinations. they want capabilities. composable, callable, reliable capabilities. So instead of “go to Expedia” or “open the app,” the future interaction is more like: an agent assembles a workflow on the fly. it pulls a flight search tool, a hotel booking tool, maybe a weather model, maybe even your personal preference graph. none of these are full products in the traditional sense. they’re more like endpoints with taste and state. This flips distribution completely. historically you win by owning the surface area. seo, app store ranking, homepage traffic. in an agent world, you win by being the default callable primitive. the thing that shows up again and again in agent-generated plans because it works, has clean interfaces, and returns structured outputs. distribution shifts from “top of funnel” to “top of call stack.” And the crazy part is this might actually compress product surface area dramatically. the best products might look more like tight, extremely well-designed CLIs with opinionated defaults rather than sprawling UIs. almost like the stripe api moment, but for everything. imagine if every vertical had a “stripe-level” primitive that agents preferentially use. there’s also a weird inversion of brand here. humans used to choose brands. now agents will. so the brand becomes partially machine-legible. reliability, latency, error rates, schema clarity. you can almost imagine “agent seo” where the ranking factors are things like success rate across thousands of agent runs, or how easy your tool is to integrate in a chain-of-thought execution loop. This also suggests a new kind of moat. not just data or network effects, but integration depth with agent ecosystems. if claude or codex or openclaw learns that your tool is the safest way to accomplish X, it gets baked into prompts, templates, maybe even fine-tunes. you become a default. and defaults, historically, are insanely sticky. The contrarian take is that most current “AI features” are a local maximum. chat panels, copilots, assistants. they’re transitional. the real end state might look closer to invisible infrastructure that agents orchestrate. the ui is just a debug layer for humans to peek into what the agents are doing. so maybe the new growth channels for ai look like: - being callable - being composable - being reliable at scale in agent loops - being embedded in agent templates and workflows - being the default primitive in a given domain and if that’s right, then the question for any new product isn’t “what’s the ui” or even “what’s the killer feature.” it’s “what’s the minimal, highest-leverage capability we can expose such that agents will repeatedly choose us when building something new.”

日経新聞に取り上げていただきました。 スタートアップへの転職、40歳以上は10年前の7倍以上に増えているそうです。 自分もその一人。 40代でスタートアップCFOになった理由はシンプルで、「まだ挑戦できる場所にいたかった」から。 カウシェでは未来の仲間を探しています。 挑戦したいと感じている方、ぜひ話しましょう。 （記事リンクはリプライに）

日経新聞に取り上げていただきました。 スタートアップへの転職、40歳以上は10年前の7倍以上に増えているそうです。 自分もその一人。 40代でスタートアップCFOになった理由はシンプルで、「まだ挑戦できる場所にいたかった」から。 カウシェでは未来の仲間を探しています。 挑戦したいと感じている方、ぜひ話しましょう。 （記事リンクはリプライに）

New in Claude Code: Code Review. A team of agents runs a deep review on every PR. We built it for ourselves first. Code output per Anthropic engineer is up 200% this year and reviews were the bottleneck Personally, I’ve been using it for a few weeks and have found it catches many real bugs that I would not have noticed otherwise

Released today: /loop /loop is a powerful new way to schedule recurring tasks, for up to 3 days at a time eg. “/loop babysit all my PRs. Auto-fix build issues and when comments come in, use a worktree agent to fix them” eg. “/loop every morning use the Slack MCP to give me a summary of top posts I was tagged in” Let us know what you think!