Grok Bot产品开发经验分享

My biggest takeaways from Grok @Bot product lead @RomanUgarte_: 1. Two key early product decisions ...

My biggest takeaways from Grok @Bot product lead @RomanUgarte_ : 1. Two key early product decisions made Grok Bot the success it has become. First, everything runs in the cloud. This means bots can be kicked off from a phone and run while the user sleeps. Second, each bot has access to its own computer. This allows it to operate on tools that have no API because they can simply use the computer the way a human would. 2. “Unshipping” is a big opportunity in product right now. One of the most counterintuitive things the Grok Bot team did in the weeks between internal beta and public launch was remove features. They initially exposed internal model thinking, memory traces, and developer-style observability tools inside the product. They decided to cut all that out. Their mental model for the product is a colleague: you wouldn't ask a teammate for second-by-second updates on every button they're pressing, so the bot shouldn't either. 3. The decision to make it a separate app (vs. inside Cursor) was not at all obvious. The team had the option to build Grok Bot inside Cursor, the way some competitors added knowledge-work tabs to their existing coding surfaces. Roman says the decision not to do that gave them complete control over every pixel and allowed them to build around a single, coherent vision of how an AI assistant should feel. The alternative, he argues, is "shipping your org chart"— and users can feel it. 4. Grok Bot went from the first line of code to a viral internal beta in four weeks. The team moved into a separate part of the office, set up private Slack channels, and made dozens of micro-decisions every day without needing buy-in from the larger org. This allowed them to go from internal beta to global launch in 3 weeks. 5. Roman and his team onboarded 200 to 300 people personally. This was one of the highest-leverage investments they made. When something broke or confused a user, the team felt it and fixed it the next day. Beyond the product improvements, the onboarding surfaced non-obvious use cases the internal team would never have imagined. A coffee shop owner found through a friend of a friend became one of Grok Bot’s most active users and a rich source of Shopify-integration feedback. 6. The Grok Bot team is “colleague-pilled” (vs. AGI-pilled). When the Grok Bot team hits a product decision with good arguments on both sides, they use a test: how would you want a human teammate to behave in this exact situation? Roman says the answer is almost always unanimous and clarifying. This is how Grok Bot landed on hiding internal mechanics from users, on building automations through natural language rather than UI, and on the huddle-style voice experience they’re building toward. 7. Grok Bot’s GTM team became one of its most enthusiastic internal user groups. Sales work depends on tools that often lack reliable integrations. Giving the bot a computer meant it could interact with those products the same way employees do. The resulting feedback forced them to level up Grok Bot’s computer use: the mouse needed finer control to click a particular part of a Salesforce dashboard. The infrastructure team would fix that invisible capability and hear the next day that the whole workflow finally worked. 8. Moats are discovered, not engineered. Roman said that if Cursor had tried to work backward from a moat strategy, it would not have created the product or the outcome it did. What worked was an obsession with building something genuinely useful today, pulling future capabilities forward even when they required significant engineering to stabilize, and then deleting that scaffolding as the models improved. The distribution advantages and data advantages followed from that. 9. Innovating requires the cultural willingness to abandon sunk costs. Roman’s explanation for why competitors haven’t made the same cloud-first, bot-gets-its-own-computer bets isn’t that they missed the insight. It’s that they’re stuck in an existing paradigm with real sunk costs. Most companies can see where the market is going; fewer have the stomach to act on it when acting means deprecating their current product. The advantage of building something new is that you get to be right about the future without the weight of having been right about the past. 10. Roman's advice for new users: connect Slack and email, then ask Grok Bot to go through them and suggest five things it could take off your plate. When he did this himself, two of the five were things no previous AI tool could have done, and he spun off two bots to handle them on the spot. Lenny Rachitsky @lennysan Grok @Bot is the hottest new AI product in the world right now. I'm absolutely hooked. It all started a few months ago as a tiny team holed up in a separate part of the office, building from scratch. Four weeks after the first line of code, the whole company was obsessed. Three weeks later, it launched to the world. Less than a month in, millions of Grok Bots are already helping people get work done. Roman Ugarte ( @romanugarte_ ) incubated, launched, and now leads product for Grok Bot. This is the first time he's told the story: 🔸 Why they started fresh instead of building it into Cursor 🔸 The two non-obvious bets that made it such a success 🔸 What they learned from manually onboarding the first 200–300 users 🔸 Why they spent the weeks before launch *unshipping* features 🔸 The first prompt to try when you open it Watch the full episode right here on X 👇 Your browser does not support the video tag. 🔗 View on Twitter 🔗 View Quoted Tweet 💬 7 🔄 2 ❤️ 11 👀 2880 📊 7 ⚡