Albert Rey Perez
LinkedIn Say hello

GTM Engine

Revenue operations and automated outbound · Turgon AI, 2026 to now

I built a campaign factory. One problem statement goes in. A live campaign comes out, running across email, calls and LinkedIn, with every send and reply logged.

I run the BDR team at Turgon AI and built the system it runs on in Claude Code. In one quarter, the share of held meetings that turned into deals went from 18% to 31%.

The factory

Claude Code builds every run. People approve spend and launches, read ten sample emails, and talk to prospects.

  1. Problem
  2. Signal-picked accounts
  3. Research check
  4. Tier A / B / C
  5. People by persona
  6. Verified emails
  7. Email gate
  8. CRM first
  9. Email
  10. Calls
  11. LinkedIn
  12. Reply
  13. Slack alert
  14. Daily scorecard
  15. Friday review

How a campaign gets built

Six steps. Each one ends on a check, so a bad list stops before it sends.

  1. 1Intake

    One problem, one hypothesis, and the rule for keeping or killing the campaign, written before launch.

  2. 2Account book

    Accounts picked by a dated buying signal, then tiered: A has two or more ways in, B has one, C is signal only. The tier decides the channels.

  3. 3People

    Personas in pick order, found on the tools already paid for first. Emails pass a seven-part gate, or the contact goes to calls only.

  4. 4Messaging

    One sequence per campaign, with a sourced opening line per person. A person reads ten rendered emails before anything loads.

  5. 5Send

    Contacts land in the CRM first, then load interleaved by company. The first 50 sends are a probe.

  6. 6Measure

    A scorecard refreshes every weekday morning, one row per run. Friday decides: keep, change, spread or kill.

Rules, and what broke to earn them

Every rule in the system exists because something went wrong once.

The stack: one job per tool

What moved the number

What it does and doesn’t do

The factory solves supply: the list, the research, the verified contacts and the first draft. Reps still win the meeting on calls and LinkedIn, so the system’s job is to feed those conversations, not replace them.

Three reps doing the work of ten.

Same engine, other markets

The inputs are a target list and a reason to reach out. Swap enterprise data leaders for beverage brands and the same workflow builds a sponsor pipeline, which is how I ran brand partnerships for Secret Disco Society.