Design
Explore 2 tools in this category.
Engineering
Engineering is where Grok Bot setups need receipts. A good Bot can triage issues, review a PR, update docs after a merge, run a narrow CI task, or keep a software crew coordinated. Grok Ship is the big pattern here: Firstmate, crewmates, state, routines, Cursor cloud work, and human judgment on decisions and PRs. Smaller workflows matter too: commits to issues to status page, Linear IDs in PR titles, and Intercom docs after a UI change. This hub is for code work that shows its trail. Trust comes from diffs, links, and review points.
Marketing
Marketing Bots earn their keep by turning noisy inputs into a small number of useful choices. Strong marketing setups include content crews, agency trend monitors, app-store growth work, and competitor-intel Bots that report only what changed. This category covers research, content, social, ads, analytics, SEO, and positioning. The best setups are not generic content machines. They watch a lane, gather receipts, draft with constraints, and leave the final taste decision to a person. Use this hub when the Bot is helping you pick what to say, where to say it, and what changed after you did.
Operations
Explore 1 tool in this category.
Product
Explore 4 tools in this category.
Sales
Sales work rewards Bots that are patient, narrow, and honest about approval. The useful setups do not pretend to close deals alone. They find likely accounts, enrich a lead list, draft the first note, update the CRM, or summarize what changed in a pipeline. Strong sales setups include prospect research, email outreach with before-and-after sorting, and small teams where Scout or Pitch has a defined lane. Use this category for sales Bots that reduce follow-up drag while keeping the human relationship intact. Good entries name the data source, the CRM field, and the moment a person reads before send.
Work
Work is where a Grok Bot earns trust or loses it fast. The useful setups do small, named jobs: sort the overnight inbox, draft the brief before a meeting, keep a task list honest, or turn a messy research trail into a readable note. Good work setups share that shape: chief-of-staff Bots, daily research tables, docs that update after a merge, and crews that hand work back for approval. This hub keeps the work lane practical. Look for setups that say what they sign into, what they change, and where a human stays in the loop.
