GTM Engineering Cheat Sheet · how the industry is changing

I talked to several Top 1% GTM Engineers.

Here are the 5 traits they all share.

I'm talking about people sending several million emails per month for clients.

1) They've outgrown Clay.

Off-the-shelf doesn't scale past a certain size. Every Top 1% GTM engineer I talked to is in Claude Code, building their own infra. Postgres, Trigger.dev, n8n. Clay is the gateway drug. Claude Code is what comes after.

2) They picked a camp.

The middle is cooked. Two paths left in the next 12 months:

→ Become technical. Run agents as your orchestrator. → Become a closer. AI eats the automation. You own the customer end-to-end.

The "I send some emails, I do some demos, I'm kind of technical" middle? Cooked.

3) They record every sales call.

Not for QA. They pipe recordings into Claude Code, pull out every objection, and answer them on the website or in a piece of content before the next call. By the time the prospect shows up, the objection is already dead.

4) Standard signals are dead.

Job change, funding, hiring · everyone has them. The alpha is in custom-built signals nobody else is firing on.

The signal triggers the send. It doesn't show up in the copy. "I saw you just raised" is dead too.

5) They ship micro-SaaS, not services.

Service as a Software. I've seen Lovable apps, Claude-Code-built dashboards, vibecoded internal tools running real client revenue. Every play that works gets wrapped in a product, sold per seat or per send. Less agency. More software.

This is the gap we built OXYGEN for.

GTM teams want to be in Claude Code. The primitives aren't there. So they vibecode buggy DIY software that breaks every other week.

Early feedback from top GTM engineers has been strong. More updates soon.

If you're building in this direction, hmu :)