Pete Olsen, GTM Systems Operator

How I think through a revenue system

Building the system has now gotten easy. The hard part is asking the right questions before touching anything, knowing why to build it one way and not another, and spotting where issues could creep in. Nineteen stages from ICP to renewal, with my thinking at each one.

Dashboards show you averages. Following one lead shows you where it breaks.

System step AI agent step Includes client work Problem found

Ask before building

At Frameplay the pipeline wasn’t showing reality. I met with our CFO to discuss necessary changes to pipeline stages to allow our forecast to be more accurate. The team went from 25% to 75% of target.

“I’d rather fix the system that’s causing a problem than blame the person stuck in it.”

On AI

I build with Claude Code, n8n, and Clay’s CLI. Agents do most of the building now, so my job is writing the logic, overseeing the runs, and checking the results. Every stage shows who does the work and what I oversee.

The shared brainOne context file every agent reads before it does anything. Knowledge that used to live in one person’s head, written down where every agent and every teammate can use it.
Score0
OwnerUnassigned
StageProspect
Value$0
or press the right arrow key

System log

    Bring me a broken process

    A routing mess, a pipeline nobody trusts, a sync that keeps fighting itself. Send it over and we’ll get on a call and work through it together. You’ll see how I think faster than any résumé could show you.