Pipeline Pulse is Krista Letz's official Marketplace template for scanning a full pipeline for movement, stale next steps, forecast risk, and CRM gaps. 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 Pipeline Pulse listing.
What it does
The listing describes book-level monitoring: new signals, stale next steps, forecast risk, ownership and field hygiene, rollups, and supported drafts for next-step, close-date, stage, forecast, ownership, and hygiene updates.
It is positioned as a portfolio monitor rather than a qualification inspector or a tool that closes individual commitments. One skill on the page is pulling multi-source signals and drafting CRM next-step notes without inventing activity.
Source policy prefers live connectors, treats paste, CSV, exports, URLs, and files as fallbacks, and says conflicts should be shown with timestamps rather than merged silently.
Who it is for
It is a reasonable fit for account executives cleaning a book, sales managers running forecast, RevOps, founder-led sales, and customer success or account management roles that need rollups. Setup questions on the page ask about role, operating setup, and focus.
It is not a fit if your main need is closing one stranded promise, coaching a call, or rewriting a pitch deck.
Integrations and inputs
Named integrations are Salesforce, Gmail, Slack, Granola, Notion, and Google Sheets. The listing does not publish permission scopes or a setup duration. Paste and export routes are also described.
Start with a narrow approved opportunity view. If you connect CRM or email, inspect the actual account and scope being authorized.
Routines
One routine is listed: Weekday pipeline pulse. It is disabled by default and is described as scanning an approved opportunity view for new signals, stale next steps, and forecast risk.
The instructions say all routines ship disabled. Enabling requires an explicit schedule, source scope, private destination, empty-result behavior, and approval boundary. Routines never send externally or silently write, per the listing. Verify that in your copy.
Safety check
Safety: Pipeline Pulse can read CRM and related sales systems you connect and drafts forecast and hygiene updates; it says routines never send externally or silently write, so check the listed integrations, write permissions, approval boundary, and disabled Weekday pipeline pulse in the Add preview before enabling anything.
Pipeline data includes deal amounts, close dates, and customer names. Limit scope to the views you are authorized to process. The page also says public and routine outputs should not include private URLs, customer data, or tokens.
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 Krista Letz.
- 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 context and integrations in the app preview. Confirm the access shown fits monitoring and draft updates.
- 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, then answer only the setup questions required for your first scan.
- Run one manual pulse on a small approved view before enabling the weekday routine.
The listing does not state a setup duration.
Three example tasks
- Stale next steps: "Scan this opportunity export for deals with missing or stale next steps. Show the evidence for each risk and draft a next-step note without inventing activity."
- Forecast risk list: "From this book snapshot, list forecast risks and ownership or field hygiene gaps. Separate observed CRM fields from your recommendations."
- Draft-only CRM update: "Draft the stage and close-date updates that would make this forecast honest. Do not write to Salesforce until I approve each change."
Limitations and when not to use it
Do not use it for deep qualification-framework inspection, inbox reply drafting, or closing individual commitments; the listing excludes those. Do not treat drafted forecast changes as approved CRM writes.
If you need to close a specific open loop, use GTM Loop Closer. If you need call coaching, use Sales Call Coach.
Alternative templates
- GTM Loop Closer fits closing one evidenced commitment across tools.
- Sales Call Coach fits improving talk tracks rather than book hygiene.
- Pitch Deck Coach by Hiten Shah fits fundraising narrative, not pipeline rollups.
FAQ
Does Pipeline Pulse change forecast fields without approval?
The listing says it drafts next-step, close-date, stage, forecast, ownership, and hygiene updates, and that routines never send externally or silently write. Confirm write permissions in the Add preview.
Is the weekday routine enabled when I add it?
No. The Weekday pipeline pulse ships disabled. Enabling requires an explicit schedule, source scope, private destination, empty-result behavior, and approval boundary.
Which systems does it connect to?
The listing names Salesforce, Gmail, Slack, Granola, Notion, and Google Sheets. Scopes are not published, and paste or export fallbacks are also described.
Compare the sales templates, or return to the Grok Bot templates hub.