These are production systems Apero runs internally. Client work is the same pattern on your CRM, senders, and Slack, not a slide describing agents.
What GTM systems has Apero built with Cursor?
Apero has shipped Network Miner (LinkedIn graph to ICP-scored Lemlist outreach), an outreach reply agent (Lemlist and EmailBison drafts with Slack approval), RevOps inbound automations (website form to enrichment to Monday to sequence), MUTHUR (Slack as the CRM interface), Fireflies-to-CRM call writeback and deal-stage sync, CRM Health, a Pre-CRM TAM store, EmailBison operations (Apero Bison), billing reconciliation, and mailing list ops. Client engagements reuse these patterns on the client's CRM and senders.
Network Miner
Team LinkedIn graphs (and optional X followers) become an ICP-scored keep/skip queue, overlapped against CRM so customers are not re-pitched, then enrolled to Lemlist with a first-degree icebreaker. Built in Cursor. Prompt for a replica is on the Apero blog.
Outreach reply agent
Lemlist and EmailBison replies load a per-campaign playbook, classify yes/no/question/meeting, draft a short reply from programmed links, and stop in Slack until a human sends. Kill switches default off. Never auto-sends.
RevOps inbound routing
Website form to enrichment (LeadMagic, then Serper/Exa if LinkedIn is missing) to Monday contact/account to Lemlist campaign, then Slack. Separate lanes for work-email hand-raisers, mailing-list signups, and Bison replies that should get a LinkedIn invite.
MUTHUR (Slack CRM)
Slack is the interface to Monday: deal-stage alerts, pipeline questions, website-lead cards, calendar booking follow-up, campaign stats, LinkedIn lookup, and approved writes. Monday stays the source of truth.
Self-updating CRM from calls
Fireflies transcripts go to a business-trained agent that writes Monday meeting records. A related service classifies completed calls and advances deal stage only on high-confidence forward moves. Won and Lost stay terminal.
CRM Health
Daily snapshot of Monday completeness, orphans, firmographics, persona coverage, and stale records. Definitions live in the repo so an agent can inspect health without a generic "clean the CRM" prompt.
Pre-CRM TAM store
The account universe before it becomes CRM records: browse, score, and keep research out of HubSpot or Monday until someone is worth a row.
Apero Bison (EmailBison ops)
Sending infra dashboard plus reply and bounce classifiers, domain blacklist for current customers, EmailGuard placement, and Slack alerts on disconnected mailboxes. Routing of interested replies belongs in RevOps, not the sequencer UI.
Billing vs CRM reconciliation
Mercury invoices as the billing ledger, Monday as pipeline. Discrepancies are evidenced before any CRM write. Same idea for clients: billing system of record is not the CRM.
Mailing list and GTM context apps
Subscriber and newsletter ops against Lemlist, plus a working GTM plan (ICP, channels, activity targets) that agents can read. Context files beat a mega-prompt.
What does Grok Bot automate in GTM engineering?
At Apero, Grok Bot runs scheduled jobs against connected GTM tools: a morning follow-up brief on inbound and open deals, Fireflies transcripts matched to Monday deals with draft follow-ups, Slack commitment checks, referral mining on customer networks, CRM Health and EmailBison QA, and campaign drafting when SOPs exist in the repo. It sits on top of Clay, Cursor-built apps, Monday CRM, Lemlist, EmailBison, Fireflies, Slack, Gmail, and GitHub. It is not a substitute for a data model or a sequencer.
Morning follow-up brief
Inbound leads and open deals that went quiet, plus projects that still need a close. Posted before the inbox wins.
Post-call follow-ups
Pull yesterday's Fireflies calls, match Monday deals, draft follow-ups in the operator's voice, show anything that stalled.
Slack commitment check
Read Slack for promises the operator made and flag anything still open. Accountability without another dashboard.
Referral mining
Walk customer networks (job posts, graph overlap, ICP score) and surface referral asks that match a motion Apero already knows how to sell.
Campaign and list QA
Inspect Clay tables, EmailBison campaigns, and CRM Health definitions (orphans, incomplete records, persona gaps) instead of a vague "go clean it" prompt.
Repo and proposal chores
Review unmerged PRs on the GTM codebase, keep internal proposal pages current, and draft campaign copy when the SOP for list pull, segment, and first line lives in the repo.
Which tools is Grok Bot connected to at Apero?
Connected tools in the live Apero environment include Gmail, Slack, Google Calendar, Fireflies, Monday CRM, Clay, Lemlist, EmailBison, LeadMagic, Network Miner, GitHub, Vercel, Supabase, Cloudflare, Trigger.dev, Exa, Firecrawl, OpenRouter, ScaledMail, Reoon, Dynadot, and Deepline.