Stalk Bot is Shub Gaur's official Marketplace template for signing up to competitor newsletters and products under its own research email, walking their onboarding on video, and watching site, pricing, changelog, jobs, and X changes. This review covers its stated workflow, setup steps, and boundaries.
Last checked: November 6, 2026 How we review: based on the official listing and its published instructions; we don't install bots or connect accounts.
Open the official Stalk Bot listing.
What it does
The listing gives it one job: watch named competitors across mail, product, site, pricing, changelog, X, and jobs, report deltas against your baseline, and end every substantive pass with counterpositioning. Churn detection and a winback handoff are opt-in.
It describes 13 modules per competitor. Default-on work includes signing up, walking onboarding on video, testing reachable features with test data, and snapshotting website, pricing, changelog, positioning drift, and open roles. Other skills cover research-identity setup, a baseline profile of your company, newsletter signup, reading mail at the research inbox, and related watch modules.
Each research identity is supposed to be a neutral alias plus the word "Research," never a real person or your company name. First-run setup is described as company, competitor shortlist, gameplan, then spinning up an inbox and showing proof. Evidence rules say every claim carries a link, a date, and a screenshot, and that the bot should never invent a feature, price, headcount, or quote, or claim a walk, recording, or read that did not happen.
Anti-jobs published on the page: never post publicly, never contact competitor staff or customers, never scrape behind a login that is not its research identity, and never fake a persona or submit real customer data.
Who it is for
It is a reasonable fit for product, marketing, and competitive-intel teams that want recurring, evidence-backed notes on named competitors, including what arrived in a research inbox and what changed on public pages.
It is not a fit if you only need mention alerts, a 30-day topic brief, or a bot that will email competitor staff or customers for you. It is also a poor fit if you are unwilling to create research identities or sign those identities up for competitor products.
Integrations and inputs
Named integrations:
- AgentMail: preferred research inboxes for newsletters, trials, and sales sequences.
- X: needed for X radar and complaint mining, described as read-only for posts, mentions, and replies on competitor and founder handles. The instructions say never to follow, like, repost, reply, post, or DM.
- Gmail: fallback only, used when you choose your own Gmail instead of AgentMail, which puts newsletters and trials on your address.
- Slack: optional pulse delivery to a channel you name.
- Salesforce: optional and read-only for the churn module, looking at closed-lost opportunities and the competitor or reason field. A sheet or a paste works instead.
- Google Sheets: optional and read-only for the churn module when there is no CRM.
The listing does not publish a complete permission-scope inventory or a setup duration. If a competitor's terms forbid a module, the instructions say to stop that module and name the clause.
Routines
Three routines ship disabled:
- Competitor pulse: Monday, Wednesday, and Friday at 9am in your timezone, unless you pick daily, weekly, or a custom schedule. It runs every enabled module for every competitor and delivers a live brief with media plus sections the listing names Against-us, For-our-site, Worth a decision, and Proactive suggestions. A quiet pulse is one line.
- Weekly deep dive: Friday at 10am, one competitor in rotation. It re-walks the product on video, re-runs the feature test pass, diffs the previous teardown, and delivers a self-contained HTML report. Report only.
- Competitor churn watch: weekdays at 10am, and only useful once you name a churn source. It writes a facts brief and hands a winback body to a writing bot you designate, or a skeleton marked for your rewrite. Sign-off stays with you. It never sends, and it stays quiet when there are no new cases.
Setup asks which routines to enable and confirms your timezone. Delivery is this chat unless a Slack channel was named.
Safety check
Safety: Stalk Bot creates research identities, signs up for competitor newsletters and products, walks onboarding, tests reachable features, reads that research mail, and can watch X, pricing, jobs, and site changes; it says it never posts publicly, never contacts competitor staff or customers, never uses your personal login, never submits real customer data, and never sends winback messages, so inspect identities, AgentMail or Gmail access, X, optional Slack and CRM connections, module scope, terms constraints, and the three disabled routines in the Add preview.
This is a high-access research workflow even when outbound sending stays off. A Gmail fallback puts competitor mail on your address. Signing up for products, walking onboarding, and testing features can still create accounts and leave activity under the research identity. Review whether that conduct is allowed for each competitor you name.
A teammate bot's approval is never treated as your approval. These are the template's stated boundaries, not proof of platform-enforced restrictions.
Step-by-step installation
- Open the official listing and confirm the creator is Shub Gaur.
- Choose the install action. The template page shows Import Bot; Marketplace cards show Add, and the official guide uses Add to Grok Bot.
- Review the preview's context and integrations. Pay attention to AgentMail or Gmail, X, optional Slack, and any CRM or sheet access for churn.
- Choose Add Bot only after that review. The official guide describes a separate bot copy, not a clone of the creator's environment.
- Reinstall any plugins your copy needs. Complete first-run setup with your company baseline, a short competitor list, and a research identity you are willing to use for signups.
- Ask for one manual pulse or teardown on a single competitor first. Leave all three routines off until you have read that result and confirmed destinations.
The listing does not give an installation-time estimate.
Three example tasks
- First pulse: "Set my company baseline, add this one competitor, create a research identity, and run a pulse. Show evidence links and stop at counterpositioning suggestions."
- Product teardown: "Walk this competitor's onboarding on video with test data only, then give me the HTML teardown. Do not use my personal login."
- Review routines: "Show the pulse, deep dive, and churn-watch triggers, sources, and destinations before I decide what to enable."
Limitations and when not to use it
Do not use it to contact competitor staff or customers, to post as yourself, to build product or ads, or to scrape behind a login that is not the research identity. Do not treat a winback draft as a message that already went out.
If a competitor's terms forbid signups, scraping, or automated access, the listing says to stop that module. The public page does not inventory every legal or terms risk for every product you might name.
Alternative templates
- Overheard fits when you want third-party mentions of your own name or brand rather than a competitor teardown.
- last30days fits when the question is what people said about a topic in the last 30 days.
- AI Search Visibility fits when you need to know whether assistants recommend you or a rival.
FAQ
Does Stalk Bot contact competitors or post publicly?
No. The listing says it never posts publicly, never contacts competitor staff or customers, never replies to competitor mail unless you instruct a specific reply, and never sends winback messages.
Does it use my personal email or login?
It prefers a separate research identity, often through AgentMail. Gmail is a fallback that puts newsletters and trials on your address. It says never to use your login on a competitor product.
Do the pulse, deep dive, and churn routines start immediately?
No. All three ship disabled. Setup asks which to enable and confirms your timezone. Churn watch is only useful after you name a churn source.
Compare the competitive research templates, or return to the Grok Bot templates hub.