Updated
What Apero builds with Cursor
Apero Advisors is a GTM engineering and revenue operations partner for PE- and VC-backed companies. Cursor is where Apero ships GTM software like a product team: named apps, reviewable code, and a repo the client can keep.
Ship and maintain GTM software with reviewable code.
What we build with Cursor
Cursor and Claude Code ship the named apps. Network Miner, the reply agent, CRM Health, inbound routing, Slack as the CRM, and sending ops.
These systems run inside Apero today. Client work uses the same patterns on the client's CRM, senders, and Slack.
How Ben prompts Cursor
Benyamin (Ben) Holley, Apero's Head of GTM, dictates prompts with Wispr Flow (voice to text) and prompts the repo from Slack, sending coding tasks to Cursor agents from Slack.
Example workflows
01
Network Miner: team LinkedIn graph to warm outreach
- Trigger
- A team has thousands of first-degree LinkedIn connections and nobody can query them together.
- System
- Each teammate's Connections.csv loads into one people graph keyed by LinkedIn URL. People are scored against ICP definitions in a markdown file, overlapped against CRM, and put in a keep or skip queue. Keep and skip labels rewrite the ranking prompt.
- Output
- Keepers enriched for email, added to CRM with the owning teammate noted, and enrolled in Lemlist with a first-degree icebreaker.
- Operator outcome
- Outreach starts from people who are likely to reply, not a bought list, and current customers are not re-pitched.
02
Reply agent with a playbook per campaign
- Trigger
- A prospect replies to a Lemlist or EmailBison campaign.
- System
- The reply loads that campaign's playbook (offer, real links, yes, no, question, and meeting rules, never-list). It is classified, drafted only from programmed links, and stopped in Slack for a human. Kill switches default off.
- Output
- A short draft with the right link for simple asks, or the raw reply in Slack for anything messy.
- Operator outcome
- Simple replies get handled fast without inventing a link, offer, or answer. Nothing auto-sends.
03
Inbound RevOps routing
- Trigger
- Someone submits the website form or replies to a campaign.
- System
- The person is enriched (LeadMagic, then Serper or Exa if LinkedIn is missing), the CRM account and contact are created or reused, skip rules apply, and the right follow-up lane runs.
- Output
- A CRM record, a routed follow-up, and a Slack card with the context.
- Operator outcome
- A hand-raiser does not disappear between the form, the sender, the CRM, and Slack.
04
CRM Health
- Trigger
- Every day.
- System
- A snapshot of CRM completeness, orphans, firmographics, persona coverage, and stale records. Definitions live in the repo.
- Output
- A health report an agent or a human can inspect against written definitions.
- Operator outcome
- Cleanup is specific instead of a vague 'go clean the CRM' request.
05
Nightly review on the GTM codebase
- Trigger
- Nightly, and whenever a PR is open.
- System
- Review runs on the repo that holds CRM sync, webhooks, and sending logic.
- Output
- Flagged breakage and unmerged PRs.
- Operator outcome
- Deliverability, CRM sync, and webhooks do not fail silently.
How we work in your codebase
- Access
- Client's choice: Apero builds in the client's accounts and repos, or in Apero's. API keys or MCP connections stay scoped to what the motion needs. Ideally each person's connection mirrors their own permissions, so the code cannot touch what that person could not.
- Change control
- Code lives in GitHub, not only in a workflow UI. Changes go through pull requests, and the GTM codebase gets a nightly review. Playbooks, never-lists, and kill switches are written in the repo instead of a mega-prompt.
- Documentation
- ICP files, SOPs, and definitions sit next to the code that uses them, so the next person (or agent) can read them. Context files beat a mega-prompt.
- Handoff
- That includes hosting (Vercel, Railway, or similar) as well as the GitHub repo. Docs and training come with the handoff either way.
When we do not reach for Cursor
- Shared list work the whole team needs to audit row by row. That stays in Clay.
- Dopamine-hit builds. A sleek internal app that does not help close deals is not worth maintaining.
- Anything where the sales motion is not defined yet. Code makes a fuzzy process louder.
FAQ
What does Apero build with Cursor?
Named GTM apps with reviewable code: Network Miner, an outreach reply agent, inbound RevOps routing, MUTHUR (Slack as the CRM interface), CRM Health, a Pre-CRM TAM store, and EmailBison operations. These systems run inside Apero Advisors today, and client engagements reuse the same patterns on the client's CRM and senders.
Does our team need to code to run the GTM software Apero builds?
Apero writes and maintains the GTM code. Your team does not need to code to run it. The hard part is knowing what should happen in the sales process, which is why the work starts with context, not syntax.
Is Cursor or Claude Code better for GTM engineering?
Apero uses both. Cursor is the default for shipping named apps with reviewable code. Claude Code is used for messy cross-system work like bulk CRM changes and enrichment runs. Many engagements use Clay for data and Cursor for everything that connects Clay to CRM and senders.