Scouts
Gremlin scouts are purpose-built investigative agents that map ownership, find data breakpoints, and return evidence for RevOps decisions. Gremlin is the janitor of the RevOps stack: it does the boring, load-bearing investigative work no one on a RevOps team has time to finish.
Point a scout at a system. It investigates who owns what, where data is breaking, and what is safe to change, then hands the findings to humans. The findings are structured so humans and their AI tools can turn them into an implementation plan, not just another dashboard to read.
What scouts actually do
They go look where teams already know something is off but never have the time to trace it properly.
Find the humans, rules, integrations, and workflows that really control the process.
Surface the places where data is drifting, policies are colliding, or follow-through is failing.
Return findings with enough context for a human or a bounded module to decide what happens next.
What you send a scout to go find
Not dashboards. Not vague monitoring. A scout is what you use when the question is messy and the ownership is unclear.
Go find the real owners
Scouts trace which humans, rules, integrations, and workflows actually control a messy process instead of relying on memory or stale documentation.
Bring back evidence
Each scout returns record-level evidence, reason codes, and structured findings so operators can see what was found and why.
Make messy systems legible
A scout is what you use when the question is messy, ownership is unclear, and nobody has time to trace the breakpoints by hand.
Run when needed or keep watch
Use scouts from Gremlin CLI when an executive asks a hard question or run them on customer-managed schedules for recurring coverage.
How teams use scouts
Some teams run scouts when an executive asks a hard question. Others keep them on customer-managed schedules so the same messy problems do not quietly come back.
Aim a scout at a messy question
Teams use scouts interactively from the CLI or run them on customer-managed schedules when the same issue keeps coming back.
Trace the evidence
Each finding carries typed evidence: record ids, relevant fields, reason codes, severity, and related record references.
Surface the breakpoints
Scouts recommend next moves such as pause sequence, route exception, or follow-up enforcement. They do not hide the handoff.
Hand findings to humans
People, modules, and approval flows decide what runs. That is the control point between investigation and execution.
Featured scout patterns
Gremlin ships 25+ scout checks today; these examples show the kind of boring, valuable work scouts take off a RevOps team's plate.
do_not_contact
Do Not Contact guardrail
DNC or support-escalation records that still overlap with outbound sequencing.
Suppression fields, optional open support cases, and Outreach-backed sequence state when configured.
Usually prepares review or pause follow-through for supported Outreach setups.
sequence_collision
Sequence collision detection
One persona enrolled in multiple active Outreach sequences at the same time.
Email-linked enrollments plus Outreach prospect and state lookups with deterministic priority rules.
Usually prepares targeted pause follow-through for Outreach-backed collisions.
cross_system_field_drift
Cross-system field drift detection
Conflicting canonical field values across source systems for the same entity.
Field provenance history and authoritative-source selection from the substrate layer.
Usually routes exceptions for review rather than claiming direct remediation.
customer_open_ticket_guardrail
Customer open-ticket guardrail
Existing customers, open-ticket accounts, or churn-marked accounts that still overlap with outbound sequencing.
Opportunity state, case state, churn markers, and Outreach-backed sequence enrollment.
Routes exceptions and can prepare pause follow-through for supported Outreach setups.
meeting_followup_breach
Meeting follow-up breach detection
Completed meetings with no follow-up inside the target SLA window.
Event timing plus follow-up activity from tasks, emails, notes, and related CRM activity.
Prepares reminder or follow-up enforcement steps; best understood as an audit, not an all-channel SLA guarantee.
Scouts investigate
Find risk, drift, collisions, and policy breaches.
Bring back evidence and recommended next steps.
Run on demand or on customer-managed schedules when teams need recurring coverage.
Modules execute
Apply approved actions such as pause sequence, route exception, or follow-up enforcement.
Live behind policy gates, approvals, and receipts.
Stay bounded so execution is reviewable instead of opaque.
Need the boundary in plain English?
Use the comparison guide if you need to explain where investigation ends and governed execution begins.
Where scouts show up in real work
Sometimes the investigation stands on its own. Sometimes it shows up inside an audit or a playbook.
Audit
Salesforce Lead Status Audit
Salesforce audit for teams that need to know whether lead status is telling the truth about tomorrow's pipeline.
Playbook
Inbound Lead Routing Patrol
An example scout operating loop for routing review built around unassigned inbound detection and adjacent CRM checks.
Playbook
Weekly Renewal Risk Sweep
An example scout operating loop for renewal review built from Gremlin renewal checks and CS handoff steps.
Not magic
Scouts investigate. They do not invent answers or decide what to change.
Not another dashboard
They do the digging for you instead of asking your team to build another monitoring layer.
Not a replacement for human judgment
Scouts hand findings to operators who decide what happens next.
Scout FAQ
What is a Gremlin scout?
A Gremlin scout is a purpose-built investigative agent in Gremlin CLI. It maps ownership, finds data breakpoints, and returns evidence so humans can decide the next action.
How is a scout different from a module?
Scouts investigate. Modules execute. A scout produces evidence and recommended actions. A module is the bounded execution unit that applies an approved change such as pausing a sequence or enforcing follow-up.
Do scouts decide for you?
No. Scouts investigate messy systems and hand findings to people. They can feed automation, but they do not replace human judgment.
Do scouts only run on a schedule?
No. Teams can run scouts on demand from the CLI for investigation or on customer-managed schedules for recurring coverage. The team owns the runtime.
Where do audits fit?
Scouts do the digging. Audits package that work around one business question. Playbooks show how a team uses the findings in real operating loops.
Need a concrete example?
Open the Lead Status Audit if you want to see scouts applied to a board-level question. Open Playbooks if you want to see the operating loops around them.